
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-23-2011 12:27 AM
I was running latest, last version. Did not try the beta of 4.1.0.14. Database schema as 10. As I have a customized setup (non-default database name), I've been able to just run the sql scripts manually. Problem this time. I get the errors below running upgradescript11.sql:
(0 row(s) affected)
Msg 1779, Level 16, State 0, Line 1
Table 'tsysreports' already has a primary key defined on it.
Msg 1750, Level 16, State 0, Line 1
Could not create constraint. See previous errors.
(0 row(s) affected)
Msg 1779, Level 16, State 0, Line 1
Table 'tsysdonotscan' already has a primary key defined on it.
Msg 1750, Level 16, State 0, Line 1
Could not create constraint. See previous errors.
(0 row(s) affected)
Msg 1779, Level 16, State 0, Line 1
Table 'tsysserials' already has a primary key defined on it.
Msg 1750, Level 16, State 0, Line 1
Could not create constraint. See previous errors.
(1 row(s) affected)
The constraints are not getting created.
Thanks,
Joe
(0 row(s) affected)
Msg 1779, Level 16, State 0, Line 1
Table 'tsysreports' already has a primary key defined on it.
Msg 1750, Level 16, State 0, Line 1
Could not create constraint. See previous errors.
(0 row(s) affected)
Msg 1779, Level 16, State 0, Line 1
Table 'tsysdonotscan' already has a primary key defined on it.
Msg 1750, Level 16, State 0, Line 1
Could not create constraint. See previous errors.
(0 row(s) affected)
Msg 1779, Level 16, State 0, Line 1
Table 'tsysserials' already has a primary key defined on it.
Msg 1750, Level 16, State 0, Line 1
Could not create constraint. See previous errors.
(1 row(s) affected)
The constraints are not getting created.
Thanks,
Joe
Labels:
- Labels:
-
Archive
3 REPLIES 3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-23-2011 03:54 PM
Thank you.
Updatescript12 ran fine. All is working great.
Updatescript12 ran fine. All is working great.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-23-2011 12:45 AM
I'm thinking that with the PKs already there, that these 3 errors are because what was being updated/added by upgradescript11 already exists. (The altered view and schema version update ran fine.)

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-23-2011 09:37 AM
joegasper wrote:
I'm thinking that with the PKs already there, that these 3 errors are because what was being updated/added by upgradescript11 already exists. (The altered view and schema version update ran fine.)
This is normal behaviour and can be ignored.
