Trying to upgrade to GP 2016 R2

(0) Share

Report

Posted on by Community Member

I'm trying to upgrade from GP 2015 R2 to GP 2016 R2, but am running into an issue. If I run this

SELECT b.fileOSName, a.fileNumber, a.PRODID, a.Status, a.errornum, a.errordes, c.CMPANYID, c.INTERID
FROM DYNAMICS.dbo.DU000030 a
JOIN
DYNAMICS.dbo.DU000010 b
ON a.fileNumber = b.fileNumber
AND a.PRODID = b.PRODID
JOIN
DYNAMICS.dbo.SY01500 c
ON a.companyID = c.CMPANYID
WHERE (a.Status <> 0 or a.errornum <> 0) and a.Status <>15

I get this:

[Microsoft][SQL Server Native Client 11.0][SQL Server]Invalid object name 'P310PO30'.

Has anyone seen this before?

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (1)

GMA 1,074 on at

Like (0)

Report

That doesn't look list a valid object in GP. "P310PO30" looks like a mangled version of POP30310 (receipt line history). You may want to review those tables individually to ensure there isn't corrupt data.

But no, I haven't seen that. I have performed a test upgrade (GP 2013SP2 to GP2016) without issues.

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (0)

Report

I would look in your company database for a table by this name. If it is there I would rename it to POP30310. I would also correct this in the DUOS tables. I would imagine that you do not process purchase orders. After the upgrade it would be a good idea to use the SQL maintenance utility to drop and create this table.

Was this reply helpful? Yes No
L Vail 65,271 on at

Like (0)

Report

Hi,

I also have gone from 2015R2 to 2016R2 without issue. The POP30310 table does get updated with 16R2. Look in your DU000010 table in the Dynamics (or whatever you've named it) database for both the 'POP30310' table and the 'P310PO30' table. You should not have a table named 'P310PO30'. I would be inclined to change the table name to 'POP30310' if one turns up and I didn't have a 'POP30310' entry. I'm certainly no SQL expert, but I do not know why the statement you posted would generate the error. You're not referencing that table in your query, so I'm not sure why it would care.

As Richard suggested, I would also look in my company database and see if I had either table.

Kind regards,

Leslie

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

I guess I should flesh this out a little more.

I was able to get the upgrade complete, but it took some work. SQL Replication was still enabled, so I had to remove that (looking in dexsql.log told me that) and after that, I just had to bring POP30310 in from a backup (I have no idea why it was removed)

After that, I was good to go.

Was this reply helpful? Yes No