Moving Existing Dynamics GP 8.0 to New Server

(0) Share

Report

Posted on by Community Member

Hello,

I am currently running a Windows Server 2003 box that has many problems and I have been tasked with moving it to new hardware running the same OS and version of Dynamics GP 8.0. I have a new box running Windows Server 2003 and SQL Server 2005 Express. Can I successfully move our instance of GP 8.0 over to the new box without losing anything? I managed to install GP 8.0 on the new box, but I'm not sure how to go about moving the old database over. Can anyone help?

*This post is locked for comments

All responses (38)

Answers (0)

Mariano Gomez 26,225 on at

Like (0)

Report

RE: Moving Existing Dynamics GP 8.0 to New Server

Thanks for the "young kids" part. Unfortunately, my mind says do one thing, but my body does not respond quite in the same manner :-)
Richard Wheeler 75,848 Moderator on at

Like (0)

Report

RE: Moving Existing Dynamics GP 8.0 to New Server

Darn, getting old sucks. You make mistakes like this. Thanks for the catch Mariano! You young kids never miss anything.
Mariano Gomez 26,225 on at

Like (0)

Report

RE: Moving Existing Dynamics GP 8.0 to New Server

I would also BACKUP system and company databases then run a check links against each one of the GL transaction tables. Chances are, if you had transaction level posting issues, you may have orphan records somewhere.
Mariano Gomez 26,225 on at

Like (0)

Report
RE: Moving Existing Dynamics GP 8.0 to New Server

The script in the link posted by Richard has a syntax error:

SELECT * from SY00500 whereBACHNUMB = 'xxx'

If you look at it carefully, there must be a space between the where clause and the column name, and instead should read:

SELECT * from SY00500 where BACHNUMB = 'xxx'
Bill Campbell 12 on at

Like (0)

Report

RE: Moving Existing Dynamics GP 8.0 to New Server

When a user is disconnected from the system - your case the Terminal User is dropped and the session is not correctly reconnected and then someone cleans up the Terminal Server Users who show disconnected - SQL still thinks there was a connection - now it has to hold onto that - that is what I believe Richard means when he mentions disconnect.

Have a great day.
Community Member on at

Like (0)

Report

RE: Moving Existing Dynamics GP 8.0 to New Server

These issues are happening directly on the server. The accounting personnel Terminal into the server and use it directly on the server, so I don't think it's a network issue.
Richard Wheeler 75,848 Moderator on at

Like (0)

Report

RE: Moving Existing Dynamics GP 8.0 to New Server

I would check the other companies and hopefully you find none. It is fine and dandy to fix this but the bigger question is why are they here in the first place. You may want to have your network checked and make sure there is not a disconnect issue.
Community Member on at

Like (0)

Report

RE: Moving Existing Dynamics GP 8.0 to New Server

I should remove them from just the SY00500 table, correct? Should I check each company's database for entries like this?
Bill Campbell 12 on at

Like (0)

Report

RE: Moving Existing Dynamics GP 8.0 to New Server

Richard thanks for posting the link - it lead me to the end of it where the question is asked 'what is XPM_CHec' and that is where I was going.

I think you are right - as I recall my notes - when you end up with the user name in what should have been a completed batch processing - it is 'hung up'

So, I would have to agree - it is best to remove them - make the backup of the table of course - then remove the offending lines.
Richard Wheeler 75,848 Moderator on at

Like (0)

Report

RE: Moving Existing Dynamics GP 8.0 to New Server

I just tried an online posting from sales.

Under BACHUMB I see RMSLS00000700

Under BCHSOURC I see GL_Normal

https://dynamicsgpland.blogspot.com/2014/09/dynamics-gp-bchsourc-values.html

These are the valid values for BCHSOURC. The combination of the BACHNUMB being the user name and the X prefix in BCHSOURC leads me to believe these are the offending entries. To be safe, perform a backup and then delete them.