jhalliday
Guest
|
Posted:
Tue Feb 15, 2005 10:24 pm Post subject:
BizDesk startup problems |
|
|
Hello all,
This problem is regarding a BizDesk problem on our Demo environment on
a Win2k3 box with the web, commerce, and db servers all on the same
box.
BizDesk hadn't had any problems starting until we changed the password
for the local administrator account (which from what I can tell isn't
even used in our CS setup). BizDesk is now throwing the following
error:
-----------------------------------------------------------------
-----------------------------------------------------------------
Technical Information (for support personnel)
Error Type:
Microsoft Commerce Configuration (0x80004005)
Cannot open database requested in login 'MSCS_Admin'. Login fails.
SiteConfigReadOnly:Initialize
/LM/w3svc/1/Root/NEJOnlineSiteBizDesk/global.asa, line 118
Browser Type:
Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322)
Page:
GET /NEJOnlineSiteBizDesk/bizdesk.asp
Time:
Monday, February 14, 2005, 4:19:27 PM
More information:
Microsoft Support
---------------------------------------------------------------
---------------------------------------------------------------
The only other thing I can add is that this error is thrown immediately
after startup. There is no waiting for a connection to fail/timeout,
or any other general lag. As soon as you open BizDesk the error is
immediate.
I have done the following so far to try to resolve the issue:
1. Reset local administrator password back to the old password to see
if we could get a quick fix. The password is currently set back to the
old password.
2. In commerce server manager, test out all connection strings. Admin
database connection string connects without a problem.
3. I started a trace in SQL Profiler to try to see if there was an
access attempt failing for our admin database. Curiously, it doesn't
seem to even make it this far in the process. Starting BizDesk doesn't
cause any access attempts that I can see in Profiler.
4. Went to Component Services -> COM+ and checked to make sure all of
our identities were intact and correct. Again, none of this
information was changed/touched throughout the process.
5. I have read other posts with people having similar problems and have
tried various other fixes, all to no avail.
Has anyone else bumped into a situation like mine or have any ideas as
to what the cause could be? As always, any help would be greatly
appreciated.
Thanks,
Jon |
|