Stefan [MS]
2003-07-23 20:55:56 UTC
Hi Ben,
your problem description is very vague.
Site Deployment is very fragile and you need to check many things.
Below are a list of checks you need to perform. Ensure that all(!) settings
are as described.
Cheers,
Stefan.
----------------
Question: The XML parser could not parse the tag it was given
Error Message "The XML parser could not parse the tag it was given" during
SDO Import
Answer
There are multiple different possible reasons and solutions for this error:
1.. The SDO file that should be imported is 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.
2.. Memory problems. Increase the virtual memory of the Microsoft® Content
Management Server (MCMS) server.
3.. Internet Explorer caching issues. Clear the Microsoft 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).
4.. For unknown reasons clearing the memory cache also often solves this
problem
5.. 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.
6.. The Microsoft Internet Explorer Webcontrols are not 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.
7.. ensure that the user doing the import is a MCMS administrator
8.. if 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.
9.. Ensure that the user listed inthe ProcessModel section of the
Machine.Config file has adequate rights (also read access to the SDO file).
10.. Ensure that SQL server has enough per seat licenses configured.
11.. 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.
----------------
your problem description is very vague.
Site Deployment is very fragile and you need to check many things.
Below are a list of checks you need to perform. Ensure that all(!) settings
are as described.
Cheers,
Stefan.
----------------
Question: The XML parser could not parse the tag it was given
Error Message "The XML parser could not parse the tag it was given" during
SDO Import
Answer
There are multiple different possible reasons and solutions for this error:
1.. The SDO file that should be imported is 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.
2.. Memory problems. Increase the virtual memory of the Microsoft® Content
Management Server (MCMS) server.
3.. Internet Explorer caching issues. Clear the Microsoft 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).
4.. For unknown reasons clearing the memory cache also often solves this
problem
5.. 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.
6.. The Microsoft Internet Explorer Webcontrols are not 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.
7.. ensure that the user doing the import is a MCMS administrator
8.. if 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.
9.. Ensure that the user listed inthe ProcessModel section of the
Machine.Config file has adequate rights (also read access to the SDO file).
10.. Ensure that SQL server has enough per seat licenses configured.
11.. 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.
----------------
Hi,
We have finished our intranet using CMS. We plan to
migrate to production server. But we have a lot of
problems.
Actually, we have defined a new web site in IIS 5.0, and
install CMS. When I tried to import the sdo file (Site
manager),and I've got several errors. I also have "access
forbidden" to the site??? (I have checked all security and
seems ok for me). What is really strange is, when I define
a Virtual Web Site in the default web site of IIS, it
works fine!!!
Did I mist something????
Someone can help me?
Thanks in advance.
We have finished our intranet using CMS. We plan to
migrate to production server. But we have a lot of
problems.
Actually, we have defined a new web site in IIS 5.0, and
install CMS. When I tried to import the sdo file (Site
manager),and I've got several errors. I also have "access
forbidden" to the site??? (I have checked all security and
seems ok for me). What is really strange is, when I define
a Virtual Web Site in the default web site of IIS, it
works fine!!!
Did I mist something????
Someone can help me?
Thanks in advance.