You’re offline. This is a read only version of the page.
1,275
My attempted move of my GP 9 from a Windows Server 2000 SQL 2000 database to a new Windows Server 2003 SQL Server 2000 box did not work. If I just stay on GP 9 $the goal was to upgrade to GP 10$, will tax updates and other stuff like that still be provided even though there isn't support anymore?
*This post is locked for comments
OK. Status update:
1. I deleted all of my company databases on the new server
2. I tried to create a company using GP Utilities. It would not let me even log on because there was no DYNAMICS database
3. I created a DYNAMICS database.
4. I went to the old server and did a database backup (DYNAMICS)using SQL Server.
5. I went to the new server and did a database restore using SQL Server.
6. I logged into GP Utilities and tried to create a new company. It told me the company already exists. I assume it got that from the DYNAMICS that I brought across.
7. I created a new company (TG1) using SQL server
8. I restored the TG1 database (using SQL Server)that I had backed up last week.
9. I logged back into GP Utilities. It told me I was only licensed for MS Access. I dug up the registration keys and got past that.
10. It updated the TG1 company.
11. I went into GP Dynamics and logged onto TG1.
12. I tried the things that weren't working last week and they are working now. I almost wish they weren't. I hate the inconstancy.
Now I will have to schedule a time to bring everything across again. It is month-end this weekend. So, it will probably have to be next weekend.
Sounds like a plan to me.
Step 1) Delete exisitng DYNAMICS database
Step 2) Detach your existing databases from old server
Step 3) Copy and attach them to the new server(this includes DYNAMICS database)
Make sure you have run the capture user script
Since you have already run GP utilties the DYNSA user should be in SQL. If not, install GP and go through the motion of having GP utilities create the DYNAMICS database again and then delete it.
OK. Here is a thought. I use the SQL Manager and delete the Dynamics databases. I then set up a new company using the GP Utilities (remember this is the same directory from the original server). I should then be able to run the restore and the scripts, etc. Does that sound feasible?
Yes, that would be a problem. Always create the GP databases using GP utilities. That is why you see your database names having GPS .....Dat.mdf names. It sets the logical anenms of the databases plus sets the database owner to be DYNSA.
I was reading another thread and the question was asked about having Symantec Endpoint Protection running on the server causing issues. I DO have SEP running on both servers.
Now, this "did you launch utilities and create the DYNAMICS database", I did not do. I used the SQL Manager and created the "empty" databases and used the restore to create the structures, etc. Do you think that might be the issue?
On the document, step 7 is where I am supposed to do a restore and I don't install the GP software until step 10. How could I use utilities (I assume you mean Dynamics Utilities) to create the Dynamics database?
If you continue to have trouble with this I would be willing to remote in and help out. It is too damn cold outside to do anything and I will just be studying for my SQL exam this weekend.
You should be able to copy across the GP application folder. But, I'm not sure that this is your issue.
It seems that the table definition for the UPR table seems to be different on the old and new servers.
Eithre the tables are actually different - or you have a different version of GP installed on the new (when you run a process, its trying to update / read from a column in a table, and it cannot find that column.
Certainly a second attempt at the transfer is on the cards.
In terms of the GP application folder - you should be able to install GP on the new server, and then copy across the contents of the Old GP application folder and overwrite what you just installed. (After you do this - search for any .cnk files in the application folder and delete them - otherwise, the first time you launch, these .cnk files will try and create new dictionaries)
This will ensure both GP installs are at excatly the same version. If you install in exactly the same folder on the new server, then you shouldn't need to change much once you copy over the old files - just maybe the Dynamics.set file.
Then if you set up SQL exactly the same as the old, same collation etc, and attach the databases, when you launch GP and connect to the new server, you should be OK.
Verify that your ODBC settings are correct - SQL Native Client, no tick boxes ticked etc.
One thing you could do after you copy the SQL data across is to do a 'select * from that UPR table' in both SQL's - and compare the column names.
Also, can you set up a new ODBC on the old server that connects to the new server? If you can, then you can rule out the GP application from the issue - if you can connect to the new server from the old GP application and still get the same errors - then its probably not GP? - its got something to do with how you are transferring the SQL databases across.
Time to head home and think about it tomorrow.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,113
Super User 2024 Season 2
#2
Martin Dráb
229,918
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (