Quantcast
Channel: Primavera Online Interaction » WARNING
Viewing all articles
Browse latest Browse all 61

prim28251:Warning: The table ‘QUERYLIB’ has been created but its maximum row size (12604) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.

$
0
0
Solution ID: prim28251
Warning: The table ‘QUERYLIB’ has been created but its maximum row size (12604) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a row in this table will fail if the resulting row length exceeds 8060 bytes.
Status: Reviewed
Version(s): 4.0, 4.1, 5.0, 6.0, 6.1, 6.2, 6.2.1, 7.0



Problem:


Warning: The table ‘QUERYLIB’ has been created but its maximum row size
(12604) exceeds the maximum number of bytes per row (8060). INSERT or UPDATE
of a row in this table will fail if the resulting row length exceeds 8060
bytes.





Server: Msg 208, Level 16, State 1, Procedure EXPPROJ, Line 2

Invalid object name ‘dbo.EXPPROJ’.

Server: Msg 208, Level 16, State 1, Procedure FINDATES, Line 2

Invalid object name ‘dbo.FINDATES’.

Server: Msg 208, Level 16, State 1, Procedure FORMCATG, Line 2

Invalid object name ‘dbo.FORMCATG’.

Server: Msg 208, Level 16, State 1, Procedure FORMPROJ, Line 2

Invalid object name ‘dbo.FORMPROJ’.

Server: Msg 208, Level 16, State 1, Procedure FORMTMPL, Line 2

Invalid object name ‘dbo.FORMTMPL’.

Server: Msg 208, Level 16, State 1, Procedure ITERATION, Line 2

Invalid object name ‘dbo.ITERATION’.

Server: Msg 208, Level 16, State 1, Procedure ITERDAYS, Line 2

Invalid object name ‘dbo.ITERDAYS’.

Server: Msg 208, Level 16, State 1, Procedure ITERGOAL, Line 2

Invalid object name ‘dbo.ITERGOAL’.

Server: Msg 208, Level 16, State 1, Procedure JOBRPT, Line 2

Invalid object name ‘dbo.JOBRPT’.

Server: Msg 208, Level 16, State 1, Procedure PROCGROUP, Line 2

Invalid object name ‘dbo.PROCGROUP’.

Server: Msg 208, Level 16, State 1, Procedure PROCITEM, Line 2

Invalid object name ‘dbo.PROCITEM’.

Server: Msg 208, Level 16, State 1, Procedure PROJWSRPT, Line 2

Invalid object name ‘dbo.PROJWSRPT’.

Server: Msg 208, Level 16, State 1, Procedure QUERYLIB, Line 2

Invalid object name ‘dbo.QUERYLIB’.

Server: Msg 208, Level 16, State 1, Procedure RELEASE, Line 2

Invalid object name ‘dbo.RELEASE’.

Server: Msg 208, Level 16, State 1, Procedure ROLERATE, Line 2

Invalid object name ‘dbo.ROLERATE’.

Server: Msg 208, Level 16, State 1, Procedure RSRCSEC, Line 2

Invalid object name ‘dbo.RSRCSEC’.

Server: Msg 208, Level 16, State 1, Procedure TASKFIN, Line 2

Invalid object name ‘dbo.TASKFIN’.

Server: Msg 208, Level 16, State 1, Procedure TRSRCFIN, Line 2

Invalid object name ‘dbo.TRSRCFIN’.

Server: Msg 208, Level 16, State 1, Procedure UDFCODE, Line 2

Invalid object name ‘dbo.UDFCODE’.

Server: Msg 208, Level 16, State 1, Procedure WBSRSRC, Line 2

Invalid object name ‘dbo.WBSRSRC’.

Server: Msg 208, Level 16, State 1, Procedure WBSRSRC_QTY, Line 2

Invalid object name ‘dbo.WBSRSRC_QTY’.

Cause: You will get this error message if you have run the ConfigAsst utility AND the upgrade scripts on the database.

In order to upgrade the database you either need to run the upgrade scripts OR the ConfigAsst utility, NOT both.

Fix: Restore the database to the previous version and run the ConfigAsst utility (recommended way to upgrade the database) OR the upgrade scripts

Viewing all articles
Browse latest Browse all 61

Trending Articles