Error SCRIPT NAME GetLastCustomerGuid : 0

(0) Share

Report

Posted on by Napolo

766

We have moved our servers to a new environment over the weekend. During our testing phase, we have found the below errors during cash application(so far).

SQL Error SCRIPT NAME GetLastCustomerGuid : 0

ODBC Error SCRIPT NAME GetLastCustomerGuid : 0

GPS Error SCRIPT NAME GetLastCustomerGuid : 0

Does anyone know what this might mean? I have poked around the GP server and SQL server and things look the same as before the move.

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

KirkLivermont 5,985 on at

Like (0)

Report

Did you manually create the 32 bit ODBC connection on the client?

Was this reply helpful? Yes No
Napolo 766 on at

Like (0)

Report

Our IT Department simply copied over all applications and systems in one server environment and moved them to a new Soft Layer Server Environment. Everything seems to be working properly except for GP. Many pop up errors and the system hanging up. Is there something maybe our IT team missed with this kind of transition?

Was this reply helpful? Yes No
Suggested answer

babubaskaran@outloo... 12 on at

Like (0)

Report

Hi Nicole,

I am not sure how copying GP application from one server to another will work. If you are moving its better to install GP application on the new server. Please try to run Dynamics utilities and see whether that fix your issues.

Was this reply helpful? Yes No
Napolo 766 on at

Like (0)

Report

Our IT states: "The systems were moved as images so we did not install anything nor moved individual files."

We are getting the below SQL Server messages from the log every hour.

DBCC TRACEON 610, server process ID (SPID) 60. This is an informational message only; no user action is required.

DBCC TRACEON 2371, server process ID (SPID) 60. This is an informational message only; no user action is required.

I am going to check into the Dynamics Utilities. Will keep you posted.

Was this reply helpful? Yes No
KirkLivermont 5,985 on at

Like (0)

Report

Hi Nicole,

It sounds like your IT department did a physical to virtual conversion of your SQL Server. I am not sure exactly what is causing these issues but I believe best practice is to spin up a new Windows/SQL Server, and restore the databases from your current production server.

Good luck!

Kirk

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (1)

Report

We see this error when our users passcodes expire. They ignored the passcode change alert and have not since logged out of GP to get the passcode update request again. SQL expires it, so anything they try to run in GP throws error, because SQL password is expired already and won't validate request basically. If you think this may be your issue, our users just exit and go back into GP and the change passcode message pops up for them to do so. This is an old thread, so hope it has been resolved before now for you .... adding this for anyone else who may see it to try.

Was this reply helpful? Yes No
MG-16101311-0 26,225 on at

Like (0)

Report

To move your Dynamics GP application from one environment to another, you should have followed the steps outlined in KB article 878449 - support.microsoft.com/.../how-to-transfer-an-existing-microsoft-dynamics-gp-microsoft-small-busi. There's more to moving GP than just copy/pasting files and restoring databases.

Was this reply helpful? Yes No