Error 207: upgrade

Showing posts with label upgrade. Show all posts

Thursday, March 29, 2012

Error 946: Cannot open database upgrade the database to the latest

I am trying to move a database from SQL Server 70 @. 70 compatibility level to
SQL Server 2000 @. 70 compatibility level.
But when execute restore stmt (cmd), I keep getting the errors:
Server: Msg 9002, Level 17, State 6, Line 2
The log file for database 'my_db' is full. Back up the transaction log for
the database to free up some log space.
Server: Msg 3013, Level 16, State 1, Line 2
RESTORE DATABASE is terminating abnormally.
Converting database 'my_db' from version 515 to the current version 539.
Database 'my_db' running the upgrade step from version 515 to version 524.
Database 'my_db' running the upgrade step from version 524 to version 525.
Database 'my_db' running the upgrade step from version 525 to version 526.
Database 'my_db' running the upgrade step from version 526 to version 527.
Database 'my_db' running the upgrade step from version 527 to version 528.
Database 'my_db' running the upgrade step from version 528 to version 529.
Database 'my_db' running the upgrade step from version 529 to version 530.
Database 'my_db' running the upgrade step from version 530 to version 531.
Database 'my_db' running the upgrade step from version 531 to version 532.
Database 'my_db' running the upgrade step from version 532 to version 533.
Database 'my_db' running the upgrade step from version 533 to version 534.
Database 'my_db' running the upgrade step from version 534 to version 535.
Error 946: Cannot open database upgrade the database to the latest version
Any idea, how I can restore w/o errors?Hi,
Looks like you do not have enough room in your hard disk in which the LDF
file resides. Could you identify the drive with more space and use
RESTORE DATABASE command with MOVE options to restore the database. See
Restore with Move option in Books online.
Thanks
Hari
SQL Server MVP
"Pari" <Pari@.discussions.microsoft.com> wrote in message
news:C74D6B5B-436D-4288-ABF3-31C835CC236B@.microsoft.com...
>I am trying to move a database from SQL Server 70 @. 70 compatibility level
>to
> SQL Server 2000 @. 70 compatibility level.
> But when execute restore stmt (cmd), I keep getting the errors:
> Server: Msg 9002, Level 17, State 6, Line 2
> The log file for database 'my_db' is full. Back up the transaction log for
> the database to free up some log space.
> Server: Msg 3013, Level 16, State 1, Line 2
> RESTORE DATABASE is terminating abnormally.
> Converting database 'my_db' from version 515 to the current version 539.
> Database 'my_db' running the upgrade step from version 515 to version 524.
> Database 'my_db' running the upgrade step from version 524 to version 525.
> Database 'my_db' running the upgrade step from version 525 to version 526.
> Database 'my_db' running the upgrade step from version 526 to version 527.
> Database 'my_db' running the upgrade step from version 527 to version 528.
> Database 'my_db' running the upgrade step from version 528 to version 529.
> Database 'my_db' running the upgrade step from version 529 to version 530.
> Database 'my_db' running the upgrade step from version 530 to version 531.
> Database 'my_db' running the upgrade step from version 531 to version 532.
> Database 'my_db' running the upgrade step from version 532 to version 533.
> Database 'my_db' running the upgrade step from version 533 to version 534.
> Database 'my_db' running the upgrade step from version 534 to version 535.
> Error 946: Cannot open database upgrade the database to the latest version
>
> Any idea, how I can restore w/o errors?|||Hi
For an Upgrade, SQL Server needs space in the transaction log to work. You
don't have enough.
On the SQL Server 7.0, before you make the backup, dump the log, grow the
transaction log to at least 10% of the database size, then do the backup and
then the restore the SQL Server 2000.
Regards
Mike
"Pari" wrote:
> I am trying to move a database from SQL Server 70 @. 70 compatibility level to
> SQL Server 2000 @. 70 compatibility level.
> But when execute restore stmt (cmd), I keep getting the errors:
> Server: Msg 9002, Level 17, State 6, Line 2
> The log file for database 'my_db' is full. Back up the transaction log for
> the database to free up some log space.
> Server: Msg 3013, Level 16, State 1, Line 2
> RESTORE DATABASE is terminating abnormally.
> Converting database 'my_db' from version 515 to the current version 539.
> Database 'my_db' running the upgrade step from version 515 to version 524.
> Database 'my_db' running the upgrade step from version 524 to version 525.
> Database 'my_db' running the upgrade step from version 525 to version 526.
> Database 'my_db' running the upgrade step from version 526 to version 527.
> Database 'my_db' running the upgrade step from version 527 to version 528.
> Database 'my_db' running the upgrade step from version 528 to version 529.
> Database 'my_db' running the upgrade step from version 529 to version 530.
> Database 'my_db' running the upgrade step from version 530 to version 531.
> Database 'my_db' running the upgrade step from version 531 to version 532.
> Database 'my_db' running the upgrade step from version 532 to version 533.
> Database 'my_db' running the upgrade step from version 533 to version 534.
> Database 'my_db' running the upgrade step from version 534 to version 535.
> Error 946: Cannot open database upgrade the database to the latest version
>
> Any idea, how I can restore w/o errors?|||Hi, you are right my log file did not have enough space, however, do you know
what these messages mean?
> > Database 'my_db' running the upgrade step from version 524 to version 525.
> > Database 'my_db' running the upgrade step from version 525 to version 526.
> > Database 'my_db' running the upgrade step from version 526 to version 527.
> > Database 'my_db' running the upgrade step from version 527 to version 528.
> > Database 'my_db' running the upgrade step from version 528 to version 529.
Does it mean its upgrading the DB from 70 compatibility to 80'
Thanks
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> For an Upgrade, SQL Server needs space in the transaction log to work. You
> don't have enough.
> On the SQL Server 7.0, before you make the backup, dump the log, grow the
> transaction log to at least 10% of the database size, then do the backup and
> then the restore the SQL Server 2000.
> Regards
> Mike
> "Pari" wrote:
> > I am trying to move a database from SQL Server 70 @. 70 compatibility level to
> > SQL Server 2000 @. 70 compatibility level.
> >
> > But when execute restore stmt (cmd), I keep getting the errors:
> >
> > Server: Msg 9002, Level 17, State 6, Line 2
> > The log file for database 'my_db' is full. Back up the transaction log for
> > the database to free up some log space.
> > Server: Msg 3013, Level 16, State 1, Line 2
> > RESTORE DATABASE is terminating abnormally.
> > Converting database 'my_db' from version 515 to the current version 539.
> > Database 'my_db' running the upgrade step from version 515 to version 524.
> > Database 'my_db' running the upgrade step from version 524 to version 525.
> > Database 'my_db' running the upgrade step from version 525 to version 526.
> > Database 'my_db' running the upgrade step from version 526 to version 527.
> > Database 'my_db' running the upgrade step from version 527 to version 528.
> > Database 'my_db' running the upgrade step from version 528 to version 529.
> > Database 'my_db' running the upgrade step from version 529 to version 530.
> > Database 'my_db' running the upgrade step from version 530 to version 531.
> > Database 'my_db' running the upgrade step from version 531 to version 532.
> > Database 'my_db' running the upgrade step from version 532 to version 533.
> > Database 'my_db' running the upgrade step from version 533 to version 534.
> > Database 'my_db' running the upgrade step from version 534 to version 535.
> > Error 946: Cannot open database upgrade the database to the latest version
> >
> >
> > Any idea, how I can restore w/o errors?

