You’re offline. This is a read only version of the page.
Announcements
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
One other thought, try running a SQL trace on the SQL end and see if that shows any incoming activity. If not, then the SL login screen is not getting any packets over to that instance of SQL and that would mean that the workstation likely has an unregistered DLL. In answer to you prior question, DB Maint uses an entirely different process to connect to SQL then is used by the SL database find process (according to the SL developers). However, they do not share what the difference is, at least when I asked.
Thanks for the additional info. I did not hear back as to whether this is a new workstation and whether it can connect to the old SQL box or not. If it can then the next though does not apply but, just in case, make sure capicom.dll registered. This issue is also driving me nuts because I know I have encountered it before and eventually got it working so I will continue to go through my call logs. Did you even verify what version of SL 2011 is being used (SP! or FP1)?
There is a knowledgebase article at support.microsoft.com/.../875704, title of Error message when you try to log on to Microsoft Dynamics SL: "System Message 5003 - Unable to open the specified server database."
It has 12 possible causes, and 15 resolutions to try. We had our network technician, our Solomon expert, and me, the Sql programmer, going through the document for hours. Every resolution that could have any bearing was tried. (Stuff like Cause 4, database name begins with a number, could be overlooked because it was obviously not the case.)
The only thing hinting at a discrepancy was in Resolution 8, where we were to verify that the file version of capicom.dll was 2.1.0.1. Ours is 2.1.0.2, and shouldn't it be backward compatible?
That should give you a pretty clear ideal of what we've tried so far.
I just remembered someone in another recent thread said he fixed a similar situation by resetting the SYSAdmin account to his Windows account:
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.
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.)
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.)
Sorry ... I was thinking I read SQL 2012, not Windows 2012.
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.
For SQL 2012, you either have to be on SL 2011 with SP1 and a hotfix, or running FP1. Are either of those true?
#1
André Arnaud de Cal...
291,359
Super User 2024 Season 2
#2
Martin Dráb
230,370
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
