Error Messages

  • Article
On This Page

Site Builder Error Messages Site Builder Error Messages
MSCMS 2001 Server Error Messages MSCMS 2001 Server Error Messages
Communication Errors Communication Errors
Site Stager Error Messages Site Stager Error Messages

This chapter contains a listing of Microsoft Content Management Server 2001 and MSCMS 2001 Site Stager error messages, categorized by the domain that generates them.

Most Content Management Server 2001 error messages contain details to help you determine the source of the error. Click the Details button on the error message for this information.

Site Builder Error Messages

The following messages can appear when working in the Site Builder.

Could not create a connection of Microsoft Content Management Server.
Could not open download start-up script server (URL is 
https://<servername>/NR/System/clientui/login.asp)
Could not get connection to Microsoft Content Management Server.
The attempt to connect to the server failed.

  • Context: Unexpected error when the user is launching the Site Builder.

  • Action: Check the network and server connections.

    Check that the IIS W3SVC is running on ths server.

Could not get connection to Microsoft Content Management Server Site Builder.
Failed to initialize the Microsoft Content Management Server Site Builder.

  • Context: Unexpected error when the user is launching Site Builder.

  • Action: Close MSCMS 2001 Site Builder and start Content Management Server 2001 again.

You do not have access rights to the Microsoft Content Management Server Site 
Builder.
Could not log into Microsoft Content Management Server. Either this user id 
has not been assigned any rights on the current server, or it is an Active 
Directory user id.

  • Context: The user attempts to launch Content Management Server 2001, but the system detects that the user has no access rights to Content Management Server 2001.

    The user may also be attempting an automatic login with an Active Directory user id that is not supported.

  • Action: Log on as a user who has access rights.

Content Management Server AENavBar::Init() failed. 

Content Management Server AENavBar.Init() called twice.

  • Context: Unexpected error when the user launches the Site Builder.

  • Action: Close Site Builder and start Content Management Server 2001 again.

Content Management Server NavBar.UnInit() called without Init() being called 
before.
Content Management Server AENavBar:UnInit() failed.

  • Context: Unexpected error when the user is closing Site Builder.

  • Action: Close Content Management Server 2001 and restart it.

The Page doesn't exist in the specified date and time.

  • Context: Occurs when viewing revisions by date.

  • Action: Select a date and time that is more recent than the last revision purge, the first editor approval of the posting, and older than the current date.

    • Large differences between the client computer's clock and the database server's clock can make it difficult to select specific revision dates.
You do not have sufficient rights to create Folder.
You do not have sufficient rights to create Channel.
You do not have sufficient rights to create page in this folder.
You do not have sufficient rights to create Gallery.

  • Context: Attempt to create an item while logged in as a user without administrator's rights.

  • Action: Log on as an administrator, or ask your administrator to give you additional rights.

The page has been opened in the Authoring window. Operation cannot be 
performed at this time.

  • Context: Attempt to Submit/Approve/Decline/Rename/Delete a page, while the Authoring window is open, has caused conflict within the system.

  • Action: Close the Authoring window and try again.

You do not have access right to edit the item.

  • Context: A user attempts to edit a page, but the user doesn't have the rights necessary to make changes to the item. It is possible the user's rights changed after the user opened the Authoring window.

  • Action: Log on as an administrator, or ask your administrator to give you additional rights.

Template has been opened in the Template Design window.

  • Context: User attempts to rename a template, but the template has been opened in the Authoring window.

  • Action: Close the Template Design window and try again.

Template has been opened by the Design Palette.

  • Context: Open a template in the Template Design window, while the template is open in the Design Palette.

    Open the Properties dialog box of a template, while the template is open in the Template Design Palette.

    Attempt to rename or delete a template, while the template is open in the Template Design Palette.

  • Action: Close the Template Design Palette.

Template has been opened in the Template Design window.

  • Context: Open a template in the HTML editor (use the Edit Template command), while the template is open in the Template Design window.

    Open the Properties dialog box of a template, while the template is open in the Template Design window.

    Attempt to rename or delete a template, while the template has been opened in the Template Design window.

  • Action: Close the Template Design window.

An unexpected error occurred during the new Group creation process.

  • Context: An administrator attempts to create a new rights group, but the system could not perform the operation.

  • Action: Try again.

Operation failed because lock cannot be obtained on the Root Control Gallery 
node.

  • Context: An administrator attempts to create a Template Designer rights group. The newly-created rights group must have access rights to the root control gallery; however, the system failed to lock the gallery, as it should. The control gallery may have been locked by another user.

  • Action: Try again.

You do not have sufficient rights to perform cut operation on this object.
You do not have sufficient rights to perform this paste operation.
An unexpected error occurred during the paste process.

  • Context: User attempts to cut/copy/paste an object, but does not have access rights to perform operation.

  • Action: None.

Failed to lock the item.

  • Context: This is a general message issued when the system has failed to lock an item.

  • Action: Refresh the associated folder and try again.

Authoring window error messages

The following messages may appear when a user is working in the Authoring window.

The number of objects selected exceeded the allowed maximum for this 
placeholder.

  • Context(s): Insert more than one image or video into a placeholder whose properties are set to allow no more than one object to be inserted.

  • Action: Insert only one object, or ask the template's designer to change the placeholder's properties to allow for insertion of multiple items.

Some of the selected elements were not inserted. Please check the 
placeholder's properties for allowed element types.

  • Context(s): Insert an image or video into a placeholder that does not allow this type of content.

  • Action: Insert only the type of content allowed by the placeholder, or ask the template's designer to change the placeholder's properties to allow for the type of content you would like to insert.

Formatting was removed from inserted section. Some elements may have been 
discarded.

  • Context(s): Insert text that contains formatting, for example from MS Word, into a placeholder whose properties have been set to allow plain text only.

  • Action: Insert plain text, or ask the template's designer to change the placeholder's setting to allow for insertion of formatted text.

Not enough storage is available to process this command.

  • Context(s): Paste a block of text that exceeds 300 KB into a page's placeholder. Save the page.

  • Action: Content Management Server 2001 does not allow a placeholder to contain a text file that exceeds 300 KB. Divide and distribute large text files among two or more placeholders on a page.

<folder name> could not be deleted because of the following conditions: the 
page <page name> is currently locked by user <user name>.

  • Context(s): Save a page in the Authoring window, after another user has deleted the folder you are saving the page to.

  • Action: Ask author to save the page to a different folder.

Failed to create <page/template> in the folder.

  • Context(s): Click Save in the Save As dialog box.

  • Action: Select another folder. User may have recently lost rights in the selected folder.

Item is locked by user <user name> on machine <machine name>.

  • Context(s): - Delete an item.

    • Approve/submit page

    • Approve posting.

    • Edit template.

  • Action: The item is locked by another user; try again later. If lock is erroneous, kill lock as administrator.

This <page/template> is no longer locked. Changes made cannot be saved.

  • Context(s): Save, or any command that performs a save operation (save as, submit, approve, decline, add/remove view).

    • Close the Authoring window

    • Submit a template in the Template Design window

    • Edit template HTML

  • Action: Close the Authoring window and open the page again. The administrator may have killed the lock on this item.

To remove this View, you must first delete all postings for it, and empty the 
Channels hierarchy's Deleted Items. 
If you still cannot remove the View, there are probably one or more postings 
for it that you don't have rights to see or delete. If necessary, contact the 
administrator.

  • Context(s): Select the "Remove View" option in Authoring window.

  • Action: To remove a view from a page, there must be no postings created from that view, including those moved to the Deleted Items container. If this message appears again, after all associated postings have apparently been deleted, it is likely that postings associated with the view still exist—they are in containers the user does not have access to.

Failed to remove View. 
There are probably one or more postings for it that you don't have rights to 
see or delete. If necessary, contact the administrator.

  • Context(s): Select the "Remove View" option in the Authoring window.

  • Action: If there are no postings on the page, the lock on the page may have been killed.

Failed to remove View. Operation cancelled.

  • Context(s): Select the "Remove View" option in the Authoring window.

  • Action: The request to remove the View failed because the page is no longer locked; possibly an administrator has killed the lock. Close the Authoring window and open the page again.

Properties dialog error messages

The following messages may appear in the context of a Properties dialog box, opened from either the Content Management Server 2001 or Authoring windows.

Failed to create posting in this channel.

  • Context: Click the Create Posting button.

  • Action: It is possible the user's rights on the selected channel have changed. To verify this, the user should close the Postings dialog box, return to the Site Builder and refresh the channels hierarchy. From the channels hierarchy, select the channel chosen to create a posting for, and click on it. If the channel icon is blue, it means the user should have posting rights there; if the channel is dimmed, the user doesn't have rights.

Item is locked by user <user name> on machine <machine name>.

  • Contexts: Click OK on a Properties dialog box.

    • Delete an item.

    • Set Sub-Channel Templates in channel Properties dialog box.

    • Modify Group Rights in User Role Properties dialog box.

    • Purge template.

  • Action: The item is locked by another user; try again later. If lock is erroneous, use the Kill Lock command.

Failed to lock the item.

  • Contexts: Delete an item.

    • Purge template.

    • Approve/Submit a posting.

    • Approve posting.

    • Edit template.

    • Set sub-channel templates in channel properties.

    • Modify user role properties.

  • Action: Refresh the MSCMS 2001 Site Builder.

Insufficient rights to use the template, please select another template.

  • Context: Click the OK button in the Select Template dialog box.

  • Action: Select another template and try again. It is possible that the user's rights on the selected template have changed. So alternatively, the user can exit the dialog box, refresh the Template Gallery hierarchy, and try again.

Failed to lock the item <channel/posting name>.

  • Context: In a Channel Properties dialog box, click the OK button after sorting the order of sub-channels and postings on the Postings tab of the dialog box.

  • Action: None. Since it is not locked by another user, the item's data may be corrupted. The order of the other channels and postings should be unaffected.

Item <channel/posting name> is locked by user <locking username> on machine 
<locking machine name>. 
Invalid folder to move to.
The expiry policy will be set to do nothing.

  • Context: In a page's Properties dialog box, for the On Expiry Options on the General tab, user selects the Move To option, but the folder the user wants to move the page to does not exist.

  • Action: Select another target folder to move to on expiry.

Template has been opened by the Design Palette. Please try later.

  • Context: Attempt to edit or delete a template.

  • Action: Switch to the default HTML editor, and find the template that has been opened by the Template Design Palette. If it is not opened, it has probably been closed by the HTML editor. To edit this template, close the Template Design Palette, and try again.

Template has been opened in the Template Design window.
Please try later.

  • Context: Attempt to edit or delete a template.

  • Action: Find and close the Template Design window, which will have this template opened and try again.

The selected cover page has been moved to Deleted Items. Do you want to use 
default cover page.
The selected Cover page has been deleted on the server. The default cover page 
will be used.
This posting is not currently published. Do you want to use default cover 
page.
This Channel is not currently active. Do you want to use default cover page.

  • Context: A selected cover page is not valid anymore when the user opens the Channel Properties dialog.

  • Action: Select a new cover page or select the default one.

Failed to retrieve the Base template for new template creation.

  • Context: Import a template.

  • Action: Restart Content Management Server 2001 and try again.

The expiry date of this page has passed. Do you still wish to submit the page?
The expiry date of this page has passed. Do you still wish to approve the 
page?

  • Context: Submit/Approve page.

  • **Action:**Clicking the Yes button will continue the Submit/Approve process of the page; however, when the page is approved, the page's status will change to "Expired" as opposed to "Published," since its expiry date has passed. Alternatively, the user can select "No" to cancel the operation, then make changes in the Expiry Date option for the page, and try again.

Link: <linked file name> not found. Continue Parse?
Control: <control file name> not found. Continue Parse?
Resource: <resource file name> not found.
Continue Parse?

  • Context: Import a template.

  • Action: Click the OK button to continue the parsing of the template being imported. Or click the No button to cancel the operation.

Template Design Palette error messages

The following messages may appear in the context of the template Design Palette (sometimes referred to as the HTML Editor Manager).

Failed to create Content Management Server Parser Manager COM object.

  • Context: The user's copy of the MSCMS 2001 Site Builder does not have the Content Management Server 2001 parser installed and/or registered. The Content Management Server 2001 parser is required to edit templates.

  • Action: Re-install the MSCMS 2001 Site Builder.

Download of template file <insert filename here> from <insert URL here> 
failed. Check for the existence of this file on the server and try again.

  • Context: The user wants to edit a particular template, but Content Management Server 2001 is unable to find the template file on the MSCMS 2001 server.

  • Action: Refresh the screen, then verify that another user has not deleted the template from the template gallery.

Failed to create an instance of the file notification object.

  • Context: Content Management Server 2001 cannot create an instance of a required component.

  • Action: Check that TEMP and TMP system variables are set to valid, existing directories. These can be found at Start>Control Panel>System > Environment. Also try re-installing the MSCMS 2001 Site Builder

Failed to configure an HTML editor.

  • Context: The user attempts to configure an HTML editor for use with Content Management Server 2001, but configuration fails.

  • Action: The client machine does not have the required control installed and registered for configuring an HTML editor. The missing OCX is HTMEDTUI.OCX. Re-install the MSCMS 2001 Site Builder.

No HTML file specified to edit.

  • Context: The user attempts to edit a template but Content Management Server 2001 cannot find the HTML file associated with the template.

  • Action: Ensure that a template is selected (highlighted) in the Site Builder and try again.

Microsoft Content Management Server has not detected a save action from your 
HTML editor. If you have made any changes to the template <insert template 
name here>, these will not be saved unless you return to the editor and save 
the file. Close Design Palette anyway?

  • Context: The user attempts to close the Design Palette window before saving changes made to the template.

  • Action: Clicking the Yes button: the Design Palette closes; the user can no longer save any changes to the template.

    Clicking the No button: the Design Palette stays, allowing the user to continue editing the template, if the HTML editor is open.

MSCMS 2001 Server Error Messages

The following messages may appear when a call is made to the MSCMS 2001 server. They are initiated by the server.

SYSTEM ERROR: Server running low on memory.
Please record and report this error to the appropriate administrator.

  • Context: This error can occur following any call to the server.

  • Action: Shut down unnecessary processes on the server. If the error persists, restart the (IIS) server. As a last resort, reboot.

This item is not available for you to update. This is possibly due to the fact 
that an administrator has killed the lock on it in which case your changes 
will be lost... If not, this is probably a software error and should be 
reported to the appropriate administrator.

  • Context: Saving changes to the server.

  • Action: Try to get exclusive access to the node and make your changes again. Advise your administrator that you don't want your locks killed.

User Error: That Microsoft Content Management Server item (node<number>) is 
currently in use by another user (<name> on <computer>).

  • Context: A user attempts to modify an item, thereby requesting exclusive access to it.

  • Action: If the other user is not intentionally locking the item, or is not available, or is not using the specified computer, an administrator may need to manually kill the lock on the item.

SYSTEM ERROR:
The current transaction was deadlocked (more than once) and could not be 
completed.
Please record and report this error to the appropriate administrator.

  • Context: Do an update on the server by saving changes to an item, approving/publishing a page, or obtaining exclusive access on an item.

  • Action: Try again, if possible. If the other user is not intentionally locking the item, or is not available, or is not using the specified computer, an administrator may need to manually kill the lock on the item.

SYSTEM ERROR:
The current transaction failed because updating the database failed as either 
the database is full, or the transaction log is full.
Please record and report to the appropriate administrator.

  • Context: Do an update on the server, by saving changes to an item, approving/publishing a page, or obtaining exclusive access to an item.

  • Action: Allocate more database space to the server, or dump the transaction log (as appropriate).

INTERNAL ERROR:
<error specific message>
Please record and report this error to the appropriate administrator.

  • Context: Access the server.

  • Action: Restart the server.

Communication Errors

The following error messages may appear when a call is made to the server. They are initiated from the client-side proxy, or the server-side stub.

Network IO exception.

  • Context: This error is seen when the user opens the administration tool; it usually indicates that the anonymous user has not been configured properly on the server.

  • Action: This may occur when either the network or server are not available. Check that both are connected properly and working.

Could not continue server conversation.

  • Context: The security manager on the server couldn't validate token received from client.

  • Action: Ensure that if security service has been shut down, the Web server was properly shut down as well. In IIS3, this means all services must be shut down; in IIS4, the IIS admin service must be shut down.

Could not create object.

  • Context: The stub has attempted and failed to create a required subcomponent. This error indicates that the code has issued a "class not registered" error from the operating system.

  • Action: Ensure that the security manager, grammar parser DLLs, and any other server-side components are correctly installed and registered.

Insufficient access privileges to perform this action.

  • Context: The system allowed the user access to an area where the user does not have rights to perform the requested action.

  • Action: This is an unexpected exception.

Operation timed out.
  • Context: The server's attempt to check in/out an item may return this error if updates to the database cannot be completed quickly enough. This can indicate that the proxy was not able to synchronize data with the stub object for whatever reason when attempting to perform an update.
The following node has been removed from the database: {guid of node}

  • Context: Another user has deleted the "node" being accessed by the current user.

  • Action: Try to refresh the Site Builder and try again.

Node retrieval aborted due to timeout or network error.
  • Context: Downloading an item from the server may report this error if another network exception or transaction fails and therefore interrupts this download, preventing it from completing successfully.

Site Stager Error Messages

Internal error messages

An entry already exists in the staging name mapper for this URL: <URL>
Could not convert to a usable name: <URL>
Could not find URL in Staging Map when it should have been added prior to 
staging - <URL>
Could not parse URL correctly in source: <referring URL>
Entry not added successfully to StagingNameMapper <URL>
Entry not found in StagingNameMapper: <URL>
Error staging a link: no new URL returned. Old URL: <URL>
Error while trying to get the children of an XML element.
Failed to find text off the TITLE subtag of the XML Element.
Failed to get HREF attribute off the XML Element. 
Failed to get TITLE subtag of the XML Element.
URL not registered with name mapper: <URL>
Error while trying to get the children of an XML element.
Cannot stage the specified item. The URL for the staged item has not been set.
Could not create mail slot: <Filename>
Could not find URL in Staging Map when it should have been added prior to 
staging 
MSCMS 2001 Site Stager was unable to download the sitemap from MSCSMS 2001 server
  • Context: An internal error indicates each of the above error messages.

System errors

Problem encountered in creating the log directory. <Directory>

  • Context: There was an error in creating the log directory. This sub-directory should reside in the directory as all the Site Stager components.

  • Action: Create a directory called Site Stager Logs in the directory that contains the Site Stager components.

Error in formatting the name of the log file.

  • Context: There was a failure in the Site Stager's call to create the name of the log file from a system service.

  • Action: Check that other programs are working—this may be a system-wide problem.

Problem encountered in creating the Staging Directory - <Staging Directory>

  • Context: There was an error in creating the Destination Directory.

  • Action: Check that the Destination User has rights to create the Destination Directory; or try creating the directory manually as the Destination User. Check that there is enough disk space available on the Destination disk.

Problem encountered in creating a test directory <Directory> in the Staging 
Directory. The Destination User may not have the proper access rights.

  • Context: The Site Stager attempted to create a test directory in the Destination Directory to test the Destination User's access rights to the Destination Directory, but the process failed.

  • Action: Verify that the Destination User has Change (RWXD) access to the Destination Directory.

Could not convert Java Proxy progid to clsid. Please recheck your Site Stager 
installation.

  • Context: The Site Stager cannot translate the PROGID representing Content Management Server 2001 Java Proxy to the CLSID that represents this software component. This could be the result of the Content Management Server 2001 Java Proxy not being installed.

  • Action: If the MSCMS 2001 Site Builder is also installed, try running it to check that the Proxy is installed properly. Otherwise, try re-installing the Site Stager to install the proxy.

Could not co-create Java Proxy component. Please recheck your Site Stager 
installation.

  • Context: Site Stager cannot access the Content Management Server 2001 Java Proxy software component. Site Stager needs this component to log on the server designated for staging.

  • Action: Re-install Site Stager.

Proxy Login process failed.

  • Context: Site Stager tried to execute the Login command on the Proxy. No connection has been made to the server yet.

  • Action: There may be an error in the Proxy; if the MSCMS 2001 Site Builder is installed, try running it. If the MSCMS 2001 Site Builder will not run, try re-installing MSCMS 2001 Site Stager.

Failed to connect to server, probably due to user authentication error. Please 
\check the Stage As User name and password in the staging profile. Also check 
to make sure the Microsoft Content Management Server has this virtual path.

  • Context: Site Stager is failing to access the server that is to be staged.

  • Action: Check that the Stage As User username and password are correct. Check that the server is operating and is properly connected to the machine that will host the staged site.

Failed to get Login Cookie from Proxy.

  • Context: Site Stager is failing to get the authentication token from the Java Proxy that it needs in order to make secure requests to the server.

  • Action: The Stage As User settings may be incorrect, or there might be an error in the Proxy; if the MSCMS 2001 Site Builder is installed, try running it. If the Site Builder will not run, then try re-installing Site Stager.

Initialization of XML Parser with URL: <Sitemap URL> failed. Please make sure 
that IE4.01 is installed.

  • Context: Site Stager is using the XML Parser in Internet Explorer 4.01 or above to parse the sitemap located at the given URL.

  • Action: Check that the Profile's Site Map URL is correct. Check that the structure of the generated sitemap is correct—it should be a properly formatted XML document. Check that IE4.01 is installed properly.

Error opening input file: <Filename>

  • Context: Site Stager is trying to open the downloaded file for processing links.

  • Action: Check that the file exists and is accessible for reading and writing by the Destination User.

Error reading input file into memory: <Filename>

  • Context: The Site Stager is trying to read the file for processing.

  • Action: Check that the file exists and is accessible for reading by the Destination User.

Error closing the input file: <Filename>

  • Context: The Site Stager is trying to close the file after reading from it.

  • Action: Check that the file exists and is accessible for reading by the Destination User.

Error opening output file for writing: <Filename>

  • Context: The Site Stager is trying to open the file for writing.

  • Action: Check that the file exists and is accessible for reading and writing by the Destination User.

Error saving/closing output file: <Filename>

  • Context: The Site Stager is trying to close the file after writing to it.

  • Action: Check that the file exists and is accessible for writing by the Destination User.

Problem encountered while attempting to create a directory for the system to 
be staged <Directory>

  • Context: Site Stager couldn't create a directory for the site to be staged.

  • Action: Make sure that the Destination User has Change (RWXD) access rights to the Destination Directory and all its subdirectories, if they were present before staging started.

Could not determine server name from the Site Map URL <Sitemap URL>. Please 
check the Site Map URL setting in the staging profile.

  • Context: The Site Stager could not determine the server name from the Site Map URL. It needs the server name in order to log on to the correct MSCMS 2001 server and download the Site Map.

  • Action: Make sure that the Site Map URL is correctly entered in the form:
    https://<servername or IP address>/<path>/sitemap.asp.

No Stage As User is specified for this profile. Please check the Stage As User 
setting in the staging profile.

  • Context: A profile that the Site Stager is trying to stage has no Stage As User specified.

  • Action: Re-edit the profile and add the missing information in the Stage As User field.

No Site Map URL is specified for this profile. Please check the Site Map URL 
setting in the staging profile.

  • Context: A profile that the Site Stager is trying to stage has no Site Map URL specified.

  • Action: Re-edit the profile and add the missing information.

No Default Filename is specified for this profile. Please check the Default 
Filename setting in the staging profile.

  • Context: A profile that the Site Stager is trying to stage has no Default Filename specified.

  • Action: Re-edit the profile and add the missing information.

The Default Filename <Filename> specified contains illegal characters. Only 
letters, numbers and the period are permitted. Please check the Default 
Filename setting in the staging profile.

  • Context: The Default Filename, specified in the profile that the Site Stager is trying to stage, cannot be used as the name of a file.

  • Action: Re-edit the profile and change the name of the Default Filename.

Failed to get the root channel out of the sitemap. Perhaps the user does not 
have access to the root channel.

  • Context: The Site Stager can't extract the root object out of the XML document. The Site Map document generated by the Site Map URL may be malformed or empty.

  • Action: This may occur because the Stage As User does not have access to the root channel of the MSCMS 2001 server that is to be staged. Check the Stage As User's access rights to channels on the MSCMS 2001 server.

Broken link in location:<Referrer URL> - Could not download this URL:<URL> -> 
<Temp Filename> - <Internal Information> Link: <Destination URL on the Staged 
Site> Found on the page: <Staged Page Location>

  • Context: The Site Stager couldn't download the page located at <URL>. <Destination URL > is the Staged version of the <URL> once the link works and is staged successfully. <Staged Page Location> is the Staged Page where the broken URL was found.

  • Action: Check that a page exists at <URL>. Also if a script is used to generate the page, it may work during Published mode but fail during staging mode. This can be determined by doing a preview of the page using the MSCMS 2001 Site Builder and setting the "mode" query string parameter from "Unpublished" to "Staging."

Error getting file info, looks like the disk is full: <Filename> (Downloaded 
from: <URL>)

  • Context: The Site Stager may be unable to stage a file correctly because of low disk space and therefore can't get the attributes of the file (like file length).

  • Action: Check if the hard disk is low on disk space and free up space to accommodate the staged output.

Error opening this file, looks like the disk is full: <Filename>(Downloaded 
from: <URL>)

  • Context: The Site Stager may be unable to stage a file correctly because of low disk space and therefore can't open the file. Also the Site Stager may be unable to open the file for reading and writing because of insufficient access rights.

  • Action: Check if the hard disk is low on disk space and make sure that Site Stager can read and write to files in the Destination Directory.

Error getting attributes of file: <Filename>.

  • Context: Site Stager cannot get attributes of the file <Filename>. During the staging process, Site Stager creates temporary files which it compares to files (if they exist) in a previously staged site. This error could occur if files are deleted while the Staging Process is underway and Site Stager is unaware that the files are being deleted.

  • Action: Check to see if the file exists. Do not delete files in a previously staged site once staging is underway. Do not delete files in the Staging temp directory (<Dest. Directory>\temp) once staging is underway.

Problem encountered in creating the resource directory <Directory Path>

  • Context: The Site Stager failed to create the resource directory in the Destination Directory. The resource directory is a directory specified in the Staging Profile as holding resources if they are to be stored separately from the HTML content that is being staged.

  • Action: Check that the Site Stager Destination User has rights to create files and directories in the Destination Directory.

Failed to create the download log: <Filename>

  • Context: The Site Stager couldn't create a log file in the logs directory that's located in the Destination Directory.

  • Action: Check that the Site Stager Destination User has rights to create a file in the Destination Directory and that any logs files currently in the directory are not read-only or locked for use by another process.

Problem encountered in creating the log directory - <Directory Path>

  • Context: Site Stager couldn't create the Site Stager Logs directory which is usually in C:\Program Files\Microsoft Content Management Server directory, or wherever the Microsoft Content Management Server 2001 programs are installed.

  • Action: Check that the Destination User has sufficient rights to create a directory in Content Management Server 2001 folder and can create and write files in that directory.

Error: Destination disk has less than <Number> Megabytes of storage free 
(<Number> MB free). Aborting staging.

  • Context: Not enough space on the hard disk for Site Stager to do its job properly.

  • Action: Make room on the hard drive where the Destination Directory is located. Site Stager creates temporary files before overwriting any previously staged site so make enough room to accommodate both these temporary files and the previously staged site. Enough room to hold two versions of the staged site is sufficient.

Failed to download sitemap for this URL:<URL> Error code = <Error Code>

  • Context: Site Stager failed to download the SiteMap which it uses to get the URLs of all channels and postings to be staged.

  • Action: Verify that the SiteMap URL works by navigating to the following URL in Internet Explorer: https://<server>/nr/system/access/manuallogin.asp?NEXTURL=<sitemap url>