Had to do a site shutdown this weekend and when the SQL server came back online it seems to have dropped theStoredProcedure:
smCleanupFilesBeforeLogin.
Users are getting this error when logging on to Dynamics GP10:
Stored Procedure smCleanupFilesBeforeLogin returned the following results: DBMS: XXX, Great Plains:XXX
This KB article has instructions on fixing the error we get http://support.microsoft.com/kb/849708
I've used Resolution 1 from this KB Article and downloaded the smCleanupFilesBeforeLogin script, but now the script reported that smAddPostingSecurityRecord is also missing. Trying to find it online atm, but so far nothing.
Can anyone help, please?
Thanks,
Trevor.
*This post is locked for comments
To add on Vinutha's great answer, if you do not have those directories, you need to extract the SQL resources out of Dynamics. To do so, you need to edit your Dex.Ini look for the following line "duExtractSQLResources" if its not there add it and assign a true value, line should look like the following:
duExtractSQLResources=TRUE
run Dynamics Utilities and you will see after the version information check that will extract all the products, then you will have the directory structure that Vinutha is referring to. Remember to delete the line or change from TRUE to FALSE.
Regards
Francisco
Hi Trevor,
To re-create the stored procedure smAddPostingSecurityRecord, I have listed the steps below. You will not be able to re-create the stored procedure correctly if the role DYNGRP does not exist.
1. Navigate to the directory where Great Plains is installed. By default Dynamics GP is installed in the following directory.
C:\Program Files\Microsoft Dynamics\GP\
Now open the folder SQL, open the folder Install, open the folder 0 and open the folder Company. If Dynamics GP was install using the default configuration you should be in the following directory.
C:\Program Files\Microsoft Dynamics\GP\SQL\Install\0\Company
2. Using Notepad open the file named Procs.cmp. Copy everything between /*Begin_smAddPostingSecurityRecord*/ and /*End_smAddPostingSecurityRecord*/ to a new notepad.
3. Perform a find and replace to replace %SysDbName% with DYNAMICS.
4. Now paste the contents into a query window in the SQL Server Management Studio. Run the query against the company databases.
Regards,
Vinutha
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156