Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics SL forum
Unanswered

SL 2018 Upgrade Workstation Error 9826

Posted on by 6,405

9826.png

Let me try to explain this odd situation.  Upgraded a client from SL 2015 to SL 2018.  New SL/SQL server was added (named DYNAMICS) to the domain to host SL 2018 and SQL.  SL 2015 server was named DYNAMIC2.  Running SL on the server worked great.  Trying to connect an SL 2018 workstation error threw the 9826 error.  When I moved the databases back to the DYNAMIC2 server, the workstations could connect to them with no issues.

Through much troubleshooting and review, realized way back on SL 7 the host server on the domain was also named DYNAMICS (same as SL 2018 server).  On a hunch, we renamed the DYNAMICS server to MSDYNAMICS and the SL 2018 clients could connect to the renamed server.

I'm sure somewhere in the environment there was still something that was referencing the old DYNAMICS servers SL 7 SIVSYS database (even though it was no longer connected to the domain), but I am not sure what that would be.

While we resolved the issue by renaming the new server, I would sure like to know why reusing the old servername on the domain was throwing this error.  Not something that I had recommended, but their IT staff built the server (Hyper-V by the way) on their own and turned it over to me.

Thoughts and ideas are appreciated.

  • Mark E Profile Picture
    Mark E 6,405 on at
    RE: SL 2018 Upgrade Workstation Error 9826

    Not sure.  We just did a simple stop/start of SQL services and it all started to work on the clients.  Did not change much during the day, and the users were connected to the server via RDWeb, so we know SQL was running before and SL users were active during the day.  Will see what tomorrow brings.

  • Laura Profile Picture
    Laura 450 on at
    RE: SL 2018 Upgrade Workstation Error 9826

    Something in the DNS settings? I am no expert, just a thought.

    Beyond my knowledge, but interested in hearing the final resolution.

  • Mark E Profile Picture
    Mark E 6,405 on at
    RE: SL 2018 Upgrade Workstation Error 9826

    Yes to both.  If I move just the databases back to the old SQL Server, the clients can connect to them.  Just not on the new database server.  Still using the new server to run the SL programs.

  • Laura Profile Picture
    Laura 450 on at
    RE: SL 2018 Upgrade Workstation Error 9826

    Did you apply CU5 to the server? Did you install CU5 on the workstation?

  • Mark E Profile Picture
    Mark E 6,405 on at
    RE: SL 2018 Upgrade Workstation Error 9826

    I have been removing the old server names from the solomon.ini file in the PC roaming profile but that has not worked.  Unless the PCs are looking to another location on the domain for the ini file, checking with their IT staff.

  • Laura Profile Picture
    Laura 450 on at
    RE: SL 2018 Upgrade Workstation Error 9826

    Having the old SQL Server name in the Solomon.ini was our issue.  Updated it and all good so far.

  • Laura Profile Picture
    Laura 450 on at
    RE: SL 2018 Upgrade Workstation Error 9826

    I am checking to see if the Solomon.ini for the user (C:\Users\username\AppData\Roaming\Microsoft Dynamics SL ) is holding the prior SQL Server since the servers changed but the database names did not. On the server I log on without an issue.

    I know sometimes IT use different ways of maintaining the User Profiles - so we are checking that first.

  • Mark E Profile Picture
    Mark E 6,405 on at
    RE: SL 2018 Upgrade Workstation Error 9826

    Do you know what the issue is then?

  • Laura Profile Picture
    Laura 450 on at
    RE: SL 2018 Upgrade Workstation Error 9826

    We just ran into the same situation. SL 2015 and upgraded to SL 2018 CU5. Server names or SQL names are not the issue. 

  • Mark E Profile Picture
    Mark E 6,405 on at
    RE: SL 2018 Upgrade Workstation Error 9826

    Update on this (running SL 2018 CU5); apparently the servername issue was just a ruse.  While it worked for a single day, now we are running into the same issues again.  First issue was 5003 error trying to connect to the System DB (4060).  Checking the Server Application Event Logs, we are seeing where there is a database connection error while attempting to connect with the CD8359B5576446f85EB67E824B4770 sql user (Reason: Failed to open the explicitly specified database 'SIVSYS'.) for which the sql user does not exist.  We are running Windows Authentication, and it is my understanding that this SQL user is only relevant when using SQL authentication as the method.

    So one of the solutions I read was to use Database Maintenance to change the Authentication to SQL and then back to Windows.  That creates the CD835 user.  It was after that the above 9826 message appears (which I guess is some embedded message that tells SL if you are connecting with this method the database is an older version?).

    I seem to have exhausted all the KB knowledge suggestions for resolving the 5003 errors.  SL 2018 CU5 clients will just not talk to the new server.

    Again, if I move the databases back to the original server, everything works correctly.  Why are the SL 2018 clients attempting to communicate via SQL security to the server during initial login when using Windows Authentication?

Helpful resources

Quick Links

Replay now available! Dynamics 365 Community Call (CRM Edition)

Catch up on the first D365 Community Call held on 7/10

Community Spotlight of the Month

Kudos to Saurav Dhyani!

Congratulations to the June Top 10 community leaders!

These stars go above and beyond . . .

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 287,696 Super User

#2
Martin Dráb Profile Picture

Martin Dráb 225,490 Super User

#3
nmaenpaa Profile Picture

nmaenpaa 101,148

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans