Quantcast
Channel: Microsoft Dynamics SL
Viewing all articles
Browse latest Browse all 7845

Forum Post: Dynamics SL 2015CU2 Single User login failure

$
0
0
Upgrading client to SL2015CU2. They're a small single-user operation and I would have thought this would be a piece of cake (what was I thinking?) The installation of everything seemed to go fine. I copied the MDF and LDF files for the databases from the old workstation and attached them to the new SQL2014 incident on the new workstation; database maintenance went through smoothly. However, when I try to login to the application, I'm able to select server, system database name, enter user ID and password and select company. At that point, the login fails with the dreaded "...has stopped working" message. Looking at the windows event, I see the following: Log Name: Application Source: Application Error Date: 8/17/2017 5:14:41 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: SERVER Description: Faulting application name: MSDynamicsSL.exe, version: 9.2.41201.2, time stamp: 0x58406931 Faulting module name: MSVCR110.dll, version: 11.0.51106.1, time stamp: 0x5098858e Exception code: 0xc0000409 Fault offset: 0x0009f967 Faulting process id: 0x20d0 Faulting application start time: 0x01d3179dc3d0b7bf Faulting application path: C:\MDSL\SL\Applications\MSDynamicsSL.exe Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR110.dll Report Id: 8db8517f-4e03-44bd-aca5-530ec725a1b2 Faulting package full name: Faulting package-relative application ID: I verified that the MSVCR110.dll file is in the system32 folder. I have uninstalled/reinstalled SL. I've rerun the Database Maintenance Process. I've looked at the Hotfix list and didn't find any that appeared to be related for this version. Any ideas on how to fix this? Any help appreciated as always. Stuart Nottingham

Viewing all articles
Browse latest Browse all 7845

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>