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

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) / SL 2018 CU1 client won...
Microsoft Dynamics SL (Archived)

SL 2018 CU1 client won't start on server

(0) ShareShare
ReportReport
Posted on by Stuart Nottingham 1,226

I've got a client who is upgrading from SL 7.0 to SL 2018 CU1. I've  installed the application and no errors displayed or were logged during installation. Databases upgraded successfully in Database Maintenance. When I try to login, I get the Find Database screen and am able to enter the servername and system database name. When the login screen appears (they're using SQL Authentication,) I enter the SYSADMIN id and corresponding password. Then crickets. No error displays on the screen, no menu appears on the screen, and no application appears in the Task Manager.

Looking in the Windows Apps Event Log, I find three entries detailed in the attached. If I'm reading it correctly, it seems to point to the .Net framework as an issue. I've verified that .Net is active in the server features and roles screen. Any ideas on resolution appreciated. I'd like to enjoy the holiday without this hanging over my head.

Error-starting.txt

*This post is locked for comments

I have the same question (0)
  • FMP Profile Picture
    FMP 15 on at

    I'm receiving the same error on SL 2018 CU2 on both the server and a Windows 10 client.  Does anyone know what could be causing this?

  • Brian_IL Profile Picture
    Brian_IL 719 on at

    .NET 3.5 is an optional component for both WIN10 clients and recent Windows server versions that SL requires. The client can be updated using Control Panel -- Add/Remove features. Installing .NET3.5 components from Server Manager requires the server installation media (files not copied to the server by default), or Windows Update may be able to download and install the correct .NET 3.5 features. Some network environments block external access or use an internal distribution server, which can take some additional configuration to get this setup working.

    Retracing setup steps often proves useful. I helped someone recently with a misconfigured Windows firewall on the server blocking workstation access to databases; opening a port for SQL for domain connections resolved the problem that the installer thought was already addressed. Setting up domain accounts with a user account in SL is another easily overlooked step for setups changing between SQL and WINDOWS authentication.

  • FMP Profile Picture
    FMP 15 on at

    Thanks Brian.  I added the .net 3.5 framework in windows features on Windows 10 and the error is still occurring.  I had done the same on the server when troubleshooting the error a few weeks ago and that didn't help.

    The database is accessible as you can get past the login and it gets the companies to select from.  Once you select a company the application closes. 

    Not sure where to go from here as the install of the SL 2018 CU1 client has worked fine with other clients on both a new server and Windows 10 clients.

    Any help is appreciated.

    Fred

  • Brian_IL Profile Picture
    Brian_IL 719 on at

    Look at the Windows - Application Event Log on the problem workstation and on the SQL server, see what error message may be recorded on either at the time of the failed login attempt. You may also want to use either SQL Profiler or review the SQL Extended Events to see if the problem being encountered is with the databases. Either approach should provide more detailed information to review.

    It sounds like an account is being denied access to the application database, since the database names are accessible when selecting from the System DB connection. Check the rights for the login user to the application database(s) used by those companies. You could rerun the SL Database Maintenance scenario to Update Views. You might also try switching DB security methods in DB Maintenance; i.e. from Windows security to SQL security, check the ability to login, then update back to Windows security, Switching authentication methods forces several triggers and stored procs to be dropped / recreated.

  • FMP Profile Picture
    FMP 15 on at

    I was able to fix the problem by resetting the SYSADMIN pwd.  It was related to an upgrade from SL7 to SL 2018 and password encryption.  The passwords are encrypted in SL 7 using an older algorithm that the newer SL version cannot decrypt.  

    Brian, thanks for the suggestions you provided though.

    Fred

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April 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