If you did a SQL restore vs a dump/load then you need to make a couple of database edits. You used to get an error when the internal ORGID didn't match what was configured in database setup so this might not be it.

declare @NewOrgID as varchar(6)
select @NewOrgID = 'NLTDAT' --put your orgid here
update CSCOM set ORGID = @NewOrgID
UPDATE GL01 set COMPANYID=@NewOrgID  
UPDATE CSAUTH set COMPANYID=@NewOrgID 

Well, I tried that but it didn't work.  The orgid hadn't changed, but I figured what the heck and updated them anyways.  I wonder if there is some crash report that might help?

Take a look at all applications that are on the test server that are not installed or different version than the production server. 

Have you tried simply dumping and loading the data back in after performing the SQL restore?  I find this helps clean up any bizzare locks or strange states the backup may have been in when it was taken.  Keep using the ODBC connection and just dump your test database out and then load the DB dump straight back in.  Let us know how that goes.

Actually, there were some product updates on production that were not on test.  Once I updated test, it all worked great!  I did try the dumping and loading but it didn't work.  I just had to get everything in sync