Error 946: Cannot open database upgrade the database to the latest

Thursday, March 22, 2012

Error 8144 creating transactional publication

This one has me going for some time now:

I am trying to upgrade my SQL Server from a NT4+SQL7 to Win2K+SQL2000.

Here are the steps:

Install/Work order on "virgin" double Xeon server:
1) Win2K Server
2) SP3 for Win2K
3) SQL Server 7.0
4) SP3 for SQL Server 7.0
5) Restore full backup of master database.
6) Restore full backups of 10 databases (one named Q5)
7) Installed SQL Server 2000 Upgrade
8) SP3 for SQL Server 2000

At this point I tested my apps with the several databases and all looked good. But now I need to create a transactional publication on the Q5 database named Q5Pub.

First I go with the wizard but when he gets to the point where he is "Creating the Publication" he offers me the following:

SQL Server Enterprise Manager could not create publication 'Q5Pub' from database 'Q5'.
Error 8144: Procedure or function sp_MSadd_publication has too many arguments specified.

I then try using the Query Analyzer with the following statement:

exec sp_addpublication @.publication = N'Q5Pub', @.restricted = N'false', @.sync_method = N'native', @.repl_freq = N'continuous', @.description = N'Transactional publication of Q5 database from Publisher SQLSERVER.', @.status = N'active', @.allow_push = N'true', @.allow_pull = N'true', @.allow_anonymous = N'true', @.enabled_for_internet = N'false', @.independent_agent = N'true', @.immediate_sync = N'true', @.allow_sync_tran = N'false', @.autogen_sync_procs = N'false', @.retention = 72

This gives me:

Server: Msg 8144, Level 16, State 2, Procedure sp_MSadd_publication, Line 0
Procedure or function sp_MSadd_publication has too many arguments specified.
Job 'SQLSERVER-Q5-23' started successfully.

So I look at the sp_addpublication stored procedure in the master database where I find:

...
/*
** Add the publication to the distributor side
*/
SELECT @.distproc = RTRIM(@.distributor) + '.' + @.distribdb +
'.dbo.sp_MSadd_publication'
EXECUTE @.retcode = @.distproc
@.publisher = @.@.SERVERNAME,
@.publisher_db = @.dbname,
@.publication = @.publication,
@.publication_type = @.rfid,
@.independent_agent = @.independent_agent_id,
@.immediate_sync = @.immediate_sync_id,
@.allow_push = @.allow_push_id,
@.allow_pull = @.allow_pull_id,
@.allow_anonymous = @.allow_anonymous_id,
@.snapshot_agent = @.null,
@.logreader_agent = @.agentname,
@.description = @.description,
@.retention = @.retention,
@.sync_method = @.smid,
@.allow_subscription_copy = @.allow_subscription_copy_id,
@.allow_queued_tran = @.allow_queued_tran_id,
@.queue_type = @.queue_type_val
...

But looking at the sp_MSadd_publication stored procedure in the distribution database I see:

CREATE PROCEDURE sp_MSadd_publication
@.publisher sysname,
@.publisher_db sysname,
@.publication sysname,
@.publication_id int = 0, -- BUG REMOVE
@.publication_type int = 1, -- 0 = Transactional 1 = Snapshot 2 = Merge
@.independent_agent bit = 0,
@.immediate_sync bit = 0,
@.allow_push bit = 1,
@.allow_pull bit = 0,
@.allow_anonymous bit = 0,
@.snapshot_agent nvarchar(100) = NULL,
@.logreader_agent nvarchar (100) = NULL,
@.description nvarchar(255) = NULL,
@.retention int =60,
@.vendor_name nvarchar(100) = 'Microsoft SQL Server'
as
...

So indeed the sp_addpublication calls the sp_MSadd_publication with too many arguments.
@.sync_method, @.allow_subscription_copy, @.allow_queued_tran and @.queue_type

What am I doing wrong?

Many thanks for any suggestion or/and help on this matter.Refer to this KBA (http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q328908).sql

Friday, February 24, 2012

Error 28092 when upgrading from Express to Workgroup Edition

Hello,

when I try to upgrade SQL Server 2005 using this command line:

setup.exe /qb SKUUPGRADE=1 UPGRADE=SQL_Engine INSTANCENAME=Z1 SQLACCOUNT=NT-AUTORIT?T\SYSTEM SECURITYMODE=SQL SAPWD=XXXXXX

I get error 28092 (administrator rights needed).

It seems like the upgrade tries to use Windows authentification although I've told it to use SQL Server authentification. Or did I miss a parameter in my command line?

If I do the upgrade manually it works without needing Windows authentification.

can you goto %program files%\microsoft sql server\90\setup bootstrap\log folder, and search for the error code, and share out the log content near/around the error?|||

The file SQLSetup0008_Z1TESTVISTA_SQL.log contains:

Attempt to start service when it is already running
SQL service MSSQL$Z1 started successfully waiting for SQL service to accept client connections
Loaded DLL:
C:\Windows\system32\Odbc32.dll
Version:
6.0.6000.16386

SQL_SUCCESS_WITH_INFO (1) in OdbcConnection::connect
sqlstate=01000, level=-1, state=-1, native_error=5701, msg=[Microsoft][SQL Native Client][SQL Server]Der Datenbankkontext wurde auf 'master' ge?ndert.
sqlstate=01000, level=-1, state=-1, native_error=5703, msg=[Microsoft][SQL Native Client][SQL Server]Die Spracheneinstellung wurde auf Deutsch ge?ndert.

Error Code: 0x80076dbc (28092)
Windows Error Text: Source File Name: sqlca\upgradesql.cpp
Compiler Timestamp: Thu Aug 11 01:12:02 2005
Function Name: sqls::UpgradeSql::validateDatabases
Source Line Number: 187

- Context --

Setting status of unmanaged components and removing unmanaged resources

Error Code: 28092
MSI (s) (38!74) [17:34:44:691]: Produkt: Microsoft SQL Server 2005 -- Fehler 28092. Das SQL Server-Setup ben?tigt Administratorberechtigungen für die aktualisierte SQL Server-Instanz. Melden Sie sich mit einem Administratorkonto an, um den Vorgang fortzusetzen.

Fehler 28092. Das SQL Server-Setup ben?tigt Administratorberechtigungen für die aktualisierte SQL Server-Instanz. Melden Sie sich mit einem Administratorkonto an, um den Vorgang fortzusetzen.
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='203'>
Doing Action: ValidateUpgrade
PerfTime Start: ValidateUpgrade : Thu Feb 01 17:34:44 2007
<Func Name='ValidateUpgrade'>
<Func Name='updateFeatureSellection'>
Attempt to start service when it is already running
SQL service MSSQL$Z1 started successfully waiting for SQL service to accept client connections
Loaded DLL:
C:\Windows\system32\Odbc32.dll
Version:
6.0.6000.16386

- Context --

Setting status of unmanaged components and removing unmanaged resources

Error Code: 28092
MSI (s) (38:FC) [17:34:46:848]: I/O on thread 2504 could not be cancelled. Error: 1168
MSI (s) (38:FC) [17:34:46:848]: I/O on thread 3304 could not be cancelled. Error: 1168
MSI (s) (38:FC) [17:34:46:848]: I/O on thread 2040 could not be cancelled. Error: 1168
MSI (s) (38:FC) [17:34:46:848]: I/O on thread 3548 could not be cancelled. Error: 1168
MSI (s) (38:FC) [17:34:46:848]: I/O on thread 3172 could not be cancelled. Error: 1168
MSI (s) (38:FC) [17:34:46:848]: I/O on thread 3996 could not be cancelled. Error: 1168
MSI (s) (38:FC) [17:34:46:848]: I/O on thread 3664 could not be cancelled. Error: 1168
MSI (s) (38:FC) [17:34:46:848]: I/O on thread 1456 could not be cancelled. Error: 1168
MSI (s) (38:FC) [17:34:46:848]: I/O on thread 3848 could not be cancelled. Error: 1168
MSI (s) (38!74) [17:34:46:863]: Produkt: Microsoft SQL Server 2005 -- Fehler 28092. Das SQL Server-Setup ben?tigt Administratorberechtigungen für die aktualisierte SQL Server-Instanz. Melden Sie sich mit einem Administratorkonto an, um den Vorgang fortzusetzen.

