Dynamics GP Login Error
A user keeps getting this error:
"The stored procedure smCleanupFilesBeforeLogin returned the following results. DBMS: 0, Microsoft Dynamics GP 20505"
It started after two people made an attempt to open the same file at the same time. Now one of them gets this error when trying to login. She is able to login after she does the swich user ( her user ID ) but all dates are set at 00/00/0000 and her reports dont work. How would I clear the DBMS or what ever to close that attempt.
"The stored procedure smCleanupFilesBeforeLogin returned the following results. DBMS: 0, Microsoft Dynamics GP 20505"
It started after two people made an attempt to open the same file at the same time. Now one of them gets this error when trying to login. She is able to login after she does the swich user ( her user ID ) but all dates are set at 00/00/0000 and her reports dont work. How would I clear the DBMS or what ever to close that attempt.
You could try stopping and restarting the SQL Server service(s).
ASKER
That server has two other active DB's with about 40 clients attached so Im not able to at this time. It would be nice if I could start / stop it like IIS.
In SQL Server 2005 you can take a database offline, then back online, that might work.
ASKER
Can I do it in 2000 ? Thats what I run
Yes, you can do that in SQL Server 2000 as well, just right-click on the database, under "All Tasks" select the "Take Offline" then repeat to bring back online.
Were you able to get your issue corrected?
ASKER
No, Ive even restarted the SQL server itself, and she still gets the same error. This is nuts.
You could try clearing the system locks by running the query:
SELECT * from TempDB..DEX_SESSION where Session_ID not in (SELECT SQLSESID from DYNAMICS..ACTIVITY)
SELECT * from TempDB..DEX_SESSION where Session_ID not in (SELECT SQLSESID from DYNAMICS..ACTIVITY)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
LoL, I still get the error... Thanks but Im going to accept this and close this ticket. Thank for your help.
ASKER
the error is still here, but he was a big help