Hi,

When I connect CMS to dbserver\instance1, CMS is read-only. Every attempt to
write to it from Site Manager failed. (the read-only box of the database is
not checked of course)
I then made a backup of the db and restored it on a db-server without named
instances and CMS was now able to write to the database.

Does CMS have a problem with named instances?

Best Regards,

Frank

[ Post a follow-up to this message ]

Hi Ros,

no there are no such issues.
Maybe the system account does not have the db_datawriter permissions?

Cheers,
Stefan

"ROS" <ROS@discussions.microsoft.com> wrote in message
news:BD11A9D3-674D-46A1-BD88-C6A755F35687@microsoft.com...
> Hi,
>
> When I connect CMS to dbserver\instance1, CMS is read-only. Every attempt
to
> write to it from Site Manager failed. (the read-only box of the database
is
> not checked of course)
> I then made a backup of the db and restored it on a db-server without
named
> instances and CMS was now able to write to the database.
>
> Does CMS have a problem with named instances?
>
> Best Regards,
>
> Frank

[ Post a follow-up to this message ]

Stefan,

I read something about case-sensitive named instances and problems with CMS.
But we did not change the collation to case sensitive, so that should not be
the problem. To fix things I created a whole new database on the
dbserver\instance1. I no longer experience problems when using CMS site
manager.

Could it be that the datase became inconsistent or something. And is it
possible to repair such a database?

Regards,

Frank

"Stefan [MSFT]" wrote:

> Hi Ros,
>
> no there are no such issues.
> Maybe the system account does not have the db_datawriter permissions?
>
> Cheers,
> Stefan
>
> "ROS" <ROS@discussions.microsoft.com> wrote in message
> news:BD11A9D3-674D-46A1-BD88-C6A755F35687@microsoft.com... 
> to 
> is 
> named 
>
>
>

[ Post a follow-up to this message ]