Share
Report
26Does anyone have experience with clients that have moved an existing Dynamics Gp Installation to a new server by cloning the original virtual Sql Server and not following the protocol in the document /How to transfer an existing Microsoft Dynamics GP, Small Business Financials, or Small Business Manager installation to a new server that
is running SQL Server/
is running SQL Server/
I originally opened this case because a client's IT dept cloned their server to a new server without consulting anyone. Five days later they experienced messy posting interruptions with the error
/Could not allocate space for object /dbo/ PJournal.
To resolve their problems I tried to upgrade to the latest GP version but wasn't able to complete the it do to unresolved errors, but that's another story. I ended up doing a fresh install of the original version and restored to a backup prior to the upgrade. So, I essentially ended up following the procedures in the document listed above.
Fast forward to another scenario where a new client, cloned their previous server. To further complicate things I couldn't do a fresh install because they have 3 3rd party products. It was over the weekend. I ended up doing a Dynamics GP Repair until I could open a support request with GP. I've been running the script to delete the PJournal so they don't bomb during posting.
I just heard from GP and their answer was: If you ran a repair, then you essentially already did a uninstall/reinstall as a repair on GP will remove all third-party products. I'm just wondering if anyone has cloned their server, run a Dynamics GP Repair successfully and no other action was required? I don't want to chance just letting it go if the repair was not sufficient.
FYI, from my experience with this scenario, the three 3rd party products were not removed when I ran the /repair/. It's possible it may remove some but it did not in this case.
Categories:
All responses (
Answers (
