GP9 problems with terminal server and other issues 2

[barbola]

Upgraded from 7.50 on the weekend and all hell broke loose today. Payables won't print, and user's computer is now frozen, waiting for a call from vendor.

On another issue, during the test upgarde the Vendor said I didn't have to convert the Test company, just restore an active one over it, and I did that and now can't even open GP Utilities...I get some kind of version error on the Test company. Also waiting for a call on that.

We didn't test FRx 6.7, and I was told it was very basic, but I got fatal errors. So now I get to read the 100-page instructions.

Practically none of our reports work. This was tested but the vendor didn't tell me there were errors! Maybe I should have asked?

But one big issue, I am trying to install GP9 on a terminal server, and it freezes up on me. It didn't appear to have worked, so I uninstalled, deleted the folder as it didn't go away (there were a few files left)...and now it is frozen again trying to include new code.

Any help is much appreciated.

thanks.

 

[jazgeek]

shoot the var........

reports are always a problem from version to version. I used to spend half my consulting hours doing report conversions from one ver to the next

frx..... sorry can't help you there

terminal server... try installing from the console after a fresh reboot and use the add/remove programs to run cdsetup instead of allowing the autorun to do it's work.



-----------
and they wonder why they call it Great Pains!

jaz

 

[RobertC22]

TEST Company
------------
When upgrading I agree that the test company doesnt need to be run through the conversion process. This reduces time required.

However if you restore the upgraded production database as the test database, there are several tables that need to be manually adjusted in the DYNAMICS database so Great Plains does believe that the test database is now in Version 9.0 rather than version 7.5.

These include DU000020, DB_Upgrade.

If you have third party products, these may have their own version control table in the DYNAMICS database that needs to be adjusted. Example using Wennsoft, the table is WS_Upgrd.


Reports
-------
IO agree with Jaz in that when I used to upgrade, more than half the time was getting the 'non-upgradeable' reports fixed and ready for deployment under the new version.
Did you Vendor leave you with clear instructions on the reports that were modified and where they left the modified reports dictionary ready for deployment?


Terminal Server
---------------
Remove the registry entries as well. Read the SP1 update notes (and KB) to find out what registry entries you may need to remove.


With version 9.0 it tracks the different 'instances' of Great Plains you have installed, and whether the instance was for 'client' or 'server' mode.

As Jaz mentioned, ensure you run the install from the Add/Remove programs in Control Panel, rather than using the Autorun!

FRX 6.7
-------
Usually not a biggy, but if the Vendor had done his job, he would have a folder with the upgraded FRX 6.7 sysdata and specsets.
This upgrade to FRX 6.7 (done during the test upgrade) should have been run against the database generated by the test upgrade to your satisfaction.


------
Robert

 

[barbola]

Thanks for the helpful information guys!
Reports:
I ended up restoring alot of the old reports, and they seem to work. The log file from the test was yay long so I figure I'll re-create the reports that are really messed up, no biggie, and so far there are none.

Test:
I was given some scripts to run against DYNAMICS.
Delete DB_Upgrade where db_name = 'TEST" and PRODID = '949'
Delete DU000020 where companid = xxx and PRODID = '949'
Delete DU000030 where companid = xxx and PRODID = '949'

Well, all three gave 0 records updated. So, I'm thinking maybe I need to ADD a record for this company to that DU000020 table? The VAR is looking into this one.

Terminal Server:
I always use Add/Remove programs for the application (not the servicepacks) and also for the 3rd party. My remote session was freezing, and I kept closing it and opening a new one, so it turned out that I had 4 sessions running!

So I uninstalled GP9 from the Terminal Server for the second time, but I guess I am missing deleting some registry files. I will do that and try again.

FRx:
We didn't test this because we sort of ran out of time, but I was told it would be a basic install. I've read some of the instructions and it says I can treat it like a new install and still get the opportunity to upgrade the Spec Set...but I'm not going to do anything until I understood the 102 page manual I printed!

Thanks so much for your help!

barb

 

[RobertC22]

Barb,

Here is a script that should update those tables for the test database.
Please replace TWO with your production database, as TEST with the name of your test database.
Be aware that the numbers of records reported as deleted should be one, whereas the number added will depend on the number of products selected when you installed GP 9.0

Highly suggest take a backup of DYNAMICS db before doing this, then afterwards check you can get into both your production and test databases.

/* ################ */
/* table DB_Upgrade */
/* ################ */
begin tran


delete from DYNAMICS..DB_Upgrade where db_name = 'TEST'

print 'removed TEST from DB_Upgrade : ' + str (@@ROWCOUNT)

insert DYNAMICS..DB_Upgrade 
( [db_name], [PRODID], [db_verMajor], [db_verMinor], [db_verBuild], [db_verOldMajor], [db_verOldMinor], [db_verOldBuild], [db_status], [start_time], [stop_time] )
select 'TEST', [PRODID], [db_verMajor], [db_verMinor], [db_verBuild], [db_verOldMajor], [db_verOldMinor], [db_verOldBuild], [db_status], [start_time], [stop_time]
from DYNAMICS..DB_Upgrade  where db_name = 'TWO'

print 'added TEST using TWO from DB_Upgrade : ' + str (@@ROWCOUNT)



/* ############## */
/* table DU000020 */
/* ############## */

/* remove old v7.5 entries */
delete from DYNAMICS..DU000020 where companyID = (select CMPANYID from DYNAMICS..SY01500 where INTERID = 'TEST')

print 'removed TEST from DU000020 : ' + str (@@ROWCOUNT)


/* copy v9.0 entries */
insert DYNAMICS..DU000020 
	( [companyID], [PRODID], [versionMajor], [versionMinor], [versionBuild] )
select (select CMPANYID from DYNAMICS..SY01500 where INTERID = 'TEST') companyID,
	[PRODID], [versionMajor], [versionMinor], [versionBuild]
from DYNAMICS..DU000020 
where companyID = (select CMPANYID from DYNAMICS..SY01500 where INTERID = 'TWO')

print 'added TEST using TWO from DU000020 : ' + str (@@ROWCOUNT)


/* ############## */
/* table DU000030 */

delete from DU000030 where companyID = (select CMPANYID from DYNAMICS..SY01500 where INTERID = 'TEST')

print 'removed TEST from DU000030 : ' + str (@@ROWCOUNT)


/* no need to insert records for DU000030 ... */

For reports, V8 introduced the ability to reprint historical SOP documents in a group, whereas previously you could only do one at a time. If you had a modified layout for any of the SOP History layouts, you will need to redo those for them to work correctly.


------
Robert

 

[barbola]

OK I'm not touching anything else. Something is terribly wrong and my VAR escalated my case so I am currently waiting for a call from Microsoft.

The test company is the least of my worries. Users are okay, working fine and dandy in the other companies.

But, I cannot get into GP Utilities on the server. I am getting invalid version errors, yet everything is at the correct version.

This is what I did last weekend:
I installed GP9.0 on the server
I installed SP1 on the server
I updated all the companies
I updated some workstations
Everything was fine
I installed SP1 for Canadian Payroll (tax update)
I had to run thru update of all companies again (grrrr took 4 hours)
I had to update ALL the workstations again, even the ones without Cdn payroll.
Fine, all users could work.

But now I can't get into utilities.

Also, can't even open GP on the SQL Server.

I think I will just wait for MS to call. I am off for the next 5 days....or so I thought. *sigh*

i need chocolate!

 

[barbola]

Well, we got this fixed up. I installed the Server version on my client workstation and applied the servicepacks and was able to get into Utilities.

Microsoft helped my delete that Test company right out of the system.

I have to some in on the weekend and re-install the GP 9 application on the SQL server, then apply the CPY SP1 (didn't know it was all-inclusive) and then install the 3rd party product.

Wish me luck!!!

b.