Upgrading 7.5 -> 9

[Borvik]

Ok - we finally broke down and decided to upgrade from 7.5 to 9 (mainly to alleviate headaches - although it will most likely create new ones).

I've been working on a test upgrade (I copied all the databases to a local copy of SQL server).

Here is what I do:

Restore DB to local computer.
Install GP9 (server install - without Manufacturing).
Upgrade the local DB using GP 9 utilities (took 6 1/2 hours).
Backup local DB.
Install GP9 SP1.
Include new code into GP.
Input new registration codes:
Tools > Setup > System > Registration
Installed 3rd party addon.

The problem I'm having is that the sa user can login (using the SQL username/password used to get into Query Analyzer), but the other user's cannot.

I should clarify that - upon login of another user, GP9 requires the user to change their password. I do this and it kicks me right back to the login screen again - I use the old password and login fails, but when I use the new password I get an error " 'username' is not a valid user in database DYNAMICS."

Anyone know what might be going on?

 

[jymm]

which version of SQL? I know that when I made the leap to v9 I was already on 2005. It seemed to me that the security for v9 was MUCH better in that it was actually looking at the SQL login rules and also looking at AD.

SO - I had to go into SQL for the user's login properties and UN CHECK the 'Enforce Password Policy' as the users had some mixed case passwords before, but now the policies were important for these users (where as before they were not).

btw - I did same for test upgrade and never could get the user info to work on the test box - on the other hand the real upgrade went off without a hitch (except a few custom reports).

This help?

 

[Borvik]

SQL 2000 -> I know I'll want to get to SQL 2005 especially as I think I read (don't quote me on this) v10 will not be supported on 2000 (doesn't mean won't run - just unsupported).

I had a feeling it was because of the test box and that doing a real upgrade would probably work. I've just been pushing it off because I really don't want to screw it up.

Looks like I'll just have to break down and do it at some point.

Thanks jymm.

 

[jymm]

I also know that my test upgrade took about 3 times as long as the real thing... (although if you ask my boss it took just as long to do production as it did to do the test box - if you know what I mean)

again sql 2005 so ymmv --- btw, I was resistant to sql 2005 move - and after I put it in, wow a learning curve --- now? I can not imagine being back on 2000 (ok - it only took a few weeks before all of the cool tools and such along with some of the visual studio stuff started paying immediate dividends)... again ymmv

 

[Borvik]

Oh I'm not resistant to the SQL move (just hesitant as I don't want to screw everything up) - in fact I would love to move it over, but I'll take things one step at a time.

Yup, bosses will always do that. 3 times as long as the real thing - that is a welcome relief seeing it took all day just to run the test.

 

[jymm]

and I did the 2005 move first --- THEN the GP v9 --- go figure...

 

[Borvik]

Ah well - should still go, still waiting on our var to supply us with the final Reg codes for our 3rd party enhancements.

But, backup, backup, backup I think is the rule of thumb here.

Thanks for all the info jymm.

 

[dbigelow]

Are you doing a forced restore on a blank DB - if so there are issues with existing users in the forced DB's - try logging in before you upgrade if you crash then - big mess - sa will always work but the rest will crash out - there are some scripts that will drop the users and add the users back in so there log in will work - not sure what you mean on GP 9.0 requires you to change passwords but I will try to find those scripts if you would like

 

[Borvik]

A forced restore?

Not sure what you mean by that.

The test server didn't have those databases before, and I restored from several files.

 

[barbola]

UserIDs are also case sensitive with GP 9.

We've had the problem where you change a user password on the server, or a workstation, but it will only work on the computer it is changed on. If one of my users forgets their password, I have to reset it on their workstation, even if they are using Terminal Server, and even if I connect to the terminal server remotely, and change their password, they still can't use it.

b.

 

[Borvik]

barbola - Oh I know all about the case-sensitivity, in fact that's how (while doing the test) I'm sure that the users no longer work. Upon the test upgrade, when I logged in as another user it prompted to change password (purposely getting the login wrong, did not prompt that). Once changed I tried to login incorrectly again - it just said incorrect login, however upon using the correct credentials - it threw an absolute fit with the error I mentioned in the first post.