And the file SQLSetup0008_Z1TESTVISTA_Core(Patched).log:

Installing: sql on target: Z1TESTVISTA
Failed to install package
Schwerwiegender Fehler bei der Installation.
Setting package return code to: 28092
Complete: InstallSqlAction at: 2007/1/1 17:34:48, returned false
Error: Action "InstallSqlAction" failed during execution. Error information reported during run:
Target collection includes the local machine.
Invoking installPackage() on local machine.

|||

two questions:

1) were you running a admin on the box?

2) your express was ENU (English) or not? What language SKU it is? The same quesstion for the WorkGroup Edition?

|||

1) Yes, but on Vista with UAC enabled. Vista asks for admin evelation and I allow it.

May this be the problem? Shall I try under Windows XP?

2) Both are the German versions.

Maybe this is a similar problem like in

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1084672&SiteID=1

|||

This error means that the user who is running the setup is not sysadmin in the SQL instance. It makes sense this happens on Vista because of AUC the user is not recognize as NT administrator. You need to add yourself as sysadmin to SQL. From elevated application connect to SLQ and run:

EXEC sys.sp_grantlogin N'YourAccount'

EXEC sys.sp_addsrvrolemember N'[YourAccount]', N'sysadmin'

|||

Sorry, but this doesn't answer my question:

Why does this error not occur if I do the upgrade manually?

And how do I have to change my command line above to get the same result?

|||

So; after trying the same under Windows XP and experiencing the same problems again, I compared the log files created by the working manual upgrade with the ones from the aborting automatic upgrade.

I discovered some undocumented property names, especially "UPGRADEUSER" and "UPGRADEPWD". After changing my command line to

setup.exe /qb SKUUPGRADE=1 UPGRADE=SQL_Engine INSTANCENAME=Z1 SECURITYMODE=SQL UPGRADEUSER=sa UPGRADEPWD=XXXXXX

the automatic upgrade works now (with one exception).

THANK YOU VERY MUCH MICROSOFT FOR YOUR INCOMPLETE DOCUMENTATIONS!!!

The remaining problem now is, that the upgrade deletes Tools_Legacy even if I add

ADDLOCAL=Tools_Legacy

to the command line above. Any idea?

|||

I've found the solution for the last problem. So my (hopefully) final command line is:

setup.exe /qb SKUUPGRADE=1 UPGRADE=SQL_Engine ADDLOCAL=SQL_BC_DEP INSTANCENAME=Z1 SECURITYMODE=SQL UPGRADEUSER=sa UPGRADEPWD=XXXXXX

ERROR 26 AFTER UPGRADE OF SQL 2005 SERVER EXPRESS

I cannot make connection to database that I was using prior to the upgrade of SP1. Keep getting error 26-default settings prohibit remote access - but it's not remote.? Can anyone help - tell me how to change defaults or change properties to connect to my data after the update?

I am using Visual Web Developer Express. It can see the instance but cannot connect.

Using TCP/IP rather than named pipes is always "remote". YOu can enable the remote connections on the Computer by using the SQL Server Configuration surface. See more details and a screencast at my site in the section Screencasts >Enabling remote connections

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||Thank you - this did it.

Friday, February 17, 2012

error 21770 on SQL2k upgrade

