Stefan Goßner posted this important article on his blog. Thanks Stefan for this article
Stefan Wrote
As I dicussed earlier MCMS is not supported with Team Foundation Server. The reason is that the developer tools shipped with MCMS are incompatible with Team Foundation Server and raise an exception when items are checked in.
This might be a significant design limitation for customers, so I spent some time to identify a workaround for this problem. The problem is caused by the developer tools integration in VS.NET 2005. To get Team Foundation Server working with an MCMS template project it would be required to disable the developer tools for this specific project. To still allow users to manage template gallery item it would be required to use a standalone version of MCMS template explorer.
Read More
Tuesday, March 20, 2007
Thursday, March 08, 2007
How to maintain a Microsoft Content Management Server database
This article discusses general best practices for maintaining your Microsoft Content Management Server (MCMS) database by using tools that are included with the MCMS client tools and with SQL Enterprise Manager.
This article also discusses a substitute process for the Background Process (BP). This substitute process includes a SQL stored procedure version of the BP together with an ASP sample script to delete expired postings and to delete expired pages in your MCMS database.
Note The substitute process is for MCMS 2001 only.
MCMS and .NET 3.0 / WCF
Sometimes you need to write webservice coded in .NET 3.0 / WCF but the problem here is the site manager.
In this case Site Manager will not run if .NET 3.0 is installed. You would need to create a config file to enforce the usage of .NET 2.0 and to separate the environment for .NET versions to be able to run both Site Manager and your web service.
In this case Site Manager will not run if .NET 3.0 is installed. You would need to create a config file to enforce the usage of .NET 2.0 and to separate the environment for .NET versions to be able to run both Site Manager and your web service.
Thursday, March 01, 2007
Unauthorized user able to create posting !!!!!!
This case was reported on microsoft.public.cmserver.general group
Case:
We have multiple websites hosted on the same CMS farm by mapping Channel Names to Host Header Names. On one of the sites any user whose is a member our AD group can create new page/posting even though they are not assigned any role in the CMS system. This happens only on one site among the several sites in the server.
Have anyone come across this issue before.
Answer:
please check your rights groups.
Sounds as if the guest account has been assigned to a non-Subscriber rights group.
This is not supported and will lead to such an issue.
Answered by: Stefan Goßner
Case:
We have multiple websites hosted on the same CMS farm by mapping Channel Names to Host Header Names. On one of the sites any user whose is a member our AD group can create new page/posting even though they are not assigned any role in the CMS system. This happens only on one site among the several sites in the server.
Have anyone come across this issue before.
Answer:
please check your rights groups.
Sounds as if the guest account has been assigned to a non-Subscriber rights group.
This is not supported and will lead to such an issue.
Answered by: Stefan Goßner
The remote server returned an error: (401) Unauthorized
I get an HTTP 401 error in Site Manager when trying to export or import items. What might be causing the problem?
Answer
1 - Ensure that the 'ASPNET' account has the "Impersonate a client after authentication" privilege.
2 - Ensure that the /MCMS virtual directory has anonymous access enabled.
3 - Ensure that the /NR virtual directory has anonymous access enabled.
Answer
1 - Ensure that the 'ASPNET' account has the "Impersonate a client after authentication" privilege.
2 - Ensure that the /MCMS virtual directory has anonymous access enabled.
3 - Ensure that the /NR virtual directory has anonymous access enabled.
Subscribe to:
Posts (Atom)