web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics SL (Archived) / Unable to access SL on...
Microsoft Dynamics SL (Archived)

Unable to access SL on new sql server

(0) ShareShare
ReportReport
Posted on by Bev Kaufman 280

We have a working SL 2011 installation, connected to Sql 2008 SP3 on a small business server.  We wish to move the database to a Windows 2012 server, and will not make the switch until we have confirmed that the new system works.  Therefore, the SBS database is still up and running.

The problem is that our SL installation is not able to see the Windows 2012 server. DB Maint is able to access the new server, and all updates have been run successfully. But when we try to load the new database, it fails to connect at the Find Database level, never getting to the point where you can select a system database. The error is system message 5003.

We downloaded the extensive documentation offering 12 possible causes and 15 possible resolutions, and all of these have been examined and attempted when apt.  Nothing works.

We examined the server and database security and found no differences between the two systems.

Any clues to what's happening?

*This post is locked for comments

I have the same question (0)
  • Butch Adams Profile Picture
    Butch Adams 4,763 on at

    By SL 2011, do you mean RTM or is it a later version?

  • Community Member Profile Picture
    Community Member on at

    You indicated you have tried seveal things so I do not know if you looked at this or not but, if the Windows firewall is active you will need to allow the SQL Browser through that firewall and, even if you did this for the old server, the new server will have it at a different location.

  • Bev Kaufman Profile Picture
    Bev Kaufman 280 on at

    Our tech tried adding ports, and then completely disabled the firewall - which is not a situation we want to live with - and it has no effect on the problem.

    And there is something else that I should have mentioned. If you enter the IP address of the Sql Server into the Server field of the Find Database dialogue, you can then see and select a system database. Of course you can't get any further than that because the Domain record contains the name of the server, and not the IP address, so we just get a different error.

    I also pinged the sql server using both the name and the IP address, and it connected both times. This means the OS recognizes the server by name, but SL doesn't.  Does that help?

  • Butch Adams Profile Picture
    Butch Adams 4,763 on at

    For SQL 2012, you either have to be on SL 2011 with SP1 and a hotfix, or running FP1. Are either of those true?

  • Bev Kaufman Profile Picture
    Bev Kaufman 280 on at

    I'm pretty sure I saw FP1 in the DB Maint update menu.  However, we're on Sql 2008 SP3, not SQL 2012.  The sql server is installed on Windows Server 2012.

  • Butch Adams Profile Picture
    Butch Adams 4,763 on at

    Sorry ... I was thinking I read SQL 2012, not Windows 2012.

  • Butch Adams Profile Picture
    Butch Adams 4,763 on at

    I see you are trying to move the server the db's reside on ... did you update the domain and company tables with the new server name? (It was probably part of the long list of causes/resolutions you mentioned, but I am just checking.)

  • Bev Kaufman Profile Picture
    Bev Kaufman 280 on at

    Yes, definitely. I don't think I could have run the DB Maint updates if I hadn't. That's one of the things I can't get my head around. DB Maint's an SL tool, and it found the new server just fine. What is the SL application looking at that's different? Is there a config file I never heard of where I need to enter the new server name? (I knew changing the Solomon.Ini database and server settings wouldn't work, but I tried it anyway.)

  • Community Member Profile Picture
    Community Member on at

    This is kind of hard to offer suggestions when we do not know what you have already tried.  So, perhaps a short list of what you have check would save suggestions that you have already done.  However, just to add to the dialog, did you check the network protocols on the newer sever to make sure that named pipes and tcpip are enabled?  And, if using Windows authentication, are the users set up under SQL security?

    I know this is a challenge.  I have run into a similar issue before where DB maint can get to the server but not the SL Login.  One last question, you did not say if this is a workstation that can get to the old SQL server or if it is a new workstation and if the workstation is a Windows 7 workstation.

  • Butch Adams Profile Picture
    Butch Adams 4,763 on at

    I just remembered someone in another recent thread said he fixed a similar situation by resetting the SYSAdmin account to his Windows account:

    community.dynamics.com/.../218246.aspx

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics SL (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans