I have a client that was getting Error 0x80044005 this morning.

The SQL server is seperate from the CRM Server.

Event logs did not say much. The above error number is 2.

I checked the Database server, opened up SQL Enterprise manager and found
that two of the CRM Databases were set to single user mode.

If you have this problem just Right client on the Database. Goto Properties
and then the options tab.

I found that the "Restrict Access" Box was checked. So I unchecked it and
then restarted the CRM and Crystal Services on the CRM server.

Now the question is how did just two of the databases get set to Single user
mode during the weekend. The Database Maintenance plan should not do that,
but it turned out that manual backups were made on the databases.

Anyway, I hope this helps someone.

RE: Error 0x80044005 by CurtSpanburgh

CurtSpanburgh
Tue Oct 04 10:36:22 CDT 2005

Well , I can't say what happened in your case but here is what happened at a
client I was at.

Someone restored the CRM database from backup.

According to the Admin, the option to leave the database in "Read Only" mode
was not checked.

Nevetheless, when I checked the database in Enterprise Manager, there was
the CRM database in Single user mode.

sounds like a bug, so far. I searched the SQL logs, but found nothing.



"Curt Spanburgh" wrote:

> I have a client that was getting Error 0x80044005 this morning.
>
> The SQL server is seperate from the CRM Server.
>
> Event logs did not say much. The above error number is 2.
>
> I checked the Database server, opened up SQL Enterprise manager and found
> that two of the CRM Databases were set to single user mode.
>
> If you have this problem just Right client on the Database. Goto Properties
> and then the options tab.
>
> I found that the "Restrict Access" Box was checked. So I unchecked it and
> then restarted the CRM and Crystal Services on the CRM server.
>
> Now the question is how did just two of the databases get set to Single user
> mode during the weekend. The Database Maintenance plan should not do that,
> but it turned out that manual backups were made on the databases.
>
> Anyway, I hope this helps someone.
>
>
>
>
>