I have noticed that during a Site Deployment import, there are HTTP 500 errors being thrown on the site. Once the import was complete, the site was back to normal.
We think that some of our templates were expecting certain objects (i.e. channels, resources, etc.) to be available, but during import the expected objects may not have been present; this results in ASP scripting errors (HTTP 500) (unless there is template code checking wherever an object is available).
What kind of prescriptive guidance is there for doing imports? Until now I had always assumed that it should be fairly safe to perform an import on a live site. If this is not true – and we should assume that a site is taken offline during the import – this creates a fairly significant availability issue for shops that want to create a Development - Staging – Production scenario.
In MCMS 2002, this problem has been greatly minimized. Site Deployment is faster and therefore these types of issues are not as much of a concern.
For large site updates, a long import can cause these problems by locking objects. A workaround would be to import into another MCMS server running from a different database and then flipping the database connection through the Site Configuration API. Microsoft Internet Information Server (IIS) will need to be stopped and started.
So pages that are not in the cache will not be rendered, and any page that makes calls to the database (specifically the searches like custom prop searches and approval searches) will fail as well.
Site deployment does not import files at all. So if your templates have references to things on the file system (.GIFs, .INCs, etc) and you are changing your templates, there may be some errors thrown while import is going on. The problems would start when you changed the include files and continue until the new templates were in place. Or they would start when the new templates arrived and continue until the new include files were available. Unfortunately, the only way around this is to update your site offline so that you can be sure the include files and the templates arrive at the same time.
This would apply whenever you are changing code assets of the site - which is probably a pretty major revision. In those cases, consider doing rolling updates of your site using App Center.
For smaller updates to the site, site deployment should work well. Updates to content and anything else that is in the MCMS repository are handled just fine while the site is live. The availability of resources, channels, etc is managed so that objects with dependencies are there when asked for. Odds are it was code assets that caused the problems.
[Back to Top]
Topic: Content not deployed to destination site
When deploying content from an authoring environment to a production (live) environment, some pages are not updated properly. What can cause this?
Answer
The most probable reason for the updates not to be seen on the destination server (production/live system) is that new content was not exported from the authoring server.
When updating content an author will do one of the below action that will set the page back to a Waiting for Moderator approval status:
- Set the expiry date or set any property of the page
- Modify page content, any placeholder and save the page
As with MCMS 2002 only approved items will be exported, the updated content will not be exported unless it is submitted again for approval and approved. Failing to approve again the content, the export package will not include any change done on the item and thus will leave the content unchanged from its previous state on the destination server.
See also in the MCMS docucumentation:
\Troubleshooting MCMS 2002
\Troubleshooting MCMS Site Authoring Tools
\Content Revisions Do Not Appear on Live Site
If an author adds some information to a page that was previously published and then saves the page, the new content will appear in the edit site only. The live site will not display the new content until it has been approved.
\Managing Site Structure and Workflow
\Deploying web Site Content
\About Exporting and Importing Objects
Make sure that all objects to be exported have been approved by your assigned approver before exporting them. Any object that is submitted but not approved will not be exported. Objects on the destination server with dependencies to objects being imported will be affected by the import operation. For example, if a template is replaced during import, all of the pages using the template will automatically use the new template.
\Deploying MCMS 2002
\Types of Site Deployment
\Incremental Site Deployment
You perform an incremental site deployment to export only MCMS-managed objects that have changed since the last deployment. MCMS managed objects include channels and approved pages, as well as the resources that they depend on.
[Back to Top]
Topic: Deleted items are not deployed
We are using incremental deployment scripts to deploy the content of our Web site to our production server. Usually we limit the deployment by specifying a channel start GUID. When using such a script items deleted in Site Manager do not get deployed to the production server. How can we solve this problem?
Answer
The reason for this is that deletion in Site Manager is not really a delete. It is actually a move to the Deleted Items folder. If you purge this folder then the item gets deleted.
Regardless of whether the item is still in the Deleted Items folder or already purged it no longer has an association with your start channel. To ensure that the items deleted in Site Manager really get deleted on the production server you have to manually deploy the Deleted Items folder.
Use the script below to export the Deleted Items folder to an SDO file:
set pCmsDeployExport = CreateObject("CmsDeployServer.CmsDeployExport.1")
pCmsDeployExport.AuthenticateAsCurrentUser()
strPackageFileName = "your-filename"
strReportUrl = pCmsDeployExport.Export(strPackageFileName, 0,"{E4D1911E-9DD3-11D1-B44E-006097071264}")
set ie = CreateObject("InternetExplorer.Application")
ie.Visible = True
ie.Navigate("http://localhost" & strReportURL)
[Back to Top]
Topic: Error message: "ASP 104 - Operation not allowed"
I am using MCMS 2002 SP1 on Windows Server 2003. I am getting the following error when trying to import an SDO Package (I can export fine):
Error: 0
Description: 007~ASP 0104~Operation not Allowed~
Severity: 5
Source: NRXMLMarshaler.NRFileUploadResponse.1
Debug info: N/A
Extra info: N/A
Client Source: CImProgress::ProcessPackage
Recommended Action: N/A
Answer
This is caused by a new feature in Windows 2003. In Windows Server 2003, you can now configure the maximum amount of data for resource uploading within IIS, but the default limit is too low for MCMS site deployment.
To resolve this problem follow the instructions in the MCMS 2002 SP1 Readme and in the following KB article:
824471 - You may receive an error message when you try to run Site Deployment against an SDO package that is larger than 200 KB
[Back to Top]
Topic: Error message: "Fatal Execution Engine Error" when running SDAPI script in a Terminal Server Window
I have created a VBS script to do site deployment. This script works fine when being executed in a command window on the console of the server machine. But executing it in a Terminal Server session a message box with the following message comes up: “Fatal Execution Engine Error (0x7927c038)”.
Answer
The .NET policy through Terminal Server restricts access to the Microsoft.ContentManagement.Common assembly. To resolve the issue, CSCRIPT.EXE needs to be correctly configured to allow it to use the MCMS assembly from within a Terminal Server session:
- Open Programs\Administrative Tools\Microsoft .Net Framework 1.1 Configuration
- Right click "Application"
- select "Add"
- Click the "Other" button
- Type %systemroot%\system32\cscript.exe in the File name box and press "OK"
- Right click "Configured Assemblies" and click the "Add" button
- Click "Choose Assembly" and select "Microsoft.ContentManagement.Common" assembly and click on the "Select" button
- Click on the Finish button
[Back to Top]
Topic: Error message: "File or assembly name .dll, or one of its dependencies, was not found."
I am seeing this error message "File or assembly name <name>.dll, or one of its dependencies, was not found. (<name> is random)".
Error ID: -2147352567
Source File:
Source Method: NRSiteDeployServer
Description: File or assembly name ifdy1rnx.dll, or one of its dependencies, was not found.
What could be wrong?
Answer
Here are some things to consider:
- This error can occur if the ASPNET account doesn't have permission to write to the WinNT\Temp (system temporary) directory.
- This error can also happen if you run an MCMS application compiled for .NET framework 1.1 on .NET framework 1.0
[Back to Top]
Topic: Error message: "Overflow: 'CDate'"
On one of our MCMS machines, we always get an error upon export and import from Site Manager. The import seems to work, but the report fails.
The report generates the following error:
------------------------------------------
Generated on: Microsoft VBScript runtime error '800a0006'
Overflow: 'CDate'
/NR/System/ClientUI/Report/SDReportInfo.INC, line 47
------------------------------------------
What is making the date conversion fail?
Answer
This can happen when the locale on used by the ASP engine is not the US-English locale. Use the following steps to resolve the problem.
For Windows 2000:
- Add the following regkey according to KB306044
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLEAUT\
VarConversionLocaleSetting = 2 (DWORD)
(you might need to create the OLEAUT key if it does not already exist)
- Control Panel => Regional Options
- On the General tab select "Set default..." and change the language to "English (United States)"
- Restart machine
For Windows Server 2003:
- Add the following regkey according to KB306044
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OLEAUT\
VarConversionLocaleSetting = 2 (DWORD)
(you might need to create the OLEAUT key if it does not already exist)
- Control Panel => Regional and Language Options
- under the "Regional Options" tab change "Standards and Formats" to "English (United States)"
under the "Advanced" tab change "Language for non-Unicode programs" to "English (United States)" and click the apply to "default users and account settings" in advanced tab.
- Restart machine
[Back to Top]
Topic: Error message: "The underlying connection was closed."
Side Deployment fails on my box. In the Event log I see the following message: "The underlying connection was closed." How can I solve this?
Answer
If this problem occurs on Windows Server 2003 with II6 then the problem is most likely a restrictive configuration of IIS. Check out KB 826210 to resolve the issue.
If this does not solve the issue or the problem happens on Windows 2000 then the problem might be a problem in the network connection (e.g. a failure on the network card, a misconfiugred firewall, ...)
[Back to Top]
Topic: Error message: "There is an error in XML document"
I get the following error during a Site Deployment import:
Error Information
An error has occurred that has interfered with the generation of this report. Please try the operation again, and contact your system administrator should this error persist.
Error ID: -2147352567
Source File:
Source Method: NRSiteDeployServer
Source Line: 0
Description: There is an error in XML document (10, 30).
Recommended Action:
Answer
The XML Parser is complaining about an invalid character from the source Server. Check your application log to find the precise location of the System.Xml.XmlException and then search the XML file (open it in Internet Explorer). This will help you find out what the error is and clean the posting.
[Back to Top]
Topic: Error Message: "This request requires buffering data to succeed"
When running Site Deployment import using Site Manager or client-side SDAPI I receive the following error message: "This request requires buffering data to succeed".
What can I do to resolve this problem?
Answer
This problem can occur if anonymous access has been removed from the /NR/System/SdUpload virtual directory in Internet Information Server (IIS).
Please ensure that anonymous access is enabled on /NR and all included subdirectories and also on /MCMS and all included sub directories to allow Site Manager and Site Deployment work correct.
[Back to Top]
Topic: Error when non-administrator executes SDAPI script
When a user that is not a local administrator trys to execute a server-side SDAPI script on the MCMS server machine he gets the following error message:
C:\export-server.vbs(8, 5) AEServerObject.dll: Extended error: [What=''] [LCID='1033'] [SourceFile='nrmetadatakey.cpp'] [SourceFileLine='279'] [DebugInfo=''] [RecommendedAction=''] [ExtraInfo=''] [UniqueErrorId='10004'] [Severity='5'] [Source='AEServerObject.dll'] [CategoryId='0']
Is it required to be a local administrator to do the export?
Answer
No it is not required to be a local administrator. But in order to execute the Authenticate... method in the script it is required that the user running the script has the SeImpersonatePriviledge.
To assign impersonation privileges
- Click Start, click Control Panel, click Administrative Tools, and then click Local Security Policies.
- In the Local Security Settings window, expand Local Policies, click User Rights Assignment.
- In the User Rights Assignment folder, right-click Impersonate a client after authentication, and then click Properties.
- In the Properties dialog box, click Add User or Group.
- In the Select Users, Computers, or Groups dialog box, add the appropriate user or group, and then click OK.
- In the Properties dialog box, click OK.
[Back to Top]
Topic: Exception when using C# SDAPI application in a Terminal server session
When using server side site deployment in my C# application to import an SDO file from inside a Terminal Server session then I get the following result:
Fatal Execution Engine Error (0x7927bb38)
when calling into the CmsDeployImport object.
This works fine when logging on locally to the machine. What's wrong?
Answer
This can be caused by the following reasons:
- The account used had no write access to the %temp% directory
- The .net policy didn't allow the assembly to be used in the TS context.
You have to add the application in the in 'Microsoft .NET Framework 1.1 Configuration' to the trusted applications list.
[Back to Top]
Topic: Export to Object Package filename.sdo failed
I see this Error when I export using Site Deployment: "Export to Object Package <filename>.sdo failed"
Answer
There are multiple reasons for this problem:
- If SQL server and MCMS server are installed on the same box, then ensure that the "shared memory protocol" is disabled in the "SQL client network utility".
- The amount of data or the time required for the export exceeds the limitations set in the ..cmsroot$\server\mcms\web.config:
<httpRuntime executionTimeout="3600"
maxRequestLength="1024000"
useFullyQualifiedRedirectUrl="false"
minFreeThreads="8"
minLocalRequestFreeThreads="4"
appRequestQueueLimit="100"/>
(the settings here are for a one hour timeout and 1 GB data)
[Back to Top]
Topic: How is the node cache affected by database import?
How is the node cache refreshed? For example, if I have all my nodes in the cache, then I make a change (e.g. an import). Is the node cache actively managed? Will MCMS mark the affected nodes as changed?
Answer
The MCMS node cache is a map of node GUIDs to nodes. The nodes at this level are totally independent of each other. A change to one does not impact any others. When a change to a particular node is detected (i.e. an entry in the database change table), the node is tossed out of the cache and is re-read when it is next requested.
When a change to any node is detected, the upper level (output, fragment, etc.) caches are cleared, because we don't know the dependencies involved. For example, what URLs are invalid because of a name or state change, what additional channels have to be added to navigation, etc.
The MCMS server checks for updates in the database once every 6 seconds during normal runtime - and on the start of each session in design time. This way, we can make sure that edits are always occurring with the current data and also prevent production database stress.
[Back to Top]
Topic: Is it possible to export a resource gallery or a template gallery using Site Deployment API?
Is it possible to export a resource gallery or a template gallery using the Site Deployment API?
Answer
The Site Deployment API only can export channels and postings and resources associated to these postings. Images inside a Placeholder on an exported page will be exported but it is not possible to export resources or templates directly.
This can be done using the Site Manager.
[Back to Top]
Topic: Problems with client-side Site Deployment API within ASP.NET
I'm using the client-side Site Deployment API from within an ASP.NET application. When I do this, Internet Information Server (IIS) hangs on me. What could be wrong?
Answer
This has been fixed in MCMS 2002 Service Pack1. You should not experience this problem when MCMS 2002 SP1 is installed.
The issue was that the MCMS 2002 client-side Site Deployment API was not allowed within a service (including IIS or Scheduler Service). The reason for this was that the client-side Site Deployment API used WININET.DLL. This DLL cannot be used within a service.
[Back to Top]
Topic: SDAPI access denied
When using the Site Deployment API (SDAPI) in an ASP.NET application, I cannot import the SDO file. I get an access denied error. The same code works in a console application. What's wrong?
Answer
Here are some things to consider:
- You may be using AuthenticateAsCurrentUser. This will not work in an ASP.NET environment. Instead use the following code:
WindowsIdentity ident = HttpContext.Current.User.Identity as WindowsIdentity;
cmsDeployImport.AuthenticateUsingUserHandle(ident);
- The ASPNET_WP account may not have read access to the SDO file.
[Back to Top]
Topic: Site Deployment created an invalid SDO file
Site Deployment Export does not create a valid SDO file. Instead the file contains HTML code. What could be wrong?
Answer
Here are some things to investigate:
- This will happen if the /NR and /MCMS virtual directories do not have anonymous access enabled or if the phyiscal files and directories behind the /NR and /MCMS directories do not have "everyone read" ACL permissions set.
- Open the "SQL Client Network Utility" and disable "shared memory protocol". Also move "named pipe" to the top of the list of supported protocols.
- Increase the node cache size in SCA. It has been reported that a small Node Cache size can cause this.
- Check that the "rdonlyres" directory within /NR virtual directory is a virtual directory and not a physical folder (the icon needs to be a folder with a small globe in the lower right edge). If it is a physical folder create a new virtual directory below /NR with name "rdonlyres" which points to "\program files\microsoft content management server\server\rdonlyres"
- Check that the /MCMS virtual directory is a web application (the icon needs to be a box with a globe in it)
- Check that the "SiteDeployment" folder in /MCMS is a web application and not a physical folder (the icon needs to be a box with a globe in it).
- Check that a virtual directory named "CMS" exists in the /MCMS web application. Ensure that it points to "\program files\microsoft content management server\server\IIS_CMS" and is a virtual directory (the icon needs to be a folder with a small globe in the lower right edge)
- ensure that the ASPNET account has full control permissions on the TEMP directory and the "rdonlyres" directory within /NR virtual directory.
[Back to Top]
Topic: Site Deployment does not export correctly. No postings are included, only Folders/Channels.
Site Deployment does not export correctly. No postings are included, only folders and channels. What could be wrong?
Answer
Open the "SQL Client Network Utility" and disable "shared memory protocol". Also move "named pipe" to the top of the list of supported protocols.
[Back to Top]
Topic: Site Deployment report does not list the exported items on large exports
When I create a large SDO file with many thousand items the export report does not list the exported content.
How can I correct this problem?
Answer
This is caused by a design limitation in the product. Site Deployment will not list the exported items if the total number of exported items is higher than 10.000.
A workaround would be to ensure that less than 10.000 items are being exported.
[Back to Top]
Topic: The handle is invalid.
I'm receiving the following error message during Site Deployment in Site Manager:
Error: 6001
Description: The handle is invalid.
Severity: 5
Source: aesecurityclient.dll reposturl.cpp 323
Debug info:
Extra info:
Client source: ClmProgress::DoReport
Recommended Action:
What is the solution for this problem.
Answer
- Please check if this problem only occurs to one specific user. Try to logon to your machine with a different user and check if the problem is gone. If yes, then this can be caused by a corruption in the user profile. Please remove the old profile and check if the problem is gone.
- This can also be caused by a timeout happening while doing Site Deployment. Please check out the article discussing Timeouts in this section.
[Back to Top]
Topic: The XML parser could not parse the tag it was given
I see this error message during an SDO Import: "The XML parser could not parse the tag it was given". What could be wrong?
Answer
There are multiple different possible reasons and solutions for this error. Some issues are fixed in CMS 2002 Service Pack 1 - so it is highly recommended to install SP1.
The Site Manager application expects to receive XML messages from the MCMS server. This error generally occurs when the Site Manager receives an HTML error message from the MCMS server. In recent versions of MCMS, this error message was enhanced so that the HTML is included in the error message. Make sure you read this entire error message, it can be your best clue for resolving this issue.
Other things to consider:
- The SDO file being imported may be invalid. This can be checked with WinZip. If Winzip is able to open the SDO file the SDO file should be ok. If the SDO file is invalid check on the exporting machine if the /NR and /MCMS virtual directory has anonymous access enabled (required) and that the physical file behind the /NR and /MCMS directory have "everyone read" ACL rights.
- Memory problems. Increase the virtual memory of the MCMS server.
- Internet Explorer caching issues. Clear the Internet Explorer browser cache, especially the content of the Content.IE5 hidden directory: Delete all files and folders in the \documents and settings\<UserName<\Local Settings\Temporary Internet Files\Content.IE5 directory (including hidden files).
- Clearing the MCMS memory cache often solves this problem.
- Check for permission problems. Check the permissions on the TEMP directory and on the physical files behind the /NR and /MCMS virtual directories on the importing server. Also ensure that anonymous access is enabled on the /NR and /MCMS virtual directory.
- The Microsoft Internet Explorer Webcontrols may not be installed correctly or the wrong version of the Webcontrols are installed. Uninstall the webcontrols and install the version shipped on the MCMS 2002 server CD.
- Ensure that the user doing the import is a MCMS administrator.
- If the MCMS server and SQL server are installed on the same box ensure that shared memory protocol is disabled in the "SQL Client Network Utility". In addition move "named pipe" communication to the top.
- Ensure that the user listed in the ProcessModel section of the Machine.Config file has adequate rights (also read access to the SDO file).
- Ensure that the SQL Server machine has enough per seat licenses configured.
- Check if a web.config and/or global.asax file exist in the root of your web site. Invalid entries in these files might cause this error. Please remove them and test if this solves the problem. If you need these files for other applications, please check all entries and correct the errors.
[Back to Top]
Topic: Timeout when importing or exporting an SDO file.
I'm seeing a timeout when importing or exporting SDO files. Other error messages I have seen in this context are "The handle is invalid.", "General network error" and "The Underlying Connection Was Closed".
Answer
- It is better to use the server side APIs instead of client-side API because you are not subjected to problems associated with going through a web server. The server-side API is a COM API that directly talks to the MCMS server COM object.
- When importing large SDOs through Site Manager or the client-side API, you may run into the problem of the ASP.NET process timing out before the process is complete. To extend the various timeout parameters:
- On the MCMS server, open the machine.config file located in %windir%\Microsoft.Net\Framework\v1.0.3705\CONFIG.
In the <processModel> tag set responseDeadlockInterval from "00:03:00" to "12:00:00" (12 hours timeout for any aspnet_wp process).
- On the MCMS server, open the web.config file located in <MCMS Dir>\server\mcms\sitedeployment.
In the <httpRuntime> tag:
set executionTimeout to "43200" (12 hours timeout for this application)
- If you plan to import a big SDO file, using the Site Manager or the client-side API, configure the following, on the MCMS server machine. This web.config setting controls upload size:
In the tag:
set maxRequestLength = "...", 1024 = 1 Mb, 102400 = 100 Mb. If the SDO is 3Mb in size then use 4096 as the value (4096k > 3 Mb, 4096 = 4 x 1024).
- You may run into the error that the aspnet_wp process uses more than 60% (default) of the system memory at which ASPNET kills the process. This default can be changed by editing the machine.config file at %windir%\Microsoft.Net\Framework\v1.0.3705\CONFIG.
In the <processModel> tag:
set memoryLimit="" “80” = 80% and is a good figure for me.
- If the MCMS server is running on the same system as the SQL server (i.e. the MCMS server is a local “client” of Microsoft SQL Server™):
Adjust the SQL Client Network settings as follows (this is accessible through the “Microsoft SQL Server\Client Network Utility” Start Menu item:
- turn off: “Enable shared memory protocol”
- switch the order of the “Enabled protocols by order” so that “Named Pipes” comes before “TCP/IP”
- restart Microsoft Internet Information Server (IIS)
This cures some “General network error” problems that some have been seeing and some problems with imports failing right when the merge happens.
This also cures problems of the form:
Description = "Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."
Source = ".Net SqlClient Data Provider"
Note: This error occurs regardless of the size of the DB.
- The export initially produces a huge folder in the \server\temp that gets compressed into a smaller SDO file.
Make sure that this temp directory has enough space to contain this folder and the two copies of the file that will be produced (this is explained later). This is hard to estimate but a 500,000 posting MCMS db generates a 253 Mb file which, when uncompressed, consumes about 2Gb. After the file is produced in the temp directory it is moved to the rdonlyres directory where it gets downloaded to the client that performed the export. Make sure that there is room on the server for the copy to succeed (from temp to rdonlyres) and there is room for the client to hold the downloaded SDO file.
A rule of thumb for exporting/importing a huge SDO file would be: = 20 x + 2 x = 22 x . I’ve seen cases where 50x the size of the SDO file must be allocated.
- Sometimes during a large export the Site Manager will timeout, reporting some error in reposturl.cpp. The export is still happening on the server side and eventually the SDO file will be produced in the /nr/rdonlyres directory.
- In IIS the virtual /NR directory must have anonymous access enabled. The physical file folder (located at MCMS install dir\Server\IIS_NR) requires read permissions for 'Everyone'.
[Back to Top]
Topic: "Use channel script with pages" option not persisted
When I try to set the "Use channel script with Pages" setting in Site Manager to "Yes" the change is not persisted. After a refresh the setting has been changed back to "No". What can cause such a problem?
Answer
This can happen if the System Locale on the Site Manager machine is not set to "US-English". Windows Scripting Host uses the System Locale when it genrates the textual representations for "True" and "False". In case the System Locale is set to "Italien" (e.g.) "True" will then be written as "Vero". As Site Manager uses the output from Windows Script when it sends the response to the server "Vero" is send for this setting rather than "True".
As the MCMS server does not expect this response it sets the value to the default value which means that this option remains deactivated.
To resolve this problem please change the System Locale on the Site Manager machine to "US-english".
[Back to Top]
Topic: Cannot logon to Site Manager with SSL
I cannot logon to Site Manager, when SSL is enabled. I get a script error instead.
Answer
Please check if the content expiration settings in Microsoft Internet Information Server (IIS) are set to "expire immediately". This can cause this problem.
[Back to Top]
Topic: Dependent Report not working
The "Dependent Report" function in site manager, does not work on my system. Nothing happens - means the Internet Explorer window that should show the report does not open. How can this be solved?
Answer
This can happen if a popup blocker is installed in Internet Explorer. Please disable the popup blocker. This should solve the problem.
[Back to Top]
Topic: Error Message: "An unexpected error has occured" after installing Windows Server 2003 SP 1
Since we installed Windows Server 2003 Service Pack 1 when opening a property dialog in Site Manager I receive the following error message:
"An unexpected error has occured. Please record and report details to the appropriate administrator."
There are no further details on this error dialog. How can I resolve this problem?
Answer
This can happen when the Data Execution Protection feature (new with Windows Server 2003 SP1 and Windows XP SP2) is enabled.
You would need to add NRClient.exe to the exclude list and to solve this problem.
You will find the option to enable/disable this option or to modify the exception list using the following steps:
Go My Computer – Properties – Advanced tab – Performance Settings button – Data Execution Tab.
[Back to Top]
Topic: Error message: "Could not connect to the Microsoft Content Management Server localhost:80"
I get the following error message when I try to connect to my MCMS web server using Site Manager:
Could not connect to the Microsoft Content Management Server localhost:80. Either the web service is not running, or there are network problems that are keeping you from connecting to the server, or the server is not accessible through MCMS Site Manager.
Answer
Here are some things to investigate:
- Check if your MCMS entry is configured to port 80. If not you need to adjust the port number in the parameter string of your Site Manager shortcut.
- Check if there is a global.asa in the root of your Web site. This global.asa contain errors or settings which interact with MCMS. MCMS does not ship with its own global.asa.
- If you are using the version of Site Manager that ships with CMS 2002 SP1a (or the web download) ensure that the J# redistributable package is installed on the box.
- Ensure that the web site is configured as Read-Write and not as Read-Only entry point in the SCA.
- Try to access http://localhost:80/NR/System/ClientUI/login.asp from Microsoft Internet Explorer and see if you get an error from Microsoft Internet Information Server (IIS). If so, put a test (very simple one; e.g. just say “hello world”) ASP page in \Server\IIS_NR\System\ClientUI\ and try to access it from Microsoft Internet Explorer. If that test page gives the same error, work on the issue as a regular IIS access problem. Then try to open Site Manager again.
- Ensure by checking in IIS MMC if the web site has an application name in the Web site properties.
[Back to Top]
Topic: Error message: "Invalid server id."
When starting Site Manager we receive the following error message:
Error: 0
Description: Invalid server id.
Severity: 5
Source: N/A
Debug info: N/A
Extra info: N/A
Client Source: Login::ctlLogin_Click
Recommended Action: N/A
What could cause this problem?
Answer
There are two known reasons:
- The Site Manager version is different from the Server version (e.g. Site Manager from SP1 and MCMS server on SP1a)
- The user running Site Manager does not have access to this registry key: HKLM/Software/NCompass
[Back to Top]
Topic: Error message: "Key is not unique in collection"
We have a problem when opening the rights property screen for a resource gallery item. We get the following error:
Error: 0
Description: Key is not unique in collection
Severity: 5
Source: ListItems
Debug info: N/A
Extra info: N/A
Client Source: UserRightsList::displayRightsList
Recommended Action: N/A
The event viewer shows this warning:
Event Type: Warning
Event Source: MCMS
Event Category: None
Event ID: 2403
Date: 7/22/2003
Time: 2:06:58 PM
User: N/A
Computer: --------
Description:
Offending SQL:
INSERT INTO NodeRole (IsBeingDeleted, IsBeingUpdated, IsBeingInserted, NodeId, RoleGUID) VALUES (?, 0, ?, ?, ?); INSERT INTO NodeRole (IsBeingDeleted, IsBeingUpdated, IsBeingInserted, NodeId, RoleGUID) VALUES (?, 0, ?, ?, ?); INSERT INTO NodeRole (IsBeingDeleted, IsBeingUpdated, IsBeingInserted, NodeId, RoleGUID) VALUES (?, 0, ?, ?, ?); INSERT INTO NodeRole (IsBeingDeleted, IsBeingUpdated, IsBeingInserted, NodeId, RoleGUID) VALUES (?, 0, ?, ?, ?); INSERT INTO NodeRole (IsBeingDeleted, IsBeingUpd;Violation of PRIMARY KEY constraint 'PK_NodeRole'.
Cannot insert duplicate key in object 'NodeRole'.
Answer
Open one of the User Rights Groups property pages and open the "Group Members" tab.
If you click Modify, you get the screen which lists the domains to select users from.
By selecting the relevant domain and clicking "synchronize", any changes you've made (such as new groups) are synchronized with Site Manager. This needs to be done on all affected Site Manager machines.
If the problem still persists, restart the box after the synchronization.
[Back to Top]
Topic: Error message: "Microsoft Content Management Server 2002 installation not found" when installing SP1
I have a machine where only the downloadable version of Site Manager (Site Manager Refresh) is installed. When trying to install MCMS 2002 Service Pack 1, I get the following error message: "Microsoft Content Management Server 2002 installation not found. The patching process will exit."
How do I install SP1 on a Site Manager Refresh box?
Answer
Follow these steps:
- Uninstall Site Manager Refresh.
- Follow the instructions in the section of the SP1 readme about "Installing Site Manager or Site Stager Without Microsoft VM" to install the RTM version of Site Manager (it won't run but this does not matter as it will be replaced with the version from SP1 in the next step).
- Run SP1 setup.
[Back to Top]
Topic: Error Message: "No mapping between account names and security IDs was done."
When I tried to add a new user to a rights group using MCMS 2002 Standard Edition I received the following error message: "No mapping between account names and security IDs was done."
Answer
Check and remove all accounts listed in all rights group in MCMS which are listed as Type "Unknown". MCMS is not able to idenitfy that this specific account is an user or a group.
[Back to Top]
Topic: Error message: "Run-time error '91' - Object variable or With block variable not set"
It tried to do a change in Site Manager and received the following error "Run-time error '91' - Object variable or With block variable not set". What could be wrong?
Answer
This can happen if there are any problems on SQL server - e.g. if the Transaction log is full. Please verify if there are any error in the event log on SQL server.
[Back to Top]
Topic: Error message: "SQL Server does not exist or access denied"
I have configured my SQL server connection with named-pipe protocol and SQL authentication. When I now try to start Site Manager I get the following error message:
The List of domains is not available due to the following error: SQL Server does not exist or access denied. ConnectionOpen (Connect()). Invalid connection string attribute.
When I reconfigure the SQL client to use TCP/IP everything works fine. Only named-pipes seem to be affected. What can I do to resolve this?
Answer
In Windows Server 2003 anonymous access for named pipes is disabled per default. This means the SQL server will only accept authenticated named-pipe connections. On the client side the MCMS server is running in the context of the MCMS system account. So it is required that the MCMS system account can be validated on the SQL server machine.
If the SQL server machine is in a different domain or if the machines are in a workgroup environment, then the SQL server is not able to validate the MCMS system account and the named-pipe connection cannot be established.
As a solution either use a domain account as MCMS system account that can be authenticated on both machines or create a local account with identical name and password on the SQL server machine. This will ensure that the SQL server can map the MCMS system account from the MCMS server machine to the idenical named local account on the SQL server machine.
[Back to Top]
Topic: Error message: "The Microsoft Content Management Server proxy component is not correctly installed"
When I run Site Manager on my machine, this is what I see:
“The Microsoft Content Management Server proxy component is not correctly installed.”
When I click the details button, I get this:
Error: File or assembly name vjslibcw, or one of its dependencies, was not found.
Source: Login::ctlLogin_Click
Answer
This error can happen when the J# redistributable for the latest installed .NET framework version is not installed on the box. For example if .NET framework 2.0 has been installed on the box but the J# redistributable for .NET 2.0 has not been installed.
Another reason might be a incorrectly installed J# redistributable. Please install/reinstall the J# redistributable for all .NET framework versions installed on the affected box.
The J# redistributables can be downloaded from the following location: http://msdn.microsoft.com/vjsharp/downloads/howtoget/default.aspx
[Back to Top]
Topic: Error message: "The object invoked has disconnected from its clients"
When modifying a rights group in the Site Manager I get the following error message.
Error: 0
Description: Automation Error: The object invoked has disconnected from its clients
Severity: 5
Source: AdmnTool
Client Source: OEFUsers::HandlePropDlg
How can I resolve this problem?
Answer
This can happen when the Data Execution Protection feature (new with Windows Server 2003 SP1 and Windows XP SP2) is enabled.
You would need to add NRClient.exe to the exclude list and to solve this problem.
You will find the option to enable/disable this option or to modify the exception list using the following steps:
Go My Computer – Properties – Advanced tab – Performance Settings button – Data Execution Tab.
[Back to Top]
Error: 6001
Description: The system cannot find the file specified.
Severity: 5
Source: aesecurityclient.dll reposturl.cpp 191
Debug info:
Extra info:
Client Source: Login::ctlLogin_Click
Recommended Action:
Answer
This error message indicates a problem with your Internet Explorer installation. Please reinstall Internet Explorer 6 SP1.
[Back to Top]
Topic: Error message: "Token too Large for current BLOB SIZE"
I see this error when I login to Site Manager: "Token too Large for current BLOB SIZE".
Event log:
Error: 0
Description: Token that will be generated is too large for current BLOB SIZE.
Severity: 5
Source: N/A
Debug info: N/A
Extra info: N/A
Client Source: Login::ctlLogin_Click
Recommended Action: N/A
Answer
This is a known bug. A fix for this is scheduled for MCMS 2002 SP1.
A workaround to bypass this problem is to not use the login as current user option. Manually login to Site Manager using your username, domain and password.
[Back to Top]
Topic: Error when uploading files to the resource gallery
We are not able to upload new resource gallery items to the resource gallery using Web Author or using Site Manager.
In Web Author we get the following error message: "Object reference not set to an instance of an object."
In SiteManager we get the followng error message:
Error description: (0x80020009)
Extended error: [What='The system cannot find the path specified.(3)'] [LCID='1033']
[SourceFile='javascript:void(null);']
[SourceFileLine='187'] [DebugInfo='javascript:void(null);']
[RecommendedAction=""] [Extralinfo=''] [UniqueErrorId='5001'] [Severity='5'] [Source='']
[CategoryId='0']
What can cause this problem?
Answer
The error message details indicate a problem with the path in the following registry key:
HKLM\SOFTWARE\NCompass\Resolution Content Server\Configuration\ResolutionTempFolder
This key is either pointing to a non-existing location or the permissions on this directory have been tightend.
The required permissions on the folder where this registry is pointing to are as follows:
- Administrators group (FULL)
- CMSSystem (FULL)
- Everyone (FULL)
- System (FULL)
[Back to Top]
Topic: How do I define a channel rendering script which takes parameters?
I would like to define a channel rendering script that take parameters. But Site Manager rejects URLs in the format: <b>redirect.aspx?url=/section2/AnotherItem</b>.
Answer
This is a known issue with the script URL field in the channel rendering dialog box. But there is a workaround. You can create a custom channel property which can hold the parameters.
In the channel rendering script you need to extract these parameters using
string param = CmsHttpContext.Current.Channel.CustomProperties["RedirParams"]
[Back to Top]
Topic: Navigation URL
I'm confused about the Channel Rendering options. There’s a Script URL setting, which I’m sure is for the channel rendering script. But there’s also a Navigation URL setting what is this for?
Answer
The Navigation URL is a deprecated property. It is retained in MCMS 2002 only so that MCMS 2001 sites that used “framed navigation templates” could be migrated to MCMS 2002. Any new channel (or channels that are upgraded to ASP.NET) do not need to use this property.
[Back to Top]
Topic: New objects added in SiteManager get renamed to "Untitled"
I'm running MCMS 2002 SP1 and have encountered problems when creating (channels/resources) in Site Manager. The object loses it's properties when created.
The name defaults to "Untitled", custom properties disappear and other properties that I set for the object return to their defaults.
The loss of properties don't show in Site Manager unless you refresh the object but if I make edits using the web author the properties are saved.
Is there a solution for this problem?
Answer
This problem can occur when the SQL server settings do not allow nested triggers (triggers fired by other triggers).
To change this
- right click on the SQL server in Enterprise Manager and choose properties
- Open the "Server Settings" tab
- Ensure that the "Allow triggers to be fired which fire other triggers (nested triggers)" is enabled.
[Back to Top]
Topic: Problems with SiteManager after installing Windows XP Service Pack 2
I have installed Windows XP Service Pack 2. When I now start Site Manager I receive the following error message:
Error: 20076
Description: The client is unable to connect to the server because the client's version is incompatible with the server's version. Please make sure your client is connecting to a server with a compatible version.
Severity: 5
Source: Source: AEStubObject.dll aestub.cpp 605
Debug info: The client Version 5.0 (build 5.0.4484.0) currently is not compatible with the server Unknown (build Unknown)
Extra info: No further information is available
Client Source: Login::ctlLogin_Click
Recommended Action: Please make sure your client is connecting to a server with a compatible version.
In addition the event log shows the following error messages:
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10016
Date: 23/03/2004
Time: 5:35:40 PM
User: machinename\IUSR_machinename
Computer: machinename
Description:
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {0040D22F-54A1-11D1-9DE0-006097042D69}
to the user machinename\IUSR_machinename SID (S-1-5-21-1715567821-1580818891-854245398-1005). This security permission can be modified using the Component Services administrative tool.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
What is wrong?
Answer
Windows XP Service Pack 2 changes some security settings to increase security for your system. One of these increased settings interacts with the way MCMS works in a way that it prevents a COM component from being activated.
To resolve this you need to apply the following changes:
Open Component Services, drill down to My Computer, right click and select Properties.
On the COM security tab, select Edit Default... for Launch and Activation permissions
Give the Internet Guest User Account (IUSR_...) Launch and Local Activation permissions.
[Back to Top]
Topic: Request too big on channel with many postings
Clicking on a channel which contains many postings (hundreds) I get the following error message:
Error: Extended error: [What='The XML parser could not parse the tag it was given.'] [LCID='1033'] [SourceFile='aegrammarparser.cpp'] [SourceFileLine='310'] [DebugInfo='Request is too big'] [RecommendedAction=''] [ExtraInfo=''] [UniqueErrorId='1002'] [Severity='5'] [Source='GrammarParserC.dll'] [CategoryId='0'] Source: AeCliCmn::refreshTreeBranch
Answer
Site Manger code contains a limit of 100KB for every request. But you can change this limit. Change the constant or remove the check from this file: \program files\microsoft content management server\server\iis_nr\system\marshalling\resstub.asp
Modify or remove these lines:
if nCount > 100000 then
Response.Write "Request is too big"
Response.End
End if
If this problem occurs while starting Site Manager, also check the deleted items folder. A huge amount of items in this folder can cause the same problem.
[Back to Top]
Topic: Site Manager shows up in tabbed view rather than full screen
In Site Manager the right most pane is not in full size but appears in tabbed view with three tabs labeled as Tab1, Tab2 and Tab3. What can cause this problem?
Answer
This can happen if a wrong version of the vsocx6.ocx file is registered on your system.
Please search for all instances of this file on your disk (most likely it will be in c:\windows\system32).
To solve this problem
- Unregister the wrongly registered vcocx6.ocx by opening a CMD prompt, and
run
REGSVR32 /u C:\WINDOWS\system32\Vsocx6.ocx
(adjust the path as necessary)
- Rename C:\WINDOWS\system32\vsocx6.ocx to C:\WINDOWS\system32\vsocx6.xxx
(adjust the path as necessary)
- See if C:\Program Files\Microsoft Content Management Server\Client\vsocx6.ocx exists
- If it does, open a CMD prompt and run
REGSVR32 C:\Program Files\Microsoft Content Management Server\Client\vsocx6.ocx
Now start Site Manager again and check if the problem is solved.
- If the file does not exist, uninstall SM and reinstall.
Verify that the file is installed and correctly registered and run Site Manager to see if the problem is resolved.
[Back to Top]
Topic: Site Manager: xxxxxx is not a valid user or group in domain
Error: xxxxxx is not a valid user or group in domain WinNT://xxxxxxxx when adding users in Site Manager.
Answer
The MCMS System Account has to be able to enumerate the members of the domains you are adding. So if you want to add DOMAIN\USER to your administrator group, for example, your MCMS System Account user has to be the member of a domain that DOMAIN trusts (ideally a member of DOMAIN itself).
You can change your system account using the Server Configuration Application (SCA). You can also add supported domains in the SCA.
[Back to Top]
Topic: Valid users cannot logon to Site Manager on Windows XP
Valid users cannot logon to Site Manager on Windows XP.
Answer
This is due to a security Option in the Local Security Settings:
"Network access: Sharing and security model for local accounts" was set to "Guest only - local users authenticate as Guest" instead of "Classic - local users authenticate as themselves.
Change the local security setting "Network access: Sharing and security model for local accounts" of the Windows XP machine to "Classic - local users authenticate as themselves"
To correct this setting:
- Open the MMC using "Start" - "Run..." - "MMC.EXE"
- Open the "Add/Remove Snap-in" dialog using "File..." - "Add/Remove Snap-in"
- Click "Add..." on the "Add/Remove Snap-in" dialog
- Select "Group Policy" in the "Add standalone Snap-in" dialog and click the "Add" button
- Click the "Finish" button in the "Select Group Policy Object" dialog
- Click the "Close" button on the "Add standalone Snap-in" dialog
- Click the "OK" button on the "Add/Remove Snap-in" dialog
- Expand "Local Computer Policy"
- Expand "Computer Configuration"
- Expand "Windows Settings"
- Expand "Security Settings"
- Expand "Local Policy"
- Click on "Security Options"
- In the right pane change the option "Network access: Sharing and security model for local accounts" to "Classic - local users authenticate as themselves"
[Back to Top]
Topic: Changing the value of the Site Stager maximum broken links
How can I change the value of the maximum broken links when I run the Site Stager?
Answer
This can be changed in the registry:
[HKLM]\SOFTWARE\NCompass\Staging Server\MaxBrokenLinks: STRING
(Maximum broken allowed when staging, create manually, default = 10)
Note: make sure that you backup your registry before you make any changes.
[Back to Top]
Topic: Why do I get so many broken links when staging my site in Site Stager?
Why do I get so many broken links when staging my site in Site Stager?
Answer
If you want to troubleshoot why you are getting broken links do the following:
- Open the Site Stager log and find a broken link to a posting. There are three URLs in the error message: GUID based URL of where link was found, GUID based URL of what Site Stager was requesting, and Hierarchical URL of what Site Stager was requesting.
- Open a Web browser and log into the MCMS site with the 'StageAsUser' account.
- Paste the GUID based URL into the browser. A lot of times you will see that you will get a script error or some other 500 error, that might give you some insight into what is going on.
Another way of doing the above, is to find a posting that is getting a broken link error message.
- Log into the Site Manager with the using the 'StageAsUser' account.
- Navigate to this posting, and preview it.
- Hit Ctrl-N to open the same previewed posting in a new browser. This will open a new window with the address bar visible.
- Change NRMODE=UnPublished to NRMODE=Staging.
This will also show you what is going on.
What we have also noticed is that after SRP1 has been installed, Subscriber only 'StageAsUser' account cannot stage the site. There is no fix for this, the workaround is make the 'StageAsUser' a Template Designer (or Administrator).
[Back to Top]
Topic: Accessing a MCMS Web site different from the Default Web site
How can I configure Microsoft® Visual Studio® .NET to access a MCMS Web site that is different from the Default Web Site?
Answer
First of all: Microsoft officially only supports the Default Web site to be used with VS.NET and the MCMS developer tools. But there is a method to get it working for different Web sites.
It is required that the Web site you are trying to access has a unique port. No other Web site (independend if started or not) must have the same port number.
In addition you need to modify the 'InstanceID' in your DeveloperTools.xml file located at C:\Program Files\Microsoft Content Management Server\DevTools. This number should correspond with the entry point of your Web site in Internet Service Manager.
<CMSENVIRONMENT>
<SERVER BaseUrl="http://localhost" InstanceId="1" />
<TEMPLATE QueryString="" />
</CMSENVIRONMENT>
To determine this number have a look in the registry. There is a key for every entry point below
\HKLM\SOFTWARE\NCompass\Resolution Content Server\Configuration\0\EntryPoints.
Also ensure that the MCMS Web site has a unique port that is not being used by any other Web site. The MCMS developer tools will try to create necessary virtual directories on the first Web site with the given port and ignore the 'InstanceId'. This also happens if the other Web site is stopped.
[Back to Top]
Topic: Application for project type .csproj is not installed
After installing the WoodgroveNet sample (which installed successfully), I attempted to open the project in Visual Studio. I was told that 'The application for project http://localhost/woodgrovenet/woodgrovenet.csproj is not installed. Make sure the application for the project type (.csproj) is installed.'
I click OK and get 'The application for project 'C:\Program Files\ Microsoft Content management
Server\Sample Data\McmsWebControlLibrary\McmsWebControlLibrary.csproj' is installed. Make sure the application for the project type (.csproj) is installed.'
What's the problem here?
Answer
Please check if you installed C# support when you installed Visual Studio .NET. You may have just installed VB.NET support.
[Back to Top]
Topic: Developertools.xml not found
Whenever I start Microsoft® Visual Studio® .NET 2003 I receive the following error message: "Developertools.xml not found".
Answer
This can happen when 3rd party Microsoft Visual Studio .NET add-ins are installed.
To confirm whether the problem is caused by one of these, deactivate all 3rd party add-ins.
[Back to Top]
Topic: Error Message: "Cannot MCMS-enable a project that is on a remote computer"
I am using Content Management server 2002 (SP1a installed) with Visual Studio .NET. While creating a new MCMS Web project I receive the following error message: "The 'New MCMS server project' operation failed because the following preconditions were not met: - Cannot MCMS-enable a project that is on a remote computer".
How can I solve this?
Answer
This can happen if you did not use a Url with the host name "localhost" when creating the project. The developer tools are only supported with the default web site running on port 80.
Different web sites and ports can be used - although not officially supported - if the port is unique.
To use a different Web site than the default web site you need to modify the 'InstanceID' in your DeveloperTools.xml file located at C:\Program Files\Microsoft Content Management Server\DevTools. This number should correspond with the entry point of your Web site in Internet Service Manager.
<CMSENVIRONMENT>
<SERVER BaseUrl="http://localhost" InstanceId="1" />
<TEMPLATE QueryString="" />
</CMSENVIRONMENT>
To determine this number have a look in the registry. There is a key for every entry point below:
\HKLM\SOFTWARE\NCompass\Resolution Content Server\Configuration\0\EntryPoints.
[Back to Top]
Topic: Error message: "Could not get the root template gallery"
Error when using MCMS Template Explorer: "Could not get the root template gallery".
Answer
Here are some things to consider:
- The Web application is not located on the local Microsoft Visual Studio® .NET server. The developer tools can only access the local MCMS server.
- The user running Microsoft Visual Studio .NET is not in a Template Designer role or their role does not have access to the root template gallery.
- Check the details of the error message text for further hints. E.g. it can contain the message 'The CMS Server license has expired'. If this happens for a non-eval edition of MCMS then this indicates a problem when reading the registry. This can be caused by permission problem when accessing the registry. Please check the permissions on the \HTKLM\Software\NCompass registry key.
- On Windows Server 2003 or with Windows 2000 SP4 ensure that the user running Visual Studio .NET has the "Impersonate a client after authentication" privilege.
[Back to Top]
Topic: Error message: "This operation requires the context of a Posting"
I am trying to follow the "Using Visual Studio .NET to Create a MCMS Web Site" article from the MCMS help file. When I test the site I receive the following error:
This operation requires the context of a Posting. The request must have a valid Posting Url or QueryString so that the CmsHttpContext.Posting will not be null.
Answer
MCMS template files cannot be executed on their own. They need to be executed in the context of a posting (as indicated in the error message).
To create a posting, login and then browse to the channel you want to create a posting. You should see a "Switch To Edit Site" link on the cover page. After clicking this link you will find a "Create New Page" link. This will allow you to pick the template from the template gallery and create a new posting based on this template.
[Back to Top]
Topic: RobotMetaTag
What is the MCMS 'RobotMetaTag' and why should I add it to my template?
Answer
The RobotMetaTag does the following two things:
- Renders a META tag specifying the robot directives (INDEX, FOLLOW, NOINDEX, or NOFOLLOW) matching the settings in the page properties dialog for the posting.
- Renders a BASE tag with an href that is the entire path and querystring for the template ASPX file. This causes Microsoft Internet Explorer to resolve relative links based on the template file’s virtual location instead of the perceived address in the browser address bar (which changes between edit and live mode). This behavior can be turned off by adding the “RenderBaseHref=False” to the RobotMetaTag server control tag, but the index and follow meta tags are always printed out, even when the RenderBaseHref is turned off.
It is not necessary if both of the following are true:
- You have no need for robot meta tag directives.
- You have no links to images or script files which have a source specified as a link relative to the template file (e.g. a file in your Microsoft Visual Studio® .NET project). This also applies, to links pointing to named anchors within the page (e.g. #faq).
[Back to Top]
Topic: Virtual directory "CMS" cannot be created
I have created a new Visual Studio .NET project and I am trying to enable it as a MCMS project. I am getting this error:
---------------------------
Microsoft Development Environment
---------------------------
Could not create virtual directory 'http://localhost/project/CMS' in location C:\Program Files\Microsoft Content Management Server\Server\IIS_CMS\.
---------------------------
What could cause this problem?
Answer
Here are some things to investigate:
- Ensure that the project path in Visual Studio .NET to the Web site is http://localhost/projectname (not http://localhost/projectname/). No other name is supported since only local Web sites can be enabled as MCMS projects.
- Ensure that the Web site you are using has a unique port. This includes Web sites that are stopped.
- Ensure that the DeveloperTools.xml has the correct port and 'InstanceId' for the Web site configured.
[Back to Top]
Topic: Visual Studio .NET 2003 and .NET Framework 1.1 support
I tried using MCMS 2002 with Microsoft Visual Studio® .NET 2003 and .NET Framework 1.1 but ran into errors.
Answer
MCMS 2002 RTM does not support Microsoft Visual Studio .NET 2003 and/or .NET Framework 1.1.
Support for Microsoft Visual Studio .NET 2003 and .NET Framework 1.1 is added with MCMS 2002 Service Pack 1.
To install MCMS 2002 with Visual Studio .NET 2003 follow the hints below:
- install MCMS 2002 Server component only (no Developer Tools, no Site Manager, no Site Stager)
- install MCMS 2002 Service Pack 1
MCMS 2002 SP1 will give you the option to install updated versions of Site Manager, Site Stager and the Developer Tools.
[Back to Top]
Topic: Visual Studio .NET 2003 not recognized
I currently have Microsoft® Visual Studio® .NET 2003 installed. I am trying to install MCMS 2002 but I keep receiving the following error message:
"Microsoft Visual Studio .NET not found (needed by Dev Tools)"
Answer
Microsoft Visual Studio .NET 2003 is not recognized by the MCMS 2002 installer because this product was not out when MCMS 2002 was released. Microsoft Visual Studio .NET 2003 support is added with MCMS 2002 SP1.
To get around this problem do the following:
- Install MCMS 2002 server component only (no Site Manager, no Site Stager, no Developer Tools)
- Install MCMS 2002 SP1. The SP1 install will give you the chance to install updated versions of the above components including Microsoft Visual Studio .NET 2003 support.
- or -
Install MCMS 2002 SP1a. After installing this service pack use Control Panel - Add/Remove Programs - Select MCMS in the list - use the change option to install the missing components now.
[Back to Top]
Topic: Visual Studio .NET hangs on project creation
When I try to create a new MCMS template project in Microsoft® Visual Studio® .NET project Microsoft Visual Studio .NET (DEVENV.EXE process) hangs indefinitely.
What might cause this?
Answer
This can happen when Microsoft Visual Studio .NET Analyzer is turned on under Administrative Tools, Data Sources (ODBC), Tracing
Alternatively you can check if the following registry key is set to 1 in the current user profile:
[HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\ODBC]
"Vista"="1"
To resolve this stop Microsoft Visual Studio .NET Analyzer using the button in Administrative Tools, Data Sources (ODBC), Tracing tab.
Alternatively you can resolve it by setting the above registry key value to “0”
[Back to Top]
Topic: "400 Bad Request" when switching to live mode
We experience problems when switching from edit mode to live mode. In the browser a "Page cannot be displayed" error shows up and in the IIS log a 400 bad request is listed.
This only happens if we use a http module to do a redirect to the friendly URL when being in published mode.
How can we correct the problem?
Answer
To resolve this you need to increase the UploadReadAheadSize in the metabase. The default value is 48 KB.
To increase the UploadReadAheadSize to 512 KB use the following command:
cscript.exe adsutil.vbs SET /W3SVC/UploadReadAheadSize 512000
Usually the adsutil.vbs file can be found following location: c:\inetpub\AdminScripts
[Back to Top]
Topic: "Switch to Edit Mode" link is not visible on the channel cover page
I have tried to create new postings in my channels but the cover page does not contain the "Switch to Edit Mode" link. What's wrong?
Answer
Here are some things to consider:
- Ensure that you are authenticated. The "Switch to Edit Mode" link will only occur for authenticated users with at least Author rights.
- If you have WoodgroveNet installed then you may be seeing the 'Homeport' instead of the default cover page. This page does not contain the "Switch to Edit Mode" link. To correct this do the following:
- Open Site Manager
- right-click the channel and select "Properties"
- open the "Publishing" tab
- click the "Select..." button in the "Channel Rendering" section
- Clear the "Script URL" entry field
- Click "OK" to close the "Select Channel Rendering" dialog
- Click "OK" to close the Channel Properties dialog
[Back to Top]
Topic: 401 when creating a new page in Webauthor
When I try to create a new posting I receive authentication prompts asking for credentials. This happens after I successfully selected the template from the template gallery. Whatever credentials I enter they are not accepted.
In the Internet Information Server (IIS) log I can see a 401 for "/NR/exeres/..."
What could be causing this problem?
Answer
This can happen if the ASPNET account (IIS 5) or the account assigned to the IIS application pool running the MCMS application (IIS 6) does not have the 'SeImpersonatePriviledge'.
Usually, this happens if MCMS is installed after SP4 on Windows 2000 or if the application pool account is set to a non standard account.
On Windows 2000 domain controllers with .NET Framework 1.1 the default account is not the ASPNET account but the IWAM_<machinename> account. So this priviledge needs to be assigned to the IWAM_<machinename> account.
A solution regarding how to assign this priviledge is provided in the MCMS 2002 SP1 Readme file.
[Back to Top]
Topic: 403.1 when creating a new page in Webauthor
I tried to create a new page using one of my templates. After selecting the template in Web Author, I immediatelly received a "HTTP 403.1 Forbidden: Execute Access Forbidden" error. How can I resolve this?
Answer
This can happen when the TemplateFile property of the Template Definition in MCMS does not point to a valid template file. Please double check that the path stored in this property is pointing to a valid Template File.
[Back to Top]
Topic: Alternative for HtmlPlaceholderControl
Is there a version of the HTML placeholder control shipped with MCMS 2002 which allows HTML editing with other editors?
Answer
A 3rd party product often referenced is the Ektron HTML/XML Editor: http://www.ektron.com/mscms.cfm.
Check the MCMS partner page for more MCMS partners.
[Back to Top]
Topic: Authentication prompt when trying to access the server by name and not by IP
I have a running MCMS site on http://localhost/Intranet using Windows integrated authentication. It also works when I request http://127.0.0.1/Intranet and http://192.168.0.xxx/Intranet. But strangely, when I put host name mapping in C:\WINDOWS\System32\drivers\ect\hosts like:
127.0.0.1 intranet
I suddenly get a dialog requiring me to authenticate, when I request http://intranet/Intranet. Using Microsoft® Internet Explorer 6, every attempt to authenticate with that dialog fails.
My ultimate goal is to have the intranet host header to map on the /Intranet MCMS channel, this is not a problem, but I really want to be able to log in (at all, but preferably automatically).
I'm using MCMS 2002 on a WinXP Pro machine. What can be done to resolve this problem?
Answer
This can happen in certain situations if Internet Explorer tries to use Kerberos authentication. See the following article on how to resolve this:
294382 - Authentication may fail with "401.3" Error if Web site's "Host Header" differs from server's NetBIOS name
[Back to Top]
Topic: BaseAction ActionJavaScript
I'm trying to develop an Edit Console control to launch a new window. I inherited from the BaseNewWindow control, but it keeps telling me I didn't implement ActionJavaScript.Get. However, no where in the class structure does it stipulate MustInheirt. When I do overload the property (ActionJavascript), I now have to supply the javascript code. Not a big deal, but it virtually eliminates any benefit of inheriting from the base class.
Answer
ActionJavascript is defined as: public abstract string ActionJavascript { get; }
It is on the BaseAction class, which is a parent class of BaseNewWindow. The "abstract" modifier on the method in C# is equivalent to "MustOverride" for VB.NET. The "MustInheirt" VB.NET modifier is for classes, equivalent to the "abstract" modified for classes in C#.
So the class structure does mandate that any sub-class of BaseNewWindowAction must implement ActionJavascript get. Generating some javascript to launch a window is the primary use case of a "NewWindow" action.
[Back to Top]
Topic: Change token
When I tried to change the expiry date on a page I saw this error:
Microsoft Content Management Server
Error has occurred
Invalid change token. The current object data does not match the data associated with the given change token.
Answer
The change token is used to detect collision. The error you saw typically occurs if the content or the properties of the page has been changed by another person. Generally this is before you save your changes, but after you launched the Page Properties dialog.
One known issue is that you may have a stale cached version of the dialog. The solution is to ensure that the Microsoft® Internet Explorer option for "TemporaryInternetFiles > Settings... > CheckForNewVersionOfAPage" is not set to "Never". "Automatic" is the default setting and will avoid caching these dialog pages.
[Back to Top]
Topic: CmsAuthorizationModule missing in web.config
When saving a page I get the following error message in the error console:
Save Placeholder Failed
-----------------------------------------------------------
Error Details:
The current user does not have rights to edit the requested item. If you are seeing this exception when a MCMS template is executing, it means that you have removed the CmsAuthorizationModule from the HttpModules section of your web.config. You can only remove this module if: 1. All requests for every MCMS template in the web application will only be accessed by anonymous users 2. Guest access is enabled in MCMS (via the SCA) 3. The MCMS guest user has access to all postings based on templates in the web application If any of these requirements are not met, you MUST register the CmsAuthorizationModule in your web.config.
-----------------------------------------------------------
I checked my web.config files and the CmsAuthorizationModule is listed there. What could be the problem?
Answer
Although the error message indicates a missing authorization item in the web.config file, this is not the case. The error actually occurs when the editor is saving a page and is validating the contents of the placeholders and the template. If any invalid resources are referenced, the above "Save Placeholder Failed" error appears.
Typical scenarios for invalid resources include:
- A resource is added to the resource gallery, and a link to the resource is successfully added to a posting. Later the resource is deleted. When the page is next edited, the link to the now missing resource is invalid.
- An editor adds a link to a resource stored in a resource gallery. Then the editor's access rights to the gallery are removed. Next time when editing the page, the editor would get the above error, because the link would appear invalid.
- The author has only subscriber rights to the template gallery but not editor rights.
How to recognize invalid links?
In order to find out which link is invalid, the editor must go to the page in live mode, and click each of the links. If the link is valid, it works. If the link is not valid, either a "Page can not be displayed" error message is displayed (or the system will ask for username and password - as in error 2 above). It is also possible to write a script to crawl your MCMS pages looking for broken links.
Why can the administrator save the page on behalf of the editor?
When a resource is deleted from the resource gallery, the physical item is still in the database. However, it is no longer associated with a resource gallery. As resources are accessed with a GUID based link, the access to the item is possible but it is no longer possible to access the information about which users are allowed. This information is stored in the resource gallery. But as the item no longer belongs to a resource gallery the currently user cannot be verified. MCMS Administrators on the other hand, have access to all items. This means that no access check is done. This means that administrators also have access to deleted items which have not yet been removed from the database (during background processing). Therefore, when an administrator saves a posting, the placeholder content seems valid, and the save is successful. This is true as long as the resource has not been deleted from the database by background processing.
What must the author do when getting this error?
The editor cannot easily check for invalid links in edit mode, therefore it is best to open the page in another window and click each of the links. Once an invalid link is detected, he must go back to the edit page and remove the link.
[Back to Top]
Topic: Creating internal anchors
I want to create an internal anchor link inside my page. How do I do this?
Answer
Here is an example of how to do it in an HTML placeholder.
Step One: Create the internal anchor point
1. click inside the placeholder and select some text
2. click the 'Edit Hyperlink' icon on the Microsoft® Internet Explorer toolbar
3. under the 'Define as Internal Anchor Point' section, enter the name in the 'Name' box (e.g. name)
Step Two: Create the internal link
1. click inside the placeholder and select some text
2. click the 'Edit Hyperlink' icon on the Microsoft Internet Explorer toolbar
3. in the 'Hyperlink Address' box enter the name with a '#' sign before it (e.g. #name)
[Back to Top]
Topic: Error message about missing reference to "Microsoft.Web.UI.WebControls"
When I select "Create New Page" from the console, I get the following error:
Compiler Error Message: CS0011: Referenced class 'Microsoft.ContentManagement.WebAuthor.BaseTree' has base class or interface 'Microsoft.Web.UI.WebControls.TreeView' defined in an assembly that is not referenced. You must add a reference to assembly 'Microsoft.Web.UI.WebControls'.
Any ideas on what's wrong?
Answer
Ensure that in the assemblies section in the web.config file the following entry exists:
<add assembly="Microsoft.Web.UI.WebControls, Version=1.0.2.226, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
[Back to Top]
Topic: Error message: "'1' is not a valid identifier."
I get the following error message when I try to create a new posting based on one of my templates:
Server Error in '/TestTemplate' Application.
Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.
Parser Error Message: '1' is not a valid identifier.
Source Error:
Line ...: <FORM id="1" method="post" runat="server"></FORM>
Answer
The name in the form tag is the same name as your template file. You must not name your template with a number (without preceding the number with a letter).
[Back to Top]
Topic: Error message: "A potentially dangerous Request.Form value was detected from the client"
I get "A potentially dangerous Request.Form value was detected from the client" when saving a new page. What's going wrong?
Answer
The reason for this is that the Web Author posts HTML data to the server. HTML data posted to a Web server can potentially contain dangerous content. The .NET Framework 1.1 checks for this case. But the .NET framework does not know that MCMS expects the Web Author to send such content. This causes the error.
You need add the tag validateRequest="false" to your web.config. This will disable the check:
<configuration>
<system.web>
<pages validateRequest="false" />
</system.web>
</configuration>
For more details refer to the ASP.Net Web site.
If you don't like the idea to enable this for the whole web application, then you can also set this value to false in the web.config and only disable request validation on the templates that contain HtmlPlaceholderControls using the following page directive:
<%@ Page validateRequest="false" ...>
[Back to Top]
Topic: Error message: "File or assembly name <name>.dll, or one of its dependencies, was not found."
I am seeing this error message "File or assembly name <name>.dll, or one of its dependencies, was not found. (<name> is random)".
Error ID: -2147352567
Source File:
Source Method: NRSiteDeployServer
Description: File or assembly name ifdy1rnx.dll, or one of its dependencies, was not found.
What could be wrong?
Answer
Here are some things to consider:
- This error can occur if the ASPNET account doesn't have permission to write to the WinNT\Temp (system temporary) directory.
- This error can also happen if you run an MCMS application compiled for .NET framework 1.1 on .NET framework 1.0
[Back to Top]
Topic: Error message: "Invalid Mode for Update" when saving new page
When I try to save a new page, I see this error message:
Save new Page failed.
Error Details: Invalid Mode for Update. The requested action modifies the state of an object and can only be performed when the session is in 'Update' mode.
Answer
Here are some things to consider:
- Check if the template is in the root of the Web site. It should be in a separate web application.
You should not create a template project with http://localhost but with http://localhost/application
If you create a template project in the root then the web.config file and global.asax reside here: http://localhost/web.config
This will mean that this web.config will interact with the web.config in the /MCMS directory (http://localhost/MCMS/web.config)
- Ensure that the template is not named "Default.ASPX".
[Back to Top]
Topic: Error message: "Object doesn't support this property or method" when saving new posting
I have a problem creating a new page in the Web Author. After putting in the page name and clicking "OK" I get the following javascript error: "Object doesn't support this property or method" and the new page dialog window does not close.
What could cause this?
Answer
This can happen if a <FORM> tag is included in the template. ASP.NET automatically adds a <FORM> tag to ASPX pages. Pages can only contain one <FORM> tag.
Right click on the page in authoring mode and click "View Source". Search in the source code for "<FORM". If there is more than one tag, you will need to remove the extra ones.
[Back to Top]
Topic: Error message: "Specified cast is not valid" when opening a page
Error Message: "Specified cast is not valid" when opening a page in the Web Author. The page contains custom placeholder controls (e.g. DropDownPlaceholderControl).
Answer
This is a problem with the Viewstate data and a dynamically changing control tree.
When there are postbacks between different modes (which there are for a ReEdit event but not for a NewPage event), there can be issues with repopulating the viewstate. When this happens, exceptions like this can occur.
In the beta release I believe that ViewState may have been unavailable for all controls inside mode containers. When we allowed viewstate to work again, there were occasionally some issues like this. I believe this is a situation that can arise in a postback to any ASP.NET page where the control tree is significantly different from the source page for the postback, perhaps due to programmatic and conditional population of the control tree like this situation requires.
If the embedded control only needs access to the postback data itself and its viewstate is not required for your control, then you may be able to work around the problem by adding the following line:
this.controlname.EnableViewState = False
The following article explains this problem in detail:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbcon/html/vbtskAddingControlsToWebFormsPageProgrammatically.asp
Abstract:
However, view state information about dynamically created controls can be a problem in two scenarios:
- If you insert dynamic controls between existing controls.
- If you insert controls dynamically and then reinsert them during a round trip, but with different values.
If you insert dynamic controls between existing controls, the dynamic control's view state information is inserted into the corresponding location of the view state structure. When the page is posted and the view state is loaded, the dynamic control does not yet exist; therefore, the extra information in view state does not correspond to the right control. The result is usually an error indicating an invalid cast.
[Back to Top]
Topic: Error message: "The module 'CmsAuthorizationModule' is already in the application and cannot be added again"
I get the following error message:
Parser Error Message: The module 'CmsAuthorizationModule' already in the application and cannot be added again
What might cause this problem?
Answer
This problem is being caused by a web.config located in the root of your website. You should create an MCMS application in the root of a Web site. Please either remove this web.config file or remove the duplicate keys which interact with your template application web.config file.
[Back to Top]
Topic: Error message: "The page cannot be displayed - Cannot find server or DNS Error"
When authoring my site I sometimes receive the standard Internet Explorer error page with the following message:
The page cannot be displayed
Cannot find server or DNS Error
Internet Explorer
Answer
This is a known problem with Internet Explorer when doing POST requests to a site using Windows authentication. You need to install the following hotfix on every affected authoring machine:
821814 - You Receive a "Page Cannot Be Displayed" Error Message When You Post to a Site That Requires Authentication
Note: the following newer fix implements the same fix in a different way and requires an additional registry key. Please see the "More Information" section for details:
831167 - Wininet retries POST requests with a blank header
[Back to Top]
Topic: Error message: "The user does not have sufficient right to view the page." when clicking "Edit Hyperlink"
Sometimes when I click the "Edit Hyperlink" button on the Toolbar I receive the following error message: "The user does not have sufficient right to view the page."
Answer
This has been identified as a problem in Internet Explorer.
One workaround for this is to remove anonymous access permissions from the following file in the IIS MMC:
\<templateproject>\CMS\WebAuthor\Dialogs\HLink\HLink.aspx
[Back to Top]
Topic: Error message: "The View State is invalid for this page and might be corrupted"
I get the following error message for some of my postings. These postings include a user control which stores values in a database:
"The View State is invalid for this page and might be corrupted."
Answer
This is a problem with the Viewstate data and a dynamically changing control tree.
When there are postbacks between different modes (which there are for a ReEdit event but not for a NewPage event), there can be issues with repopulating the viewstate. When this happens, exceptions like this can occur.
In the beta release I believe that ViewState may have been unavailable for all controls inside mode containers. When we allowed viewstate to work again, there were occasionally some issues like this. I believe this is a situation that can arise in a postback to any ASP.NET page where the control tree is significantly different from the source page for the postback, perhaps due to programmatic and conditional population of the control tree like this situation requires.
If the embedded control only needs access to the postback data itself and its viewstate is not required for your control, then you may be able to work around the problem by adding the following line:
this.controlname.EnableViewState = False
The following article explains this problem in detail:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbcon/html/vbtskAddingControlsToWebFormsPageProgrammatically.asp
Abstract:
However, view state information about dynamically created controls can be a problem in two scenarios:
- If you insert dynamic controls between existing controls.
- If you insert controls dynamically and then reinsert them during a round trip, but with different values.
If you insert dynamic controls between existing controls, the dynamic control's view state information is inserted into the corresponding location of the view state structure. When the page is posted and the view state is loaded, the dynamic control does not yet exist; therefore, the extra information in view state does not correspond to the right control. The result is usually an error indicating an invalid cast.
[Back to Top]
Topic: Error message: "Type mismatch: Initialize Toolbar"
When I enter Web Author edit mode, I receive the following error message:
Error : Type mismatch: "Initialize Toolbar"
Answer
This problem is discussed in knowledge base article 811932.
[Back to Top]
Topic: Error message: "Write access denied. The user does not have sufficient rights to perform the requested action."
When our web authors throughout the company try to edit pages within MCMS, they are able to edit the page normally. However, they are unable to save any changes. Every time they try to save a page the following exception occurs:
Error: Error in Page Update using ROM
Description: Write access denied. The user does not have sufficient rights to perform the requested action.
Answer
This can happen when the user saving the page does not have rights to images or attachments embedded in one of the placeholders.
This can happen if the site way migrated from MCMS 2001 where such rights checks for resource gallery items did not exist or if the page was originally created by a user with more rights than the current user.
[Back to Top]
Topic: Error when uploading files to the resource gallery
We are not able to upload new resource gallery items to the resource gallery using Web Author or using Site Manager.
In Web Author we get the following error message: "Object reference not set to an instance of an object."
In SiteManager we get the followng error message:
Error description: (0x80020009)
Extended error: [What='The system cannot find the path specified.(3)'] [LCID='1033']
[SourceFile='javascript:void(null);']
[SourceFileLine='187'] [DebugInfo='javascript:void(null);']
[RecommendedAction=""] [Extralinfo=''] [UniqueErrorId='5001'] [Severity='5'] [Source='']
[CategoryId='0']
What can cause this problem?
Answer
The error message details indicate a problem with the path in the following registry key:
HKLM\SOFTWARE\NCompass\Resolution Content Server\Configuration\ResolutionTempFolder
This key is either pointing to a non-existing location or the permissions on this directory have been tightend.
The required permissions on the folder where this registry is pointing to are as follows:
- Administrators group (FULL)
- CMSSystem (FULL)
- Everyone (FULL)
- System (FULL)
[Back to Top]
Topic: Exception in "ConvertUtc2Local"
I'm running an MCMS Web site on two different servers. Presentation mode works fine on both boxes but on one box some actions in unpublished mode cause the following exception:
[NullReferenceException: Object reference not set to an instance of an object.]
Microsoft.ContentManagement.WebAuthor.DialogBase.ConvertUtc2Local(DateTime dtUtc) +61
Microsoft.ContentManagement.WebAuthor.StandardProperties.LoadDateTime(DateTime dtUtc, TextBox tbxDate, Calendar calendar, TextBox tbxTime) +54
Microsoft.ContentManagement.WebAuthor.StandardProperties.LoadPublishingDates() +83
Microsoft.ContentManagement.WebAuthor.StandardProperties.Page_Load(Object sender, EventArgs e) +192
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Control.LoadRecursive() +98
System.Web.UI.Control.LoadRecursive() +98
System.Web.UI.Control.LoadRecursive() +98
System.Web.UI.Page.ProcessRequestMain() +731
Answer
The reason for this problem is explained in the following KB article:
http://support.microsoft.com/?id=316112.
PRB: Session Variables Do Not Persist Between Requests After You Install Internet Explorer Security Patch MS01-055
[Back to Top]
Topic: Extreme document load time
While editing a page in the MCMS Web Author, I receive the following message in a popup:
Extreme document load time
The document is in the state of resolving links. While this is occurring the document may not be fully available for retrieval.
During this process some portions of the document may not be available. If this operation continues some items may be lost.
Do you wish to wait up to two (2) minutes for the document to complete?
Answer
This is not a message produced by MCMS but by the Ektron Placeholder control. Please contact Ektron (www.ektron.com) for details.
[Back to Top]
Topic: Forcing the download of ActiveX controls
After installing MCMS SP1, some of my Authors and Editors are no longer able to edit the pages using the Web Author. I assume this is a problem with the Microsoft ActiveX® controls. Is it possible to delete them and force a fresh download from the MCMS server?
Answer
Yes, you can force the controls to be downloaded. Follow these steps:
- Open Internet Explorer
- Click Tools and then click Internet Option
- Select the General tab
- In the Temporary Internet files section click Settings
- Click View Objects
- Delete "MCMS Html Editor" and "Microsoft MCMS Html Editor Toolbar"
- Close all Internet Explorer instances
[Back to Top]
Topic: How can I pre-select a template when creating a new page?
How can I pre-select a template when creating a new page?
Answer
You need to redirect to the following destination. This will open the Web Author with the template of your choice and the page will be saved in the channel of your choice:
WebAuthorContext.Current.GetUrlForMode(Posting,WebAuthorContextMode.AuthoringReedit)
[Back to Top]
Topic: IFRAME causes Javascript Error with Permission Denied
I've created a simple MCMS 2002 template containing an IFRAME (and the default console). When I view a posting based on this template, everything is fine until I switch to authoring mode. I then get a Javascript 'permission denied' error.
I set the visible property of the IFRAME (adding runat=server) so that it was only visible in Published mode. I no longer get the error when I switch to edit mode, but when I switch back to the live site, I still get the error (the page comes from the /NR/exeres/ cache).
Can someone explain why this error occurs, and t
he correct way to use IFRAMEs in a MCMS 2002 template without causing Javascript errors?
Answer
This is a small bug in the coding of Console.js. It causes a cross-site-scripting issue in framed sites. When switching between presentation and authoring mode, the Web Author tries to change the mode of all other frames.
This causes cross-site-scripting errors when the other frames do not belong to the same site.
This should also cause trouble in a framed site when the other frames contain content from other sites.
To solve this you have to add some code to the Console.js file located at the following location:
\Program Files\Microsoft Content Management Server\Server\IIS_CMS\WebAuthor\Client\Console.js
Change the code so that it looks like this:
function UpdateSiblingFramesInPublishedMode()
{
for (i=0; i < window.top.frames.length; i++)
{
if (window.top.frames[i] != window)
{
// refresh it with Published mode URL
try
{
window.top.frames[i].location.href =
GetUrlModePublished( window.top.frames[i].location.href );
}
catch(e)
{}
}
}
}
...
function UpdateSiblingFramesInUnpublishedMode()
{
for (i=0; i < window.top.frames.length; i++)
{
if (window.top.frames[i] != window)
{
// refresh it with Unpublished mode URL
try
{
window.top.frames[i].location.href =
GetUrlModeUnpublished( window.top.frames[i].location.href );
}
catch(e)
{}
}
}
}
[Back to Top]
Topic: Incorrect size and position of windows
In Web Author when a new window opens (e.g. Resource Manager) the positioning and size of the window causes the lower right edge of the window to be out of the screen. How can this be corrected?
Answer
To solve this this issue you need to modify some lines of code in the following file:
\Program Files\Microsoft Content Management Server\Server\IIS_CMS\WebAuthor\Client\Windows.js
The following code:
function WBC_UseDefaultSizing(pWindow)
{
var lWidth = WBC_getWindowWidth(pWindow);
var lHeight = WBC_getWindowHeight(pWindow);
...
needs to be changed to
function WBC_UseDefaultSizing(pWindow)
{
var lWidth = WBC_getWindowWidth(pWindow)-2*IDS_WIDTH_OFFSET;
var lHeight = WBC_getWindowHeight(pWindow)-2*IDS_HEIGHT_OFFSET;
...
[Back to Top]
Topic: Is it possible to pre-install the ActiveX controls for the Web Author?
A customer is restricting Microsoft ActiveX® downloads in browsers and wants to pre-install the Microsoft ActiveX controls necessary for the Web Author. How can this be done?
Answer
The customer needs to register the two classes contained in the following cab file:
c:\Program Files\Microsoft Content Management Server\Server\IIS_CMS\WebAuthor\Client\PlaceholderControlSupport\nrdhtml.cab.
Registration is done using "REGSVR32 <filename>"
If the same machines are required to author on MCMS 2001 and MCMS 2002, install the Microsoft ActiveX® controls of MCMS 2002. They are compatible with MCMS 2001.
[Back to Top]
Topic: Line Breaks in the HtmlPlaceholderControl
Is it possible to change the HtmlPlaceholderControl so that the lines are not double spaced? I just want a new line when I press enter. As it is, I have to press shift enter to get a new line.
Answer
When you press ENTER a <p> tag is inserted which means a new section is started. When you press Shift-ENTER a <BR> tag is inserted which means a line-break in a section.
If the line spacing for sections does not meet your requirements just change the margin-top and margin-bottom style attributes of the <p> tag in your style sheet.
It is not possible to change the Microsoft ActiveX® control to insert <BR> instead of <P> when pressing Enter.
If you really want to change this behavior you could create a custom placeholder control derived from the original HtmlPlaceholderControl which overrides the SavePlaceholderContent method and exchanges <p> with <br>.
[Back to Top]
Topic: Multiple Instances of the HtmlPlaceholderControl Toolbar
I experience the problem that I sometimes the have multiple instances of the Toolbar for the HtmlPlaceholderControl in the browser. How can I prevent this?
Answer
This can happen if there are hidden HtmlPlaceholderControls (e.g. hidden SPAN or DIV tags which surround the HtmlPlaceholderControl). This will still create the Tool but as the ActiveX control holding the Editor Component is not available the Toolbar cannot be bound to the placeholder control and remains orphaned on the page.
To prevent this either hide the HtmlPlaceholderControl using client side Script:
<script language="javascript">
mydiv.style.visibility='Hidden';
mydiv.style.Display='None'
</script>
or remove the HtmlPlaceholderControl using server side script by adding logic to the placeholder which prevents the HtmlPlaceholderControl from being added.
[Back to Top]
Topic: Page is refreshed when trying to save new page.
We experience problems when trying to save a new page in MCMS 2002 Web author. After closing the save new page dialog a postback to the server happens but rather than saving the page and switching to unpublished mode the page just refreshes in update mode and the placeholders show up empty. In addition the page has not been created.
What can cause this behaviour?
Answer
This can happen if the SQL server collation for the database is set to case sensitive. This is not supported with MCMS 2002. Ensure that the SQL server collation for the MCMS database is set to case-insensitive.
[Back to Top]
Topic: Placeholder content is lost when saving or doing preview
When I preview a posting or when I save a new posting, the placeholder content is gone. What can cause this?
Answer
This can happen if a <FORM> tag is included in the template. ASP.NET automatically adds a <FORM> tag to ASPX pages. Pages can only contain one <FORM> tag.
Right click on the page in authoring mode and click "View Source". Search in the source code for "<FORM". If there is more than one tag, you will need to remove the extra ones.
Beside this you also have to ensure that the placeholder controls are located between the <FORM...> and the </FORM> tag.
[Back to Top]
Topic: Problem uploading big files
I'm trying to upload a file in the resource manager. The file is a bit large (about 5 MB). When I select the file, and press ok button an error page is displayed.
Answer
Please add or modify the following section in your web.config file to control the maximum upload size and time:
<httpRuntime executionTimeout="3600"
maxRequestLength="1024000"
useFullyQualifiedRedirectUrl="false"
minFreeThreads="8"
minLocalRequestFreeThreads="4"
appRequestQueueLimit="100"/>
In this example, the values are set to 3600 seconds=1 hour and 1024000 KB=1GB.
[Back to Top]
Topic: Script error when switching to edit mode or when saving a posting.
#1: When I click on the "Switch to Edit Site" link in the console nothing happens but a script error shows up.
#2: I get a "__CMS_PostBackForm is undefined" message when trying to create a new posting in the Web Author.
What can cause this error?
Answer
There are several possible reasons for this:
-
Your Web application is missing the virtual directory "CMS". Ensure that this virtual directory exists and points to the IIS_CMS folder in the MCMS installation directory. Also ensure that it is just a virtual directory (not a web application).
-
If your template is named Default.ASPX, rename your template to a different name.
-
Ensure that the ID of the form inside the template aspx page (visisble in html view in Microsoft® Visual Studio® .NET) is not set to "default". Choose a different name.
-
Check if there is a virtual directory with the same name as your channel. Invalid Metabase entries on this virtual directory might interact with MCMS and cause this error. To troubleshoot this, rename this virtual directory to a different name and check if the console works correctly. If it does, and you need the virtual directory with the same name, check which entries are causing the problem.
-
Another reason for this can be if Whidbey and ASP.NET 2.0 are installed and the template project uses this version. MCMS 2002 is currently not compatible with ASP.NET 2.0
[Back to Top]
Topic: Setting the spell check language in Web Author
Spell checker in MCMS 2002 Web Author uses wrong language. How can I change this?
Answer
The spell checker is a component of Microsoft Word installed on the client machine. Please ensure that spell checking of this language works correct in Word. If this is ok, then check the value of the following registry key:
HKCU\Software\Microsoft\Office\10.0\Common\LanguageResources\InstallLanguage
(the version might differ)
Ensure that the correct language value is defined. Here are samples of the values for the most often used languages:
german
english
spanish
french
italian
dutch
swedish
|
|
407 (hex)
409 (hex)
40A (hex)
40C (hex)
410 (hex)
413 (hex)
41d (hex)
|
|
1031 (dec)
1033 (dec)
1034 (dec)
1036 (dec)
1040 (dec)
1043 (dec)
1053 (dec)
|
More languages can be found in KB 221435
[Back to Top]
Topic: Supported Browsers for the Web Author
Which browsers are supported by the MCMS 2002 Web Author?
Answer
Unlike MCMS 2001, there is no DHTML Version of Web Author available.
The Placeholder Controls shipped with MCMS 2002 require Microsoft Internet Explorer 5.x (also Microsoft Internet Explorer 5.01 with Windows Script 5.6) on Windows (Windows 9x and Microsoft Internet Explorer for the Mac are no longer supported).
This limitation not only belongs to the PlaceholderControls shipped with MCMS 2002. Also the dialogs are tailored for the above browser versions.
[Back to Top]
Topic: Template Gallery resources reference "/CMS/CMS/..."
When I select "create new page" in the Web Author console, I see the Template Gallery Window pop up but no images are being pulled down. The stylesheet is not being loaded and the Javascript files are not being pulled down. I viewed the source of this page and saw that there was an extra folder in the path to the resource files. The links looked like this: /CMS/CMS/WebAuthor/Client/WBC.css.
I had the same type of problem when I went into the resource gallery. What could be wrong?
Answer
The solution to this problem is that the virtual directory "CMS" in the template application is an application and not a virtual directory. You can tell the difference between the two by their appearance in the MMC. A virtual directory has a little world on top of a folder while an application has a grey box with a page in it and a green arrow.
To fix this:
- Open the IIS_Admin MMC
- Right click on the "CMS" Virtual Directory/Application item under the web root
- Click properties on the virtual Directory tab and select "remove"
- Click "OK"
[Back to Top]
Topic: Toolbar button "Edit Source" grayed out
I have this strange problem that in some (not all) of my templates when in edit mode I do not have the option to view the html source in my htmlplaceholders since the html edit source button is grayed out.
I checked that I have full formatting on the placeholder so this is not the problem what else can explain this?
Answer
This is not an option of the placeholder object but of the placeholder control object.
This option can be enabled/disabled using the "AllowHtmlSourceEditing" property of the
HtmlPlaceholderControl.
In VS.NET click on the placeholder control on your template and you will note the "AllowHtmlSourceEditing" in the behaviour section of the property windows.
[Back to Top]
Topic: Tree view refreshes without postback
If the list of resource galleries has exceeded the size of the window of the tree view control and the author has to scroll down to select and expand a tree node the following error occurs:
The resourcegallery is not expanded but the list jumps back to the first resourcegallery.
The same happens if more channels exist and a node in the hyperlink dialog needs to be expanded. The error only happens after a scroll down - not if no scroll down is required.
If the same node is expanded a second time the problem does not occur. Only for the initial page load. How can I avoid this problem?
Answer
To avoid this you need to update the treeview.htc file which is part of the IE WebControls:
treeview.htc, line 444:
...
try
{
var prevScrollTop = element.scrollTop;
var prevScrollLeft = element.scrollLeft;
// oItem.focus(); <--- this line needs to be commented out to avoid the problem.
element.scrollTop = prevScrollTop;
element.scrollLeft = prevScrollLeft;
}
catch (e)
...
[Back to Top]
Topic: Treeview broken in the Web Author
The dialog box used in the Web Author to link a piece of text to an internal link is missing the little '+' next to the channel names. This provides no means for the user to select a posting to link to. It only allows the selection of the root channel.
Answer
The resolution is to create a virtual web application named “webctrl_client” under the root of the MCMS Web site, and then map it to the “C:\Inetpub\wwwroot\webctrl_client” physical directory (this is the Default Web Site install directory). After you’ve done this, try the dialog again.
[Back to Top]
Topic: Ugly URL after postback
When I add a button to my template and click it, the URL line changes to the template instead of the nice posting URL. What's wrong?
Answer
This behavior is by design. What you can see is the true URL of the posting, which consists of a call to the template file with parameters identifying the posting. ASP.NET requires this URL to correctly process a posting. If a user enters the friendly URL in the browser the MCMS ISAPI filter silently replaces the friendly URL with the correct one. ASP.NET never knows about the MCMS internal URL, it creates postback links to the true URL.
Here is a workaround for this problem. Add the following code behind the <form...> tag in the template or add it to a User Web Control which you can add to all your templates:
<%@ Import Namespace="Microsoft.ContentManagement.Publishing" %>
<% if (WebAuthorContext.Current.Mode == WebAuthorContextMode.PresentationPublished) { %>
<SCRIPT language=javascript>
<!--
__CMS_PostbackForm.action = '<% =CmsHttpContext.Current.Posting.Url %>';
// -->
</SCRIPT>
<% } %>
[Back to Top]
Topic: Ugly URL when switching from edit to live mode
When switching from Edit to Live mode the URL in the browser is still in an ugly format. Can this be changed?
Answer
1) Add the following code part to global.asax.cs of you template project:
public void Application_PreRequestHandlerExecute(Object sender, EventArgs e)
{
//
// correct the url after switch to live
//
Posting thisPosting = CmsHttpContext.Current.Posting;
PublishingMode currentMode = CmsHttpContext.Current.Mode;
if (thisPosting != null && currentMode == PublishingMode.Published)
{
if ( Request.QueryString["NRORIGINALURL"] != null &&
Request.QueryString["NRORIGINALURL"].StartsWith("/NR/exeres") )
{
if ( !thisPosting.Url.StartsWith("/NR/exeres") )
Response.Redirect (thisPosting.Url);
}
}
}
2) Wire up this event in the global init:
this.PreRequestHandlerExecute +=
new EventHandler(this.Application_PreRequestHandlerExecute);
The complete implemetation looks like this:
namespace ...
{
///
/// Summary description for Global.
///
public class Global : System.Web.HttpApplication
{
public Global()
{
InitializeComponent();
this.PreRequestHandlerExecute +=
new EventHandler(this.Application_PreRequestHandlerExecute);
}
public void Application_PreRequestHandlerExecute(Object sender,
EventArgs e)
{
//
// correct the url after switch to live mode
//
Posting thisPosting = CmsHttpContext.Current.Posting;
PublishingMode currentMode = CmsHttpContext.Current.Mode;
if (thisPosting != null && currentMode == PublishingMode.Published)
{
if ( Request.QueryString["NRORIGINALURL"] != null &&
Request.QueryString["NRORIGINALURL"].StartsWith("/NR/exeres") )
{
Response.Redirect (thisPosting.Url);
}
}
}
...
}
}
[Back to Top]
Topic: Users not authenticated with Standard Edition
All requests to a site (MCMS 2002 Standard Edition) that is managed by MCMS and configured with windows authentication receives a 404 error. If a request is made to the application (root channel) then user will get a "Directorly listing denied" error 403.
Requests to non MCMS resources are resolving correctly, access to Site Manager is working as well as the SCA.
When doing a manual login into the Web site by accessing the Manuallogin.asp we are able to authenticate to the site and the site is working as expected.
This shows that the site is working but some part of the windows authentication is not working in the MCMS application.
What might cause the problem?
Answer
This can happen with MCMS 2002 Standard Edition if MCMS is not able to determine if a license violation has happened.
In the Standard Edition of MCMS there is a limit to the number of users that is allowed by the system and it is restricted to 15 Non Subscribers. NT/AD Groups are not allowed as members of nonsubscriber rights groups.
If MCMS is not able to identify if a member of a rights group is a user or a group you might experience the problem you have seen. Please enter SiteManager and have a look into all rights group and check if you find an entry where the type column is shown as <UNKNOWN>.
Remove all the affected entries and your site should start working again.
A known reason for the type to be <UNKNOWN> is that the domain is not accessable from the MCMS server machine (domain controller is down).
[Back to Top]
Topic: View state error when changing application pool of template application
After changing the application pool of my MCMS template application I receive an view state error. Is there any problem with doing this?
Answer
This can happen if the MCMS folders do not run in the same application pool as the Web site. See here for details about all the directories that have to run in the same applicaiton pool:
842429 - You receive a 403.18 error message when you run an MCMS application in a different application pool on IIS 6.0
[Back to Top]
Topic: Warning: "Are you sure you want to navigate away from this page?"
Clicking on a calendar control embedded in a template causes the following message: "Are you sure you want to navigate away from this page? Refreshing or leaving this page will loose all unsaved changes."
Answer
Some custom placeholder controls like the calendar control uses postbacks to the server when you click on it. This will cause this message to occur because the template assumes that you are leaving the page.
Another reason might be a client side reload being cause by (e.g.) a resize event. Some navigation controls use this to ensure that the rendering is done correct on the current window size.
For such situations you can use EnableLeaveAuthoringWarning = "false", a property of the console tag.
[Back to Top]
Topic: Available Woodgrove sample sites
On the MCMS 2002 CD there is an ASP.NET C# sample site called WoodgroveNet. Is there also a Visual Basic .NET or ASP version available?
Answer
WoodgroveNet Sample Site
This sample demonstrates how to use C# to build a site with Content Management Server 2002
This sample demonstrates how to use Visual Basic .NET to build a site with Microsoft Content Management Server 2002:
http://www.microsoft.com/downloads/details.aspx?familyid=d0bd546c-f2b2-4ed0-a209-54f3ee35322a
This sample demonstrates how to build a framed Intranet site with Microsoft Content Management Server 2002:
http://www.microsoft.com/downloads/details.aspx?familyid=56459d80-0d16-4275-895c-414ed5a9299b
This sample demonstrates three different ways to build a multilingual Web site using Microsoft Content Management Server 2002:
http://www.microsoft.com/downloads/details.aspx?familyid=19bf2542-b0d5-4866-9c73-2a52598c91dd
This sample demonstrates how to build a Microsoft Content Management Server 2002 Web site in ASP:
http://www.microsoft.com/downloads/details.aspx?familyid=a95973ab-8f56-4ddd-b0ab-092107ed1a85
Other samples: http://www.microsoft.com/cmserver/default.aspx?url=/cmserver/evaluation/samplesites
[Back to Top]
Topic: Broken references
I installed the Woodgrove Bank sample but my project won't compile in Microsoft® Visual Studio® .NET. After a little investigation, I found that the references on the MCMS DLLs are broken. How did this happen?
Answer
Microsoft Visual Studio .NET projects use an XML file to store the location of references. Generally the references can be found under "Program Files/Microsoft Content Management Server" but there are cases where this isn't true.
For example, on non-English systems there is no "Program Files" directory and therefore the references are broken.
To correct the references
1. In Microsoft Visual Studio .NET open the WoodgroveNet project.
2. In the Solution Explorer expand the References section.
3. Right click on any DLL whose reference is broken and select Delete on the popup menu.
4. Right Click on the References and select Add Reference...from the popup menu.
5. Select the Browse button in the Add References dialog box.
6. Browse to the MCMS installation folder and under that \Server\bin folder.
7. Select the DLL whose reference is to be added to the project, then select Open button.
8. In the Add Reference... dialog box, select OK.
[Back to Top]
Topic: Credentials are not accepted when importing the Woodgrove sample site on Windows XP
The credentials are not accepted when trying to import the Woodgrove sample site into the MCMS repository on Microsoft Windows XP.
Answer
This is a problem with the default Windows XP security policy.
Go to your Local Computer Policy, click Computer Configuration, then Windows Settings, then Security Settings, then Local Policy, then Security Options.
Change the "Network access: Sharing and security model for local accounts" setting to "Classic - local users authenticate as themselves".
[Back to Top]
Topic: Homeport instead of MCMS cover page
I created a new channel and navigated to it using http://localhost/channelname. All I get is an MCMS presentation page. There is no option to switch to edit mode.
Answer
The default setting (once you have installed the Woodgrove ASP.Net sample) is for the root channel to redirect to the MCMS Homeport page. You will need to edit your channel properties in the Site Manager.
To Modify your Channel Rendering property in Site Manager:
1. In Site Manager, click on Channels in the far left pane.
2. In the middle pane right click Channels then select Properties in the menu.
3. In the Publishing tab click the Select button in the Channel Rendering section.
4. Clear the Script URL entry. This will direct your browser to the MCMS cover page when the channel is empty.
[Back to Top]
Topic: Left navigation highlight
The left navigation console in WoodgroveNet (About Us) is constantly highlighted regardless of what page is currently being viewed. How can I change this?
Answer
This is an issue with the Microsoft® Internet Explorer Webcontrols 'Treeview' control. You can manually alter the TreeView.htc file to change this behavior. We did not make the change as it would affect all instances of the tree control on your machine.
You can find more information about the Treecontrol Webcontrol on Microsoft's Microsoft MSDN® Web site.
[Back to Top]
Topic: Project error
Why is it that if the sample site is installed to a directory that is different from the default, you get an error when opening the WoodgroveNet project in Microsoft® Visual Studio® .NET.
Answer
The Microsoft Visual Studio .NET solution for WoodgroveNet (woodgrovenet.sln) expects that the virtual directory created for WoodgroveNet be mapped to the default path for the MCMS install.
If your sample site was installed to any directory that is not the default, you must modify your virtual directories "Local Path" setting. You will also need to modify the path property for the MCMSWebControlLibrary.
To Modify your MCMS Sample Site virtual directory Settings:
- In the Microsoft Internet Information Server (IIS) snap-in, right click on WoodgroveNet.
- Select Properties in the menu
- In the Virtual Directory tab modify the Local Path setting so that it points to the path that you installed WoodgroveNet
To Modify the Path property for the MCMSWebControlLibrary Reference:
- Microsoft Visual Studio .NET open the WoodgroveNet project
- In the Solution Explorer expand the References section
- Right click on MCMSWebControlLibrary and select Delete from the popup menu
- Right click on References and select Add Reference from the popup menu
- Select the Browse button in the Add References dialog box
- Select \Sample Data\WoodgroveNet\bin\McmsWebControlLibrary.dll then select the Open button
- In the Add Reference dialog box, select OK
[Back to Top]
Topic: Roll back when installing Woodgrove sample site
At the end of the Woodgove sample site installation process, the setup rolls back for some unknown reason. The following event is getting added to my event log:
Event Type: Information
Event Source: MsiInstaller
Event Category: None
Event ID: 11708
Date: 10/20/2003
Time: 1:51:56 PM
User: N/A
Computer: TIMOL-DEV
Description:
Product: Microsoft Content Management Server Sample Data -- Installation operation failed.
Any idea what might have happened?
Answer
This can happen when you install the sample site on a different Web site as the Default Web Site. This is not officially supported. Also ensure that you did not rename the Default Web Site to another name.
The workaround is to copy the files from another machine onto <CMS_Root>\Sample Data\ manually, and then manually create the web application mapping. The files under the <Cms_Root>\Sample Data\ hierarchy are basically Microsoft Visual Studio® .NET project files.
The next step is to create a web application named "WoodgroveNet" (i.e. the original MCMS template project name) under the root of the Web site where MCMS is installed and map it to <Cms_Root>\Sample Data\WoodgroveNet\.
Then create a virtual directory named "CMS" and map it to: <Cms_Root>\Server\IIS_CMS\ (under the root of the WoodgroveNet web application). This "CMS" virtual directory (ensure that it is not a web application) is required. Without it, you will have problems switching to edit mode using Web Author.
After this has done, you should be able to browse the WoodgroveNet sample site as http://<ServerName>/WoodgroveNet.
[Back to Top]
Topic: Tree Control Styles
How do you change the color of the navigation/treenode links? I have tried modifying every instance of the default woodgrove #336633 color and it has no effect. I have modified the .css file as well as the mcmsnavigationcontrol.cs file. I have even done a search and there are no more references to the #336633 color anywhere! Where is the web application pulling this color from? I want to be rid of this green woodgrove color, please help!
Answer
Woodgrove uses the IE Webcontrols tree control. It uses HTC files.
Look here for the readme: C:\Program Files\Microsoft Internet Explorer WebControls
snippet....
4. Create the following directories below the Root Web:
webctrl_client\1_0\
webctrl_client\1_0\images
webctrl_client\1_0\treeimages
webctrl_client\1_0\treeimages\rtl
5. Copy the HTC files (Behaviors) to the "webctrl_client\1_0\" folder
below the Root Web folder.
6. Copy the images to the following paths:
Images used by the WebControls: "webctrl_client\1_0\images"
Images for the TreeView: "webctrl_client\1_0\treeimages"
Right-to-left images for the TreeView:
"webctrl_client\1_0\treeimages\rtl"
[Back to Top]
Topic: Woodgove and CMS 2002 SP1a
Hi everyone, I have installed MCMS 2002 with SP1a. I have installed Content Server, Site Manager and Site Stager and every thing seems O.K. I would like to install the Woodgrove sample site. The Content Management Server 2002 Installation Guide says:
To install the WoodgroveNet sample site
- On the MCMS computer, insert the MCMS 2002 CD into the CD-ROM drive.
- On the Microsoft® Content Management Server splash screen, click Install Components, then click Install Sample Site.
But I don't have the option Install Sample Site. What am I missing?
Answer
MCMS 2002 SP1a does not ship with the Woodgroove sample site installation. You have two options:
1. Install the Woodgroove sample site from the MCMS 2002 RTM CD by running the following MSI package file:
\SampleSite\Microsoft Content Management Server Sample Data.msi
2. Download the sample from:
http://download.microsoft.com/download/a/a/1/aa121cac-2a05-4602-8416-233e7b6779ca/WoodgroveNet.zip
[Back to Top]
Topic: Woodgrove Installation hangs
When I try to to import the MCMS Sample Data Installation (WoodGroveNet) the installation process hangs indefinitely.
What might cause this?
Answer
This can happen when Microsoft Visual Studio .NET Analyzer is turned on under Administrative Tools, Data Sources (ODBC), Tracing
Alternatively you can check if the following registry key is set to 1 in the current user profile:
[HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\ODBC]
"Vista"="1"
To resolve this stop Microsoft Visual Studio .NET Analyzer using the button in Administrative Tools, Data Sources (ODBC), Tracing tab.
Alternatively you can resolve it by setting the above registry key value to “0”
[Back to Top]
Topic: WoodgroveInternational sample site install does not import sample data
I installed the WoodgroveInternational demo site, but cannot figure out where the sample data is. I expected to see something to allow me to import sample data into my MCMS repository, but the install was basically silent with few options. Am I missing something?
Answer
The data gets imported only if you start the installation by clicking Setup.Exe, not the *.msi file.
[Back to Top]
Topic: Declined Posting does not get assigned back to the Author
I have an issue in MCMS. I find that postings are locked to various users as they travels through the workflow. For example, when a request for approval is denied, the posting is not sent to the author it came from.
Here is a sample workflow:
- An Author submits a page into the workflow and the Editor receives it
- The Editor reviews it, decides that it is not correct and plans to send it back to the Author
- However before the Editor sends it back to the Author the Editor makes some minor changes, this changes the page from "Author - Saved" to "Editor - Saved"
- When the Editor declines back to the Author the page is still locked to the Editor as "Editor - Saved" and the Author cannot make any changes to the page as requested by the Editor
Any Help would be greatly appreciated.
Answer
This behavior is as expected. When the Editor changed the content he acted as an Author - not as an Editor. Then when he later declined it, he acted as an Editor. The decline action returns the posting to the last author - and this was the Editor himself.
To prevent this, the Editor must not do any changes before declining the posting. One option would be to remove the "Edit" link in the console for Editors. This would ensure that Editors cannot act as Authors.
To allow comments to be sent to the author, the following console extension can be used. It allows an Editor to add a comment when declining. This comment can be picked up by a workflow event and possibly sent to the Author by email.
The sample can be found here:
http://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=88d0484d-d380-4ad7-ac6c-59c58f996601
[Back to Top]
Topic: Editor vs. Moderator
When I update a posting only editor approval is required and not moderator approval. Is this a bug?
Answer
No this is not a bug. Editors and Moderators approve different changes.
- Editors approve content changes
- Moderators approve property changes
So when a placeholder content gets changed only Editor approval is required. When a posting is moved then only Moderator approval is required.
If you need a 2-level workflow then either implement a 3rd party workflow engine like the workflow engine from Teamplate (www.teamplate.com) or force a property change when the posting is changed. This can be done using a workflow event.
[Back to Top]
Topic: Posting goes offline when waiting for Moderator approval
Whenever a posting state switches to "waiting for moderator approval" the page goes offline. This does not happen when the posting state switches to "waiting for editor approval". Why does this happen and how can I prevent this?
Answer
This is expected behavior in MCMS. Internally, MCMS uses two different objects: the page object and the posting object. Editors approve changes to the page object (which holds the placeholder content and the custom properties) while the Moderator approves changes to the posting object (which stores properties like the display name, the start and expiration date and the reference to the template being used by this page).
This concept of page/posting is used to implement connected postings. All connected postings use the same page object to share the content.
MCMS supports versioning for the page object but not for the posting object. So whenever the posting object requires approval, the posting changes to "waiting for moderator approval" and there is no longer a published version of the object available.
There are two workarounds to avoid this:
- use a staging environment (it usually does not affect anyone if the page goes offline in a staging environment)
- do not use moderators.
[Back to Top]
Topic: What is the sequence of Workflow Events?
When a new page is created, what is the sequence that the ASP.NET workflow events get fired?
Answer
- Creating event fires
- Changing event fires
- Create action creates the posting, with the name set to the name of the template.
- Created event fires
- Changed event fires
- PropertyChanging event fires
- Changing event fires
- PropertyChange action sets the name of the posting
- PropertyChanged event fires
- Changed event fires
[Back to Top]
Topic: Workflow with empty Editor/Moderator groups
I have assigned a rights Group (Editor or Moderator) to one of my channels. The rights group does not contain any users. When I now submit a new page the state switches to waiting for editor/moderator approval even though there is no editor or moderator available to do the approval. Is this expected?
Answer
Yes, this is expected behavior. MCMS only checks whether there are any rights groups from these user roles assigned to the channel. The server does not look to see whether that rights group contains any valid users. So even if a Editor or Moderator rights group has no AD users or groups assigned to it, the workflow state will still be set to an appropriate "waiting for approval" after a page has been submitted.
The reason for this behavior is that any channel with an Editor and/or Moderator rights group assigned is assumed, by definition, to require appropriate approvals on all pages posted there. The fact that there are no users explicitly assigned to the Editor and/or Moderator rights group in question does not eliminate the need for approval, therefore the pages must not skip the appropriate "waiting for approval" stages of the MCMS workflow.
[Back to Top]
The information contained in this document represents the current view of
Microsoft Corporation on the issues discussed as of the date of publication.
Because Microsoft must respond to changing market conditions, it should not be
interpreted to be a commitment on the part of Microsoft, and Microsoft cannot
guarantee the accuracy of any information presented after the date of
publication.
This White Paper is for informational purposes only. MICROSOFT MAKES NO
WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS
DOCUMENT.
Complying with all applicable copyright laws is the responsibility of the user.
Without limiting the rights under copyright, no part of this document may be
reproduced, stored in or introduced into a retrieval system, or transmitted in
any form or by any means (electronic, mechanical, photocopying, recording, or
otherwise), or for any purpose, without the express written permission of
Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or
other intellectual property rights covering subject matter in this document.
Except as expressly provided in any written license agreement from Microsoft,
the furnishing of this document does not give you any license to these patents,
trademarks, copyrights, or other intellectual property.
© 2004 Microsoft Corporation. All rights reserved.
Microsoft, ActiveX, Visual Studio, Windows, and Windows Server are either
registered trademarks or trademarks of Microsoft Corporation in the United
States and/or other countries.
The names of actual companies and products mentioned herein may be the
trademarks of their respective owners.
| © 2004 Microsoft Corporation. All rights
reserved. |
