MIcrosoft Dynamics CRM 3.0 "The specified Microsoft CRM server is not responding" when trying to open workflow manager.
When I try going to http://crmserver/loader.aspx I get the Authentication Error below:
When I try opening workflow manager (from the server) I get the Error below:
CropperCapture-17-.jpg
CropperCapture-19-.jpg
When I try opening workflow manager (from the server) I get the Error below:
CropperCapture-17-.jpg
CropperCapture-19-.jpg
Feridun Kadir
Ah, I think this might be that weird thing in CRM 3.0 where the administrator account defaults to being a restricted access account. Open the user record for the administrator account or whatever account you logged in with to get the above error and take off the restricted access setting.
ASKER
I cannot login! I get the error "authentication error."
Could I have some background to this?
Is this is a CRM system that was moved from one server to another?
Can any users login?
Are there any useful errors in the event log?
Is this is a CRM system that was moved from one server to another?
Can any users login?
Are there any useful errors in the event log?
ASKER
Is there any way to turn Microsoft CRM 3.0 into a heavy debug mode, so that I can try to figure out this issue?
ASKER
The CRM was restored from a production database to a test database, no one can login to the test system at this time..
In a different domain perhaps?
ASKER
Nothing useful in the event log..
ASKER
same domain
Is the test database on the same sql server as the production database?
Did you install CRM on a second server for testing and during the installation select connect to existing database and point the installation to the test database?
Can users connect to the original CRM database?
Did you install CRM on a second server for testing and during the installation select connect to existing database and point the installation to the test database?
Can users connect to the original CRM database?
ASKER
No, two different servers: From production server (which hosts sql 2005 & crm 3.0 application) to Test server (which hosts sql 2005 & crm 3.0 application)
No, this test server worked fine in the past & was always (and still is) pointed to it's own instance of SQL.
Yes, THANK GOD everyone can still connect to the production server.
No, this test server worked fine in the past & was always (and still is) pointed to it's own instance of SQL.
Yes, THANK GOD everyone can still connect to the production server.
OK I'm beginning to get the picture.
A few random thoughts:
- Did you restore an old copy of the production database or a recent one? Could there be an issue with Update Rollups is what I'm thinking.
- Have you tried running the redeployment tool on the test database? Because everything is in the same domain you shouldn't need to do this but you never know it might just fix something. The redeployment tool is on the CRM 3.0 CD.
A few random thoughts:
- Did you restore an old copy of the production database or a recent one? Could there be an issue with Update Rollups is what I'm thinking.
- Have you tried running the redeployment tool on the test database? Because everything is in the same domain you shouldn't need to do this but you never know it might just fix something. The redeployment tool is on the CRM 3.0 CD.
ASKER
-restored from a daily backup (recent)
-having trouble installing that tool
any other suggestions?
-having trouble installing that tool
any other suggestions?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
These where my steps used to resolve this issue:
1. Applied the same hotfixes as production.
2. Rebuilt the IIS c:\inetpub directory from production to test
3. Ran the CRM redeployment tool
1. Applied the same hotfixes as production.
2. Rebuilt the IIS c:\inetpub directory from production to test
3. Ran the CRM redeployment tool