You’re offline. This is a read only version of the page.
1,348
Hi
I am presently doing a test upgrade of a Dynamics 7.0SP4 database to Dynamics 2015 and after the upgrade I noticed a couple of errors in the DBuild log file. I researched online and I got an article that points to changing the connection on the server to 0 so that it could fix the timeout expired message but I still encountered the message after doing another test upgrade.
In addition, one of the error message in the log file, it pointed to an invalid column. On checking, I realized that the PONbr field is not present in the INTran table in Dynamics 7.0 but it is present in Dynamics 2015. Has anyone noticed this issue on upgrading?
I have pasted some of the errors that I go from the DBuild log file. Could someone assist in pointing to what I could do to resolve these issues. Any assistance will be greatly appreciated.
Error Code: -2
Error Text: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Statement: SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULL_DFLT_OFF ON
GO
IF NOT EXISTS(SELECT sysobjects.name, syscolumns.id, syscolumns.name
FROM sysobjects JOIN syscolumns ON(sysobjects.id = syscolumns.id)
WHERE sysobjects.name = 'INTran'
AND syscolumns.name = 'PoNbr')
Error Code: -2
Error Text: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Statement: SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULL_DFLT_OFF ON
GO
-- This will clean up orphan note entries for tables with a NOTEID column that is NOT an Identity column
declare @sql nvarchar(max) = ''
select @sql = @sql + 'UPDATE ' + t.name + ' set noteid = 0 where noteid <> 0 and NOT EXISTS(select nid from snote where nid = noteid );'
from sys.tables t WHERE EXISTS(SELECT c.name FROM sys.columns c WHERE c.object_id = t.object_id AND c.name = 'NoteId' and c.is_identity = 0 )
exec sp_executesql @sql
Error Code: 207
Error Text: Invalid column name 'PoNbr'.
Invalid column name 'SrcDate'.
Invalid column name 'SrcLineRef'.
Invalid column name 'SrcNbr'.
Invalid column name 'SrcType'.
Statement: SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULL_DFLT_OFF ON
GO
CREATE VIEW [QQ_intran]
AS
/*
Negative Check
If the Inventory Setup settings does not allow negative quantities, check to keep
the costing layer from having either a negative quantity or a negative cost.
*/
If (@NegQty = @False
Or (Select RTrim(LotSerTrack) From Inventory Where InvtID = @InvtID) = 'SI')
And (@IS_QtyOnHand + Round(CONVERT(DEC(25,9),@QtyOnHand), @DecPlQty) < 0
Or (@IS_TotCost + Round(CONVERT(DEC(28,3),@TotCost), @BaseDecPl) < 0 And @IS_QtyOnHand + Round(CONVERT(DEC(25,9),@QtyOnHand), @DecPlQty) > 0
And @ValMthd <> 'U'))
Begin
/*
Solomon Error Message
*/
Insert Into IN10400_RETURN
*This post is locked for comments
Hi Lisa,
Corrections would have been made to the source database. Since you were able to complete a 2nd run of the database upgrade and can log in, running reports to validate the upgraded items should be all that is expected for post-upgrade testing.
Hi Brian
Did you make the corrections in Dynamics 7.0 or in 2015?
After I upgraded with a couple of errors, I re-run the upgrade again and the process ending without giving any indication of errors. Not sure if it corrected itself.
Regards
Hi Jeremy
Yes I am able to log on to 2015CU1 without any errors.
I am presently doing a comparison with the transaction reports and so far the balances in Dynamics 2015 are the same as Dynamics 7.0.
Should I be worried about the errors I got in the DBuild log?
Regards
Are you able to login to SL even though you received those errors?
If not, what errors do you get when trying to login?
I did encounter a problem in one migration with the note fields. In that one instance I found the notes involved were a few obsolete entries from history, and the customer had no need for the notes. I removed the related notes from the SNOTE table and reran the migration without error.
I don't recall any problem with the PONbr field, but I recall a problem once where a record contained a reserved character in a text field, and the syntax used by the upgrade program (like the select @sql = @sql + line that is building a SQL statement) tried to use the reserved character in building the SQL statement. Locating and removing or replacing the character from the text field would resolve this type of problem.
Share
Report
All responses (
Answers (