We just upgraded our SQL 7 to SQL 2000 SP3a and we have the following
happening
1. running about 10000-50000 queries through ODBC blows the machine up
completely. Have to power off and on to get it back. This same code
ran fine on SQL 7 before the upgrade. It doesn't blow up at the same
number of queries or on the same data and varies widely on when it
blows up in this process.
2. when we go to properties on any of the databases we get an error
21770.
Specifically,
Error 21770 [SQL-DMO] The name 'null' was not found in the
specified collection.
Then when you hit OK on the subsequent properties screen, we get an
error 21266.
We have seen error 15457 in the logs at times as well.
DBCC checkdb on each database returns no errors. I am sure the 2
issues are related but I can find no solution to the problem(s)
anywhere.
Any help or ideas appreciated.Hi,
Prob 1:
the only prob i could think of is logging and the servers 'trunc. log. on
chkpt.' might be off or your recovery model is full and logs are not cleaned
up regularly.
cause generally people miss out the option as it appears in database
properties in sql 7 but in 2000 we have to explicitly set it to true by
sp_dboption
Prob 2:
have u checked for the object names im sure none has the name 'null'
is the database configured for replication cause the error 21266 is caused
in replication when it cannot publish the tables.
about 15457 error appears due to any configuration changes made in - Run the
RECONFIGURE
Regards,
MD
--
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.
--
"Russ Cobbe" <russc@.inline.net> wrote in message
news:80e8c028.0402111950.4e4eebf9@.posting.google.com...
> We just upgraded our SQL 7 to SQL 2000 SP3a and we have the following
> happening
> 1. running about 10000-50000 queries through ODBC blows the machine up
> completely. Have to power off and on to get it back. This same code
> ran fine on SQL 7 before the upgrade. It doesn't blow up at the same
> number of queries or on the same data and varies widely on when it
> blows up in this process.
> 2. when we go to properties on any of the databases we get an error
> 21770.
> Specifically,
> Error 21770 [SQL-DMO] The name 'null' was not found in the
> specified collection.
> Then when you hit OK on the subsequent properties screen, we get an
> error 21266.
> We have seen error 15457 in the logs at times as well.
> DBCC checkdb on each database returns no errors. I am sure the 2
> issues are related but I can find no solution to the problem(s)
> anywhere.
> Any help or ideas appreciated.

error 21770 on SQL2k upgrade

Error -2147467259 upgrading SQL 6.5 to SQL 2000

I'm trying to upgrade several databases from SQL 6.5 SP5a to SQL 2000
and I receive the following error from the Upgrade Wizard:
Export Exit Code: -2147467259 -
c:\progra~1\micros~3\mssql\upgrade\export.exe -CodePage 1252
-DeviceType Pipe -AllTables yes -MasterPath C:\MSSQL\DATA\MASTER.DAT
-DatabaseName AAP -DevicePath \\.\pipe\~cnvpipe0
****
Time:09-02-2004 17:55:13.272
Error in file CnvBuf.cpp Line=1555 rc=109 Msg=Result Code = 0x0000006d
****Time : 09-02-2004 17:55:13
An Error occured while exporting table ACCOUNT
Time : 09-02-2004 17:55:13
An Error occured while exporting database AAP
Time : 09-02-2004 17:55:13
An error occured while importing table. Please check the error file.
Time : 09-02-2004 17:55:14
pSql65Server->DumpAllTables () failed. hr=-2147467259
Both SQL Server versions are on the same computer and I log on as a
domain administrator. Also, both SQL services start as Administrator.
DBCC CHECKTABLE on table ACCOUNT doesn't return any errors.
Any suggestions?
Thanks everyone.
Don't knkow how the upgrade wizard works but it looks like it is bcping the
data out and getting an error. Maybe running out of space?
"Leandro Ordo?ez" wrote:

> I'm trying to upgrade several databases from SQL 6.5 SP5a to SQL 2000
> and I receive the following error from the Upgrade Wizard:
> Export Exit Code: -2147467259 -
> c:\progra~1\micros~3\mssql\upgrade\export.exe -CodePage 1252
> -DeviceType Pipe -AllTables yes -MasterPath C:\MSSQL\DATA\MASTER.DAT
> -DatabaseName AAP -DevicePath \\.\pipe\~cnvpipe0
> ****
> Time:09-02-2004 17:55:13.272
> Error in file CnvBuf.cpp Line=1555 rc=109 Msg=Result Code = 0x0000006d
> ****Time : 09-02-2004 17:55:13
> An Error occured while exporting table ACCOUNT
> Time : 09-02-2004 17:55:13
> An Error occured while exporting database AAP
> Time : 09-02-2004 17:55:13
> An error occured while importing table. Please check the error file.
> Time : 09-02-2004 17:55:14
> pSql65Server->DumpAllTables () failed. hr=-2147467259
> Both SQL Server versions are on the same computer and I log on as a
> domain administrator. Also, both SQL services start as Administrator.
> DBCC CHECKTABLE on table ACCOUNT doesn't return any errors.
> Any suggestions?
> Thanks everyone.
>

Error -2147467259 upgrading SQL 6.5 to SQL 2000

I'm trying to upgrade several databases from SQL 6.5 SP5a to SQL 2000
and I receive the following error from the Upgrade Wizard:
Export Exit Code: -2147467259 -
c:\progra~1\micros~3\mssql\upgrade\export.exe -CodePage 1252
-DeviceType Pipe -AllTables yes -MasterPath C:\MSSQL\DATA\MASTER.DAT
-DatabaseName AAP -DevicePath \\.\pipe\~cnvpipe0
****
Time:09-02-2004 17:55:13.272
Error in file CnvBuf.cpp Line=1555 rc=109 Msg=Result Code = 0x0000006d
****Time : 09-02-2004 17:55:13
An Error occured while exporting table ACCOUNT
Time : 09-02-2004 17:55:13
An Error occured while exporting database AAP
Time : 09-02-2004 17:55:13
An error occured while importing table. Please check the error file.
Time : 09-02-2004 17:55:14
pSql65Server->DumpAllTables () failed. hr=-2147467259
Both SQL Server versions are on the same computer and I log on as a
domain administrator. Also, both SQL services start as Administrator.
DBCC CHECKTABLE on table ACCOUNT doesn't return any errors.
Any suggestions?
Thanks everyone.Don't knkow how the upgrade wizard works but it looks like it is bcping the
data out and getting an error. Maybe running out of space?
"Leandro Ordo?ez" wrote:
> I'm trying to upgrade several databases from SQL 6.5 SP5a to SQL 2000
> and I receive the following error from the Upgrade Wizard:
> Export Exit Code: -2147467259 -
> c:\progra~1\micros~3\mssql\upgrade\export.exe -CodePage 1252
> -DeviceType Pipe -AllTables yes -MasterPath C:\MSSQL\DATA\MASTER.DAT
> -DatabaseName AAP -DevicePath \\.\pipe\~cnvpipe0
> ****
> Time:09-02-2004 17:55:13.272
> Error in file CnvBuf.cpp Line=1555 rc=109 Msg=Result Code = 0x0000006d
> ****Time : 09-02-2004 17:55:13
> An Error occured while exporting table ACCOUNT
> Time : 09-02-2004 17:55:13
> An Error occured while exporting database AAP
> Time : 09-02-2004 17:55:13
> An error occured while importing table. Please check the error file.
> Time : 09-02-2004 17:55:14
> pSql65Server->DumpAllTables () failed. hr=-2147467259
> Both SQL Server versions are on the same computer and I log on as a
> domain administrator. Also, both SQL services start as Administrator.
> DBCC CHECKTABLE on table ACCOUNT doesn't return any errors.
> Any suggestions?
> Thanks everyone.
>

Thursday, March 29, 2012

Error 946: Cannot open database upgrade the database to the latest

Error 946: Cannot open database upgrade the database to the latest

Error 946: Cannot open database upgrade the database to the latest

Thursday, March 22, 2012

Error 8144 creating transactional publication

Friday, February 24, 2012

Error 28092 when upgrading from Express to Workgroup Edition

ERROR 26 AFTER UPGRADE OF SQL 2005 SERVER EXPRESS

Friday, February 17, 2012

error 21770 on SQL2k upgrade

error 21770 on SQL2k upgrade

Error -2147467259 upgrading SQL 6.5 to SQL 2000

Error -2147467259 upgrading SQL 6.5 to SQL 2000

Error 207

Blog Archive

About Me