GP 10 upgrade - Field Service 949 hangs up Upgrade

[davidf.]

I am working on a test server. A current copy of GP 9.0 was installed with my
company databases. I verified everything works as on the production
environment.

Used the Feature Pack 1 download to install the upgrade due to the .net 2
problem. I have one add-on - CertiTax sales tax plugin.

Our company uses the Field Service module for Contracts and RMA.

I get to the point where everything's installed including SP3 and now I'm
ready to open Utilities to update the companies/tables and get the error
message " The stored procedure SynchronizeTableData() of form
duSQLAccountSynch :27 Pass Through SQL returned the following results: DBMS:
2601, Microsoft Dynamics GP: 0 " and the update stops.

I look at the install log and see that the last entries reference 949 which
is the Field Service number so I modify the Dynamics.set and Dynutils.set
files taking out the references to 949. Now the upgrade works and proceeds on
to updating the company tables.

Unfortunately I really NEED Field Service to work. What am I missing? Is
there a separate install of Field Service that I need to do?

I made a ghost copy of my test server before starting the upgrade so I will
reload that image and start over Monday.

Thanks,
DavidF.

[davidf.]

Any ideas on this? I am reloading the ghost image taken right before I did
the upgrade from GP 9.0 to 10.0 sp3.

This time I'm going to try just upgrading to the FP1/SP2 and try to rule out
if there was a problem with going straight to SP3.

Thanks,
DavidF.

Post by davidf.
I am working on a test server. A current copy of GP 9.0 was installed with my
company databases. I verified everything works as on the production
environment.
Used the Feature Pack 1 download to install the upgrade due to the .net 2
problem. I have one add-on - CertiTax sales tax plugin.
Our company uses the Field Service module for Contracts and RMA.
I get to the point where everything's installed including SP3 and now I'm
ready to open Utilities to update the companies/tables and get the error
message " The stored procedure SynchronizeTableData() of form
2601, Microsoft Dynamics GP: 0 " and the update stops.
I look at the install log and see that the last entries reference 949 which
is the Field Service number so I modify the Dynamics.set and Dynutils.set
files taking out the references to 949. Now the upgrade works and proceeds on
to updating the company tables.
Unfortunately I really NEED Field Service to work. What am I missing? Is
there a separate install of Field Service that I need to do?
I made a ghost copy of my test server before starting the upgrade so I will
reload that image and start over Monday.
Thanks,
DavidF.

[Chris Reston]

Did you ever resolve this I am having the same issue, if you did what was the trick?

Post by davidf.
I am working on a test server. A current copy of GP 9.0 was installed with my
company databases. I verified everything works as on the production
environment.
Used the Feature Pack 1 download to install the upgrade due to the .net 2
problem. I have one add-on - CertiTax sales tax plugin.
Our company uses the Field Service module for Contracts and RMA.
I get to the point where everything's installed including SP3 and now I'm
ready to open Utilities to update the companies/tables and get the error
message " The stored procedure SynchronizeTableData() of form
2601, Microsoft Dynamics GP: 0 " and the update stops.
I look at the install log and see that the last entries reference 949 which
is the Field Service number so I modify the Dynamics.set and Dynutils.set
files taking out the references to 949. Now the upgrade works and proceeds on
to updating the company tables.
Unfortunately I really NEED Field Service to work. What am I missing? Is
there a separate install of Field Service that I need to do?
I made a ghost copy of my test server before starting the upgrade so I will
reload that image and start over Monday.
Thanks,
DavidF.

Post by davidf.
Any ideas on this? I am reloading the ghost image taken right before I did
the upgrade from GP 9.0 to 10.0 sp3.
This time I'm going to try just upgrading to the FP1/SP2 and try to rule out
if there was a problem with going straight to SP3.
Thanks,
DavidF.

[l***@hotmail.com]

Post by Chris Reston
Did you ever resolve this I am having the same issue, if you did what was the trick?

In case someone else landed on this page, I resolved this issue by deleting some entries in the ASIEXP86 table related to Field Service.

Run the following script to find out if there are invalid entries.
SELECT * FROM DYNAMICS..ASIEXP86
WHERE ASI_Field_Number NOT IN (SELECT ASI_Field_Number FROM DYNAMICS..ASITAB20)

If the above SQL Script does not show any result or too many, you might have to enable your DEXSQLLOG to get the specific record(s).

Mine showed nothing the above SQL Script but the DEXSQL Log showed the specific record that is causing me grief.

This was my SQL Script:

delete DYNAMICS..ASIEXP86
where ASI_Favorite_Dict_ID = 949
and ASI_Favorite_Type = 26005
and ASI_Favorite_Save_Level = 1
and CMPANYID = 0