One or more requests have failed (red button with a white x)
The sample documents have been thoroughly tested to ensure that they will not result in conversion or publication errors when they are published immediately after installation. If one or more of the conversion requests has failed, this indicates that there may be problems with access rights in the Hyper.Net-SharePoint environment or that there may be a problem accessing or running Office 2007. Review the privileges and rights associated with the various administrator IDs you specified for use with Hyper.Net during the installation process to ensure that rights exist to access the server file system, SharePoint libraries and SQL.
| |
|
|
|
The ID or IDs used with Hyper.Net must have local and domain access. If you have both local and domain policies in place, keep in mind that your domain policies may reset your local policies. It is therefore important that the local and domain access privileges associated with the ID or IDs are allowed by your domain policies.
|
| |
|
|
Tip
|
If all of the sample document transformation requests end in failure, this could indicate that Microsoft Office was not activated after it was installed on the server. If this is the case, activate Office and re-queue all of the transformation requests.
To select and re-queue all of the sample document transformation requests, locate the Select Action Menu (see image below) in the Hyper.Net Administration Console, click on Select All, then click on Re-Queue.
|