Using the Import/Export Data Wizard, I'm trying to export a FoxPro 2.5 DOS (as dBase III) table of 15,000 records to SQL Server 2000. I keep getting this error message:
Insert Error, Column 32 ('PROG_START',DBTYPE_DBTIMESTAMP), Status 6: Data Overflow.
Invalid character value for cast specification.
I have SQL Server create the table each time I run the wizard. The new table allows NULLS in this column and I made sure to overwrite the empty date fields in the FoxPro table with blanks to make sure it would result in NULL. Originally SQL Server tried to put this as SMALL DATETIME, but when I got the message earlier, I changed it to DATETIME.
Any suggestions?hi
1) can you run a select in the fox tables, for example:
select min(col), max(col) from myTable
2) do you use any function to transform the fox date to sql date?
TIA
Abel.|||My first guess would be that you've got some data for 02/29/00, which Fox mis-interprets at 1900-02-29 (which it shouldn't accept, but it did).
If that isn't correct, the only thing I could offer would be that if you'll post the DBF (and any associated NDX, NTX, or CDX) files, I'd be willing to take a shot at converting them tonight.
-patP|||The problem is that it isn't always the same record that I'm getting the error. I'm getting this error with different tables I'm trying to convert and they all have numerous records with blank Date fields that are causing the problem.
Pat, thank you for your offer. I can try to come up with a sample data set to send to you or give you one of the smaller tables that give this error. Which would you prefer.
Showing posts with label wizard. Show all posts
Showing posts with label wizard. Show all posts
Thursday, March 29, 2012
Monday, March 26, 2012
Error during Copy Database Wizard operation
Do anyone know why i got "Failed to create the share OMWWIZD" error message when trying to copy databases from SQL Server 7.0 to SQL Server 2000?
Thanks!Probably something to do with security permissions between the two servers. If so, pick an administrative account which is the same on both. Run the wizard as that account. Test access by logging into one server and map a drive to the other.
--jfp|||Thanks for the suggestion! I tried using a domain admin to copy the database over and it works! I was using a local admin account before to establish the connection.
Thanks again.
--Speedster.|||hi
I have the same problem but i'm in workstation ...
i used Administrator account in the source server and the destination server, but it doesn't work :eek:
What can i do ?|||- quoting "hi I have the same problem but i'm in workstation ...
i used Administrator account in the source server and the destination server, but it doesn't work What can i do ?"
asanhaji, are you accessing it from a windows workstation via Enterprise Manger? Is it possible to be at one of the servers locally and try to copy it over? Unless you are a logged into the workstation with a domain admin account OR connect to the server in Enterprise manager with a domain admin account you may not have any luck in copying the stuff over. You may need to connect to both servers using a DBO account (typically sa is the user name for it).
slashman
Thanks!Probably something to do with security permissions between the two servers. If so, pick an administrative account which is the same on both. Run the wizard as that account. Test access by logging into one server and map a drive to the other.
--jfp|||Thanks for the suggestion! I tried using a domain admin to copy the database over and it works! I was using a local admin account before to establish the connection.
Thanks again.
--Speedster.|||hi
I have the same problem but i'm in workstation ...
i used Administrator account in the source server and the destination server, but it doesn't work :eek:
What can i do ?|||- quoting "hi I have the same problem but i'm in workstation ...
i used Administrator account in the source server and the destination server, but it doesn't work What can i do ?"
asanhaji, are you accessing it from a windows workstation via Enterprise Manger? Is it possible to be at one of the servers locally and try to copy it over? Unless you are a logged into the workstation with a domain admin account OR connect to the server in Enterprise manager with a domain admin account you may not have any luck in copying the stuff over. You may need to connect to both servers using a DBO account (typically sa is the user name for it).
slashman
Error during configuring distribution wizard
TITLE: Configure Distribution Wizard
An error occurred configuring SQL Server Agent.
ADDITIONAL INFORMATION:
SQL Server blocked access to procedure 'dbo.sp_set_sqlagent_properties' of component 'Agent XPs' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Agent XPs' by using sp_configure. For more information about enabling 'Agent XPs', see "Surface Area Configuration" in SQL Server Books Online. (Microsoft SQL Server, Error: 15281)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=15281&LinkId=20476
How do I solve this?
Thanks,
Frank
System Engineer
I think the solution is pretty clear inside the error message. Did you have problems following the instructions?|||The worst part, as with many of the error messages, the link in the error takes you to a "sorry no information is available about this problem". Don't know what broke in that process, but I have seen that exact page come up several times while checking alerts in MOM. I hope it is something that will be fixed soon because it seems pretty sad that a link in internal help provides "No Help".
Allen
|||Please execute
The following shows the available options
USE master;
GO
EXEC sp_configure 'show advanced option', '1';
RECONFIGURE;
EXEC sp_configure;
The following enables the Agent XPs
EXEC sp_configure 'Agent XPs', '1';
|||Hi,
Has anybody get the solution as I am getting the same error while installing sqlserver 2005 express on my window xp.
pls see below
TITLE: Microsoft SQL Server 2005 Setup
SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Cannot add functional unit 'sp_sqlagent_get_startup_info' to component 'Agent XPs'. This unit has been already registered with the component.. Refer to the server error logs and Setup logs for detailed error information.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=setup.rll&EvtID=29521&EvtType=lib%5codbc_statement.h%40Do_sqlScript%40OdbcStatement%3a%3aexecute_batch%40sysdbupg.sql%40107%40x3bff
BUTTONS:
&Retry
Cancel
Thanks
|||SQL Server 2005 Express does not have a SQL Server agent. Nor can it be configured as a distributor.
Exactly how are you attempting to configure it as a distributor?
From http://msdn2.microsoft.com/en-us/library/ms151819.aspx
SQL Server Express cannot serve as a Publisher or Distributor. However, merge replication allows changes to be replicated in both directions between a Publisher and Subscriber.
|||try this :
Change the system date to cureent day
Error during configuring distribution wizard
TITLE: Configure Distribution Wizard
An error occurred configuring SQL Server Agent.
ADDITIONAL INFORMATION:
SQL Server blocked access to procedure 'dbo.sp_set_sqlagent_properties' of component 'Agent XPs' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Agent XPs' by using sp_configure. For more information about enabling 'Agent XPs', see "Surface Area Configuration" in SQL Server Books Online. (Microsoft SQL Server, Error: 15281)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=15281&LinkId=20476
How do I solve this?
Thanks,
Frank
System Engineer
I think the solution is pretty clear inside the error message. Did you have problems following the instructions?|||The worst part, as with many of the error messages, the link in the error takes you to a "sorry no information is available about this problem". Don't know what broke in that process, but I have seen that exact page come up several times while checking alerts in MOM. I hope it is something that will be fixed soon because it seems pretty sad that a link in internal help provides "No Help".
Allen
|||Please execute
The following shows the available options
USE master;
GO
EXEC sp_configure 'show advanced option', '1';
RECONFIGURE;
EXEC sp_configure;
The following enables the Agent XPs
EXEC sp_configure 'Agent XPs', '1';
|||
Hi,
Has anybody get the solution as I am getting the same error while installing sqlserver 2005 express on my window xp.
pls see below
TITLE: Microsoft SQL Server 2005 Setup
SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Cannot add functional unit 'sp_sqlagent_get_startup_info' to component 'Agent XPs'. This unit has been already registered with the component.. Refer to the server error logs and Setup logs for detailed error information.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=setup.rll&EvtID=29521&EvtType=lib%5codbc_statement.h%40Do_sqlScript%40OdbcStatement%3a%3aexecute_batch%40sysdbupg.sql%40107%40x3bff
BUTTONS:
&Retry
Cancel
Thanks
|||SQL Server 2005 Express does not have a SQL Server agent. Nor can it be configured as a distributor.
Exactly how are you attempting to configure it as a distributor?
From http://msdn2.microsoft.com/en-us/library/ms151819.aspx
SQL Server Express cannot serve as a Publisher or Distributor. However, merge replication allows changes to be replicated in both directions between a Publisher and Subscriber. |||try this :
Change the system date to cureent day
sqlError during configuring distribution wizard
TITLE: Configure Distribution Wizard
An error occurred configuring SQL Server Agent.
ADDITIONAL INFORMATION:
SQL Server blocked access to procedure 'dbo.sp_set_sqlagent_properties' of component 'Agent XPs' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Agent XPs' by using sp_configure. For more information about enabling 'Agent XPs', see "Surface Area Configuration" in SQL Server Books Online. (Microsoft SQL Server, Error: 15281)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=15281&LinkId=20476
How do I solve this?
Thanks,
Frank
System Engineer
I think the solution is pretty clear inside the error message. Did you have problems following the instructions?|||The worst part, as with many of the error messages, the link in the error takes you to a "sorry no information is available about this problem". Don't know what broke in that process, but I have seen that exact page come up several times while checking alerts in MOM. I hope it is something that will be fixed soon because it seems pretty sad that a link in internal help provides "No Help".
Allen
|||Please execute
The following shows the available options
USE master;
GO
EXEC sp_configure 'show advanced option', '1';
RECONFIGURE;
EXEC sp_configure;
The following enables the Agent XPs
EXEC sp_configure 'Agent XPs', '1';
|||Hi,
Has anybody get the solution as I am getting the same error while installing sqlserver 2005 express on my window xp.
pls see below
TITLE: Microsoft SQL Server 2005 Setup
SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Cannot add functional unit 'sp_sqlagent_get_startup_info' to component 'Agent XPs'. This unit has been already registered with the component.. Refer to the server error logs and Setup logs for detailed error information.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=setup.rll&EvtID=29521&EvtType=lib%5codbc_statement.h%40Do_sqlScript%40OdbcStatement%3a%3aexecute_batch%40sysdbupg.sql%40107%40x3bff
BUTTONS:
&Retry
Cancel
Thanks
|||SQL Server 2005 Express does not have a SQL Server agent. Nor can it be configured as a distributor.
Exactly how are you attempting to configure it as a distributor?
From http://msdn2.microsoft.com/en-us/library/ms151819.aspx
SQL Server Express cannot serve as a Publisher or Distributor. However, merge replication allows changes to be replicated in both directions between a Publisher and Subscriber.
|||try this :
Change the system date to cureent day
Error during configuring distribution wizard
TITLE: Configure Distribution Wizard
An error occurred configuring SQL Server Agent.
ADDITIONAL INFORMATION:
SQL Server blocked access to procedure 'dbo.sp_set_sqlagent_properties' of component 'Agent XPs' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Agent XPs' by using sp_configure. For more information about enabling 'Agent XPs', see "Surface Area Configuration" in SQL Server Books Online. (Microsoft SQL Server, Error: 15281)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=15281&LinkId=20476
How do I solve this?
Thanks,
Frank
System Engineer
I think the solution is pretty clear inside the error message. Did you have problems following the instructions?|||The worst part, as with many of the error messages, the link in the error takes you to a "sorry no information is available about this problem". Don't know what broke in that process, but I have seen that exact page come up several times while checking alerts in MOM. I hope it is something that will be fixed soon because it seems pretty sad that a link in internal help provides "No Help".
Allen
|||Please execute
The following shows the available options
USE master;
GO
EXEC sp_configure 'show advanced option', '1';
RECONFIGURE;
EXEC sp_configure;
The following enables the Agent XPs
EXEC sp_configure 'Agent XPs', '1';
|||
Hi,
Has anybody get the solution as I am getting the same error while installing sqlserver 2005 express on my window xp.
pls see below
TITLE: Microsoft SQL Server 2005 Setup
SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Cannot add functional unit 'sp_sqlagent_get_startup_info' to component 'Agent XPs'. This unit has been already registered with the component.. Refer to the server error logs and Setup logs for detailed error information.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=setup.rll&EvtID=29521&EvtType=lib%5codbc_statement.h%40Do_sqlScript%40OdbcStatement%3a%3aexecute_batch%40sysdbupg.sql%40107%40x3bff
BUTTONS:
&Retry
Cancel
Thanks
|||SQL Server 2005 Express does not have a SQL Server agent. Nor can it be configured as a distributor.
Exactly how are you attempting to configure it as a distributor?
From http://msdn2.microsoft.com/en-us/library/ms151819.aspx
SQL Server Express cannot serve as a Publisher or Distributor. However, merge replication allows changes to be replicated in both directions between a Publisher and Subscriber. |||try this :
Change the system date to cureent day
Monday, March 19, 2012
Error Copying from 2000 to 2005
Hello. I'm getting a frustrating error trying to copy a database from SQL
2000 to SQL 2005 using the copy wizard. The attempt fails with two errors in
the event log on the SQL 2005 server. I am running SQL 2005 64-bit Edition o
n
Windows Server 2003 64 on a Intel Xeon EMT. I continue to receive the error
even after an upgrade to SP1:
Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug?
0, fault address 0x0000000000027d0d.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
&&
Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug?
0, fault address 0x0000000000027d0d.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
From this link:
http://www.dbtalk.net/microsoft-pub...
-a-165165.html
It would seem that others are also having this issue - but nothing from
Microsoft on it. I'm not sure how to move forward. And yes, I do realize tha
t
Its probably simplier to offline the database and copy the files, but that i
s
not what I want to do. I want to use a feature of the product we purchased.
Has anyone run into and FIXED this issue before.
Thanks!
Errol NealHi
Try RESTORE command
"Errol Neal" <ErrolNeal@.discussions.microsoft.com> wrote in message
news:5F4BA321-C5BB-4427-A6C8-014E1F22995D@.microsoft.com...
> Hello. I'm getting a frustrating error trying to copy a database from SQL
> 2000 to SQL 2005 using the copy wizard. The attempt fails with two errors
> in
> the event log on the SQL 2005 server. I am running SQL 2005 64-bit Edition
> on
> Windows Server 2003 64 on a Intel Xeon EMT. I continue to receive the
> error
> even after an upgrade to SP1:
> Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
> faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79,
> debug?
> 0, fault address 0x0000000000027d0d.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> &&
> Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
> faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79,
> debug?
> 0, fault address 0x0000000000027d0d.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> From this link:
> http://www.dbtalk.net/microsoft-pub...0-a-165165.html
> It would seem that others are also having this issue - but nothing from
> Microsoft on it. I'm not sure how to move forward. And yes, I do realize
> that
> Its probably simplier to offline the database and copy the files, but that
> is
> not what I want to do. I want to use a feature of the product we
> purchased.
> Has anyone run into and FIXED this issue before.
> Thanks!
> Errol Neal|||Just an update, if someone is looking for solution:
Make sure SQLServer domain user you are running SQL SERVER on new
server has access to old SQL server. Usually you need to add SQL User
domain account to Local Administrator group on the old server.
2000 to SQL 2005 using the copy wizard. The attempt fails with two errors in
the event log on the SQL 2005 server. I am running SQL 2005 64-bit Edition o
n
Windows Server 2003 64 on a Intel Xeon EMT. I continue to receive the error
even after an upgrade to SP1:
Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug?
0, fault address 0x0000000000027d0d.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
&&
Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug?
0, fault address 0x0000000000027d0d.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
From this link:
http://www.dbtalk.net/microsoft-pub...
-a-165165.html
It would seem that others are also having this issue - but nothing from
Microsoft on it. I'm not sure how to move forward. And yes, I do realize tha
t
Its probably simplier to offline the database and copy the files, but that i
s
not what I want to do. I want to use a feature of the product we purchased.
Has anyone run into and FIXED this issue before.
Thanks!
Errol NealHi
Try RESTORE command
"Errol Neal" <ErrolNeal@.discussions.microsoft.com> wrote in message
news:5F4BA321-C5BB-4427-A6C8-014E1F22995D@.microsoft.com...
> Hello. I'm getting a frustrating error trying to copy a database from SQL
> 2000 to SQL 2005 using the copy wizard. The attempt fails with two errors
> in
> the event log on the SQL 2005 server. I am running SQL 2005 64-bit Edition
> on
> Windows Server 2003 64 on a Intel Xeon EMT. I continue to receive the
> error
> even after an upgrade to SP1:
> Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
> faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79,
> debug?
> 0, fault address 0x0000000000027d0d.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> &&
> Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
> faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79,
> debug?
> 0, fault address 0x0000000000027d0d.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> From this link:
> http://www.dbtalk.net/microsoft-pub...0-a-165165.html
> It would seem that others are also having this issue - but nothing from
> Microsoft on it. I'm not sure how to move forward. And yes, I do realize
> that
> Its probably simplier to offline the database and copy the files, but that
> is
> not what I want to do. I want to use a feature of the product we
> purchased.
> Has anyone run into and FIXED this issue before.
> Thanks!
> Errol Neal|||Just an update, if someone is looking for solution:
Make sure SQLServer domain user you are running SQL SERVER on new
server has access to old SQL server. Usually you need to add SQL User
domain account to Local Administrator group on the old server.
Error Copying from 2000 to 2005
Hello. I'm getting a frustrating error trying to copy a database from SQL
2000 to SQL 2005 using the copy wizard. The attempt fails with two errors in
the event log on the SQL 2005 server. I am running SQL 2005 64-bit Edition on
Windows Server 2003 64 on a Intel Xeon EMT. I continue to receive the error
even after an upgrade to SP1:
Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug?
0, fault address 0x0000000000027d0d.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
&&
Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug?
0, fault address 0x0000000000027d0d.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
From this link:
http://www.dbtalk.net/microsoft-public-sqlserver-dts/error-copying-sql-server-2000-a-165165.html
It would seem that others are also having this issue - but nothing from
Microsoft on it. I'm not sure how to move forward. And yes, I do realize that
Its probably simplier to offline the database and copy the files, but that is
not what I want to do. I want to use a feature of the product we purchased.
Has anyone run into and FIXED this issue before.
Thanks!
Errol NealHi
Try RESTORE command
"Errol Neal" <ErrolNeal@.discussions.microsoft.com> wrote in message
news:5F4BA321-C5BB-4427-A6C8-014E1F22995D@.microsoft.com...
> Hello. I'm getting a frustrating error trying to copy a database from SQL
> 2000 to SQL 2005 using the copy wizard. The attempt fails with two errors
> in
> the event log on the SQL 2005 server. I am running SQL 2005 64-bit Edition
> on
> Windows Server 2003 64 on a Intel Xeon EMT. I continue to receive the
> error
> even after an upgrade to SP1:
> Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
> faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79,
> debug?
> 0, fault address 0x0000000000027d0d.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> &&
> Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
> faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79,
> debug?
> 0, fault address 0x0000000000027d0d.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> From this link:
> http://www.dbtalk.net/microsoft-public-sqlserver-dts/error-copying-sql-server-2000-a-165165.html
> It would seem that others are also having this issue - but nothing from
> Microsoft on it. I'm not sure how to move forward. And yes, I do realize
> that
> Its probably simplier to offline the database and copy the files, but that
> is
> not what I want to do. I want to use a feature of the product we
> purchased.
> Has anyone run into and FIXED this issue before.
> Thanks!
> Errol Neal|||Just an update, if someone is looking for solution:
Make sure SQLServer domain user you are running SQL SERVER on new
server has access to old SQL server. Usually you need to add SQL User
domain account to Local Administrator group on the old server.
2000 to SQL 2005 using the copy wizard. The attempt fails with two errors in
the event log on the SQL 2005 server. I am running SQL 2005 64-bit Edition on
Windows Server 2003 64 on a Intel Xeon EMT. I continue to receive the error
even after an upgrade to SP1:
Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug?
0, fault address 0x0000000000027d0d.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
&&
Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79, debug?
0, fault address 0x0000000000027d0d.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
From this link:
http://www.dbtalk.net/microsoft-public-sqlserver-dts/error-copying-sql-server-2000-a-165165.html
It would seem that others are also having this issue - but nothing from
Microsoft on it. I'm not sure how to move forward. And yes, I do realize that
Its probably simplier to offline the database and copy the files, but that is
not what I want to do. I want to use a feature of the product we purchased.
Has anyone run into and FIXED this issue before.
Thanks!
Errol NealHi
Try RESTORE command
"Errol Neal" <ErrolNeal@.discussions.microsoft.com> wrote in message
news:5F4BA321-C5BB-4427-A6C8-014E1F22995D@.microsoft.com...
> Hello. I'm getting a frustrating error trying to copy a database from SQL
> 2000 to SQL 2005 using the copy wizard. The attempt fails with two errors
> in
> the event log on the SQL 2005 server. I am running SQL 2005 64-bit Edition
> on
> Windows Server 2003 64 on a Intel Xeon EMT. I continue to receive the
> error
> even after an upgrade to SP1:
> Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
> faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79,
> debug?
> 0, fault address 0x0000000000027d0d.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> &&
> Faulting application dtexec.exe, version 2005.90.1399.0, stamp 43500d1a,
> faulting module kernel32.dll, version 5.2.3790.1830, stamp 42438b79,
> debug?
> 0, fault address 0x0000000000027d0d.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> From this link:
> http://www.dbtalk.net/microsoft-public-sqlserver-dts/error-copying-sql-server-2000-a-165165.html
> It would seem that others are also having this issue - but nothing from
> Microsoft on it. I'm not sure how to move forward. And yes, I do realize
> that
> Its probably simplier to offline the database and copy the files, but that
> is
> not what I want to do. I want to use a feature of the product we
> purchased.
> Has anyone run into and FIXED this issue before.
> Thanks!
> Errol Neal|||Just an update, if someone is looking for solution:
Make sure SQLServer domain user you are running SQL SERVER on new
server has access to old SQL server. Usually you need to add SQL User
domain account to Local Administrator group on the old server.
Wednesday, March 7, 2012
Error connecting to OLEDB for DB2
I'm attempting to configure a new Microsoft OLE DB Provider for DB2 connection using the provided Data Access Tool and Wizard. I'm configured for DB2\MVS TCP/IP and have my Catalog and other defaults set. When I go to connect I get the following:
Could not connect to data source 'New Data Source':
An internal network library error has occurred. A network level conversational protocol error has occurred. SQLSTATE: HY000, SQLCODE: -343
The port I've configured is what is used when we use the IBM OLE DB and ODBC drivers. Where can I look to see what the problem is?
Thanks,
Mike
I'm moving your thread to the Data Access forum as you'll have a greater chance of having an OLEDB question answered.|||Hi,
some OLEDB providers have the functionality for logging implemented which can be turned on with a flag on the client side, this should give you more information about the error you ar egetting. The Provider flags are very specific so you should look in the documentation of the used provider.
HTH, jens Suessmeyer.
http://www.sqlserver2005.de
Sunday, February 26, 2012
Error connecting to a SQL 2005 (June CTP) Cube using Excel 2003
When I use the PivotTable Wizard in Excel 2003 to connect to a SQL 2005 cube
,
the wizard successfully finds and connects to the cube, but when I click
'finish' to retrieve the data, I get the following error:
"Initialization of the data source failed.
Check the database server or contact your database administrator. Make sure
the external database is available, and then try the operation again. If you
see this message again, create a new data source to connect to the database.
"
Any ideas what could be causing this? I have Excel 2003 and SQL 2005 (June
CTP) running on the same machine.
Thanks,
--
DuncanHi Duncan
I have the same error.
I have Excel 2000 and Excel 2003 installed on my pc and SQL server 2000 and
SQL Server 2005 installed on a server. It seems that I can use most
combinations of these 2 - Excel 2000 will read data from SQL server 2000 and
2005, Excel 2003 will read data from SQL Server 2000 cubes.
But I get the same error as you when I try to read data from SQL Server 2005
Analysis Services Cubes from Excel 2003. It knows the cubes are there but
can't read the data.
Did you manage to resolve this? Can anyone else help?
Regards
Dave
"Duncan" wrote:
> When I use the PivotTable Wizard in Excel 2003 to connect to a SQL 2005 cu
be,
> the wizard successfully finds and connects to the cube, but when I click
> 'finish' to retrieve the data, I get the following error:
> "Initialization of the data source failed.
> Check the database server or contact your database administrator. Make sur
e
> the external database is available, and then try the operation again. If y
ou
> see this message again, create a new data source to connect to the databas
e. "
> Any ideas what could be causing this? I have Excel 2003 and SQL 2005 (June
> CTP) running on the same machine.
> Thanks,
> --
> Duncan|||If you found a solution, please let me know. I'm getting the same error
message.
Thanks a lot.
Duncan wrote:
> *When I use the PivotTable Wizard in Excel 2003 to connect to a SQL
> 2005 cube,
> the wizard successfully finds and connects to the cube, but when I
> click
> 'finish' to retrieve the data, I get the following error:
> "Initialization of the data source failed.
> Check the database server or contact your database administrator.
> Make sure
> the external database is available, and then try the operation again.
> If you
> see this message again, create a new data source to connect to the
> database. "
> Any ideas what could be causing this? I have Excel 2003 and SQL 2005
> (June
> CTP) running on the same machine.
> Thanks,
> --
> Duncan *
hpanneflek
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1781676.html|||hpanneflek wrote:
> *If you found a solution, please let me know. I'm getting the same
> error message.
> Thanks a lot. *
I got around this by re-registering the OLAP v9.0 dll:
regsvr32 c:\program files\common files\system\oledb\msolap90.dll
This worked for me.
Good luck
Dave
Daffyd
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1781676.html|||Thank you! It worked.
I've been using AS 2K for 3 years now and I love it. I started playing
with AS2K5 and I am realizing that a lot of things changed. My email is
hpanneflek@.univision.net in case you have any question, I'll be glad to
help.
Thanks again.
Daffyd wrote:
> *I got around this by re-registering the OLAP v9.0 dll:
> regsvr32 c:\program files\common files\system\oledb\msolap90.dll
> This worked for me.
> Good luck
> Dave *
hpanneflek
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1781676.html
,
the wizard successfully finds and connects to the cube, but when I click
'finish' to retrieve the data, I get the following error:
"Initialization of the data source failed.
Check the database server or contact your database administrator. Make sure
the external database is available, and then try the operation again. If you
see this message again, create a new data source to connect to the database.
"
Any ideas what could be causing this? I have Excel 2003 and SQL 2005 (June
CTP) running on the same machine.
Thanks,
--
DuncanHi Duncan
I have the same error.
I have Excel 2000 and Excel 2003 installed on my pc and SQL server 2000 and
SQL Server 2005 installed on a server. It seems that I can use most
combinations of these 2 - Excel 2000 will read data from SQL server 2000 and
2005, Excel 2003 will read data from SQL Server 2000 cubes.
But I get the same error as you when I try to read data from SQL Server 2005
Analysis Services Cubes from Excel 2003. It knows the cubes are there but
can't read the data.
Did you manage to resolve this? Can anyone else help?
Regards
Dave
"Duncan" wrote:
> When I use the PivotTable Wizard in Excel 2003 to connect to a SQL 2005 cu
be,
> the wizard successfully finds and connects to the cube, but when I click
> 'finish' to retrieve the data, I get the following error:
> "Initialization of the data source failed.
> Check the database server or contact your database administrator. Make sur
e
> the external database is available, and then try the operation again. If y
ou
> see this message again, create a new data source to connect to the databas
e. "
> Any ideas what could be causing this? I have Excel 2003 and SQL 2005 (June
> CTP) running on the same machine.
> Thanks,
> --
> Duncan|||If you found a solution, please let me know. I'm getting the same error
message.
Thanks a lot.
Duncan wrote:
> *When I use the PivotTable Wizard in Excel 2003 to connect to a SQL
> 2005 cube,
> the wizard successfully finds and connects to the cube, but when I
> click
> 'finish' to retrieve the data, I get the following error:
> "Initialization of the data source failed.
> Check the database server or contact your database administrator.
> Make sure
> the external database is available, and then try the operation again.
> If you
> see this message again, create a new data source to connect to the
> database. "
> Any ideas what could be causing this? I have Excel 2003 and SQL 2005
> (June
> CTP) running on the same machine.
> Thanks,
> --
> Duncan *
hpanneflek
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1781676.html|||hpanneflek wrote:
> *If you found a solution, please let me know. I'm getting the same
> error message.
> Thanks a lot. *
I got around this by re-registering the OLAP v9.0 dll:
regsvr32 c:\program files\common files\system\oledb\msolap90.dll
This worked for me.
Good luck
Dave
Daffyd
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1781676.html|||Thank you! It worked.
I've been using AS 2K for 3 years now and I love it. I started playing
with AS2K5 and I am realizing that a lot of things changed. My email is
hpanneflek@.univision.net in case you have any question, I'll be glad to
help.
Thanks again.
Daffyd wrote:
> *I got around this by re-registering the OLAP v9.0 dll:
> regsvr32 c:\program files\common files\system\oledb\msolap90.dll
> This worked for me.
> Good luck
> Dave *
hpanneflek
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message1781676.html
Error connecting to a SQL 2005 (June CTP) Cube using Excel 2003
When I use the PivotTable Wizard in Excel 2003 to connect to a SQL 2005 cube,
the wizard successfully finds and connects to the cube, but when I click
'finish' to retrieve the data, I get the following error:
"Initialization of the data source failed.
Check the database server or contact your database administrator. Make sure
the external database is available, and then try the operation again. If you
see this message again, create a new data source to connect to the database. "
Any ideas what could be causing this? I have Excel 2003 and SQL 2005 (June
CTP) running on the same machine.
Thanks,
Duncan
Hi Duncan !
Have you got to resolve this problem ?
Unfortunately I also have it in my environment.
If possible tell me what you did.
Thank you !
Aduir.
Originally posted by Duncan
When I use the PivotTable Wizard in Excel 2003 to connect to a SQL 2005 cube,
the wizard successfully finds and connects to the cube, but when I click
'finish' to retrieve the data, I get the following error:
"Initialization of the data source failed.
Check the database server or contact your database administrator. Make sure
the external database is available, and then try the operation again. If you
see this message again, create a new data source to connect to the database. "
Any ideas what could be causing this? I have Excel 2003 and SQL 2005 (June
CTP) running on the same machine.
Thanks,
Duncan
Yours in hope,
Originally posted by Duncan
When I use the PivotTable Wizard in Excel 2003 to connect to a SQL 2005 cube,
the wizard successfully finds and connects to the cube, but when I click
'finish' to retrieve the data, I get the following error:
"Initialization of the data source failed.
Check the database server or contact your database administrator. Make sure
the external database is available, and then try the operation again. If you
see this message again, create a new data source to connect to the database. "
Any ideas what could be causing this? I have Excel 2003 and SQL 2005 (June
CTP) running on the same machine.
Thanks,
Duncan
I have the same error.
I have Excel 2000 and Excel 2003 installed on my pc and SQL server 2000 and
SQL Server 2005 installed on a server. It seems that I can use most
combinations of these 2 - Excel 2000 will read data from SQL server 2000 and
2005, Excel 2003 will read data from SQL Server 2000 cubes.
But I get the same error as you when I try to read data from SQL Server 2005
Analysis Services Cubes from Excel 2003. It knows the cubes are there but
can't read the data.
Did you manage to resolve this? Can anyone else help?
Regards
Dave
"Duncan" wrote:
> When I use the PivotTable Wizard in Excel 2003 to connect to a SQL 2005 cube,
> the wizard successfully finds and connects to the cube, but when I click
> 'finish' to retrieve the data, I get the following error:
> "Initialization of the data source failed.
> Check the database server or contact your database administrator. Make sure
> the external database is available, and then try the operation again. If you
> see this message again, create a new data source to connect to the database. "
> Any ideas what could be causing this? I have Excel 2003 and SQL 2005 (June
> CTP) running on the same machine.
> Thanks,
> --
> Duncan
the wizard successfully finds and connects to the cube, but when I click
'finish' to retrieve the data, I get the following error:
"Initialization of the data source failed.
Check the database server or contact your database administrator. Make sure
the external database is available, and then try the operation again. If you
see this message again, create a new data source to connect to the database. "
Any ideas what could be causing this? I have Excel 2003 and SQL 2005 (June
CTP) running on the same machine.
Thanks,
Duncan
Hi Duncan !
Have you got to resolve this problem ?
Unfortunately I also have it in my environment.
If possible tell me what you did.
Thank you !
Aduir.
Quote:
When I use the PivotTable Wizard in Excel 2003 to connect to a SQL 2005 cube,
the wizard successfully finds and connects to the cube, but when I click
'finish' to retrieve the data, I get the following error:
"Initialization of the data source failed.
Check the database server or contact your database administrator. Make sure
the external database is available, and then try the operation again. If you
see this message again, create a new data source to connect to the database. "
Any ideas what could be causing this? I have Excel 2003 and SQL 2005 (June
CTP) running on the same machine.
Thanks,
Duncan
Yours in hope,
Quote:
When I use the PivotTable Wizard in Excel 2003 to connect to a SQL 2005 cube,
the wizard successfully finds and connects to the cube, but when I click
'finish' to retrieve the data, I get the following error:
"Initialization of the data source failed.
Check the database server or contact your database administrator. Make sure
the external database is available, and then try the operation again. If you
see this message again, create a new data source to connect to the database. "
Any ideas what could be causing this? I have Excel 2003 and SQL 2005 (June
CTP) running on the same machine.
Thanks,
Duncan
I have the same error.
I have Excel 2000 and Excel 2003 installed on my pc and SQL server 2000 and
SQL Server 2005 installed on a server. It seems that I can use most
combinations of these 2 - Excel 2000 will read data from SQL server 2000 and
2005, Excel 2003 will read data from SQL Server 2000 cubes.
But I get the same error as you when I try to read data from SQL Server 2005
Analysis Services Cubes from Excel 2003. It knows the cubes are there but
can't read the data.
Did you manage to resolve this? Can anyone else help?
Regards
Dave
"Duncan" wrote:
> When I use the PivotTable Wizard in Excel 2003 to connect to a SQL 2005 cube,
> the wizard successfully finds and connects to the cube, but when I click
> 'finish' to retrieve the data, I get the following error:
> "Initialization of the data source failed.
> Check the database server or contact your database administrator. Make sure
> the external database is available, and then try the operation again. If you
> see this message again, create a new data source to connect to the database. "
> Any ideas what could be causing this? I have Excel 2003 and SQL 2005 (June
> CTP) running on the same machine.
> Thanks,
> --
> Duncan
Sunday, February 19, 2012
Error attempting to import from Excel
Here is the error:
TITLE: SQL Server Import and Export Wizard
An error occurred which the SQL Server Integration Services Wizard was not prepared to handle.
ADDITIONAL INFORMATION:
Exception has been thrown by the target of an invocation. (mscorlib)
The connection type "EXCEL" specified for connection manager "{55E5636D-F2A9-48D6-9723-867C9F241F5B}" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.
({F390DBA3-1B52-43F4-A624-9E71D273B4D7})
I really need to get this data into SQL server... why do I have to go through SQL 2000?
Regards,
Try to refresh your connection manager or recreate a manager. Seems like when you move the package the connection properties got lost.|||This is happening from the Wizard. It happens even after I shut down the SQL server tools and restart them. It happens as I am creating the package. It is not letting me choose Excel at all with this message.
Thanks in advance ...
|||I get the same error as you. This was working for me, then suddenly it stopped working.
Have you found a resolution for this error?
|||It looks like the registration of connections got broken during the setup on your mahines.
Could you guys check if dtsconn.dll is in your %ProgramFiles%\Microsoft SQL Server\90\DTS\Binn folder?
If it is there try to register it:
regsvr32 dtsconn.dll
HTH.
|||I have not got this fixed yet and no, registering dtsconn.dll did not fix the problem. But it looks like some sort of registration is corrupt.
An interesting observation is that as soon as Excel is selected as a source it crashes.
R
|||The follwoing post helped me fix it.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PageIndex=4&SiteID=1&PostID=363238&PageID=1
The 2nd page of post has a program for you to create and then run.
Read through the post for the directions. It worked for me.
Error attempting to import from Excel
Here is the error:
TITLE: SQL Server Import and Export Wizard
An error occurred which the SQL Server Integration Services Wizard was not prepared to handle.
ADDITIONAL INFORMATION:
Exception has been thrown by the target of an invocation. (mscorlib)
The connection type "EXCEL" specified for connection manager "{55E5636D-F2A9-48D6-9723-867C9F241F5B}" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.
({F390DBA3-1B52-43F4-A624-9E71D273B4D7})
I really need to get this data into SQL server... why do I have to go through SQL 2000?
Regards,
Try to refresh your connection manager or recreate a manager. Seems like when you move the package the connection properties got lost.|||This is happening from the Wizard. It happens even after I shut down the SQL server tools and restart them. It happens as I am creating the package. It is not letting me choose Excel at all with this message.
Thanks in advance ...
|||I get the same error as you. This was working for me, then suddenly it stopped working.
Have you found a resolution for this error?
|||It looks like the registration of connections got broken during the setup on your mahines.
Could you guys check if dtsconn.dll is in your %ProgramFiles%\Microsoft SQL Server\90\DTS\Binn folder?
If it is there try to register it:
regsvr32 dtsconn.dll
HTH.
|||I have not got this fixed yet and no, registering dtsconn.dll did not fix the problem. But it looks like some sort of registration is corrupt.
An interesting observation is that as soon as Excel is selected as a source it crashes.
R
|||The follwoing post helped me fix it.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PageIndex=4&SiteID=1&PostID=363238&PageID=1
The 2nd page of post has a program for you to create and then run.
Read through the post for the directions. It worked for me.
Wednesday, February 15, 2012
Error after Disabling Merge Replication
Hi...
I disabled merge replication via the Ent. Mgr wizard and when I try to update a table that was previously part of the replication (either via stored proc or manually in query analyzer) I get this error:
Invalid object name 'dbo.sysmergearticles'
I am guessing that there are still some references or parts of the replication that were somehow left around even after disabling replication. I don't have this table in my database anymore.
Does anyone know how to resolve this issue?
Thanks
- dw
dw,
if the database is no longer involved in replication, either as a subscriber
or as a publisher, then you can run sp_removedbreplication.
HTH,
Paul Ibison
|||It sounds like the merge triggers are still in place. To get this working correctly you should run this script in your former subscription database.
DECLARE @.name varchar(129)
DECLARE list_pubs CURSOR FOR
SELECT name FROM syspublications
OPEN list_pubs
FETCH NEXT FROM list_pubs INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping publication ' +@.name
EXEC sp_dropsubscription @.publication=@.name,
@.article='all', @.subscriber ='all'
EXEC sp_droppublication @.name
FETCH NEXT FROM list_pubs INTO @.name
END
CLOSE list_pubs
DEALLOCATE list_pubs
GO
DECLARE @.name varchar(129)
DECLARE list_replicated_tables CURSOR FOR
SELECT name FROM sysobjects WHERE replinfo 0
UNION
SELECT name FROM sysmergearticles
OPEN list_replicated_tables
FETCH NEXT FROM list_replicated_tables INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'unmarking replicated table ' +@.name
--select @.name='drop Table ' + @.name
EXEC sp_msunmarkreplinfo @.name
FETCH NEXT FROM list_replicated_tables INTO @.name
END
CLOSE list_replicated_tables
DEALLOCATE list_replicated_tables
GO
UPDATE syscolumns set colstat = colstat & ~4096 WHERE
colstat &4096 0
GO
UPDATE sysobjects set replinfo=0
GO
DECLARE @.name nvarchar(129)
DECLARE list_views CURSOR FOR
SELECT name FROM sysobjects WHERE type='V' and (name
like 'syncobj_%' or name like 'ctsv_%' or name
like 'tsvw_%')
OPEN list_views
FETCH NEXT FROM list_views INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping View ' +@.name
select @.name='drop View ' + @.name
EXEC sp_executesql @.name
FETCH NEXT FROM list_views INTO @.name
END
CLOSE list_views
DEALLOCATE list_views
GO
DECLARE @.name nvarchar(129)
DECLARE list_procs CURSOR FOR
SELECT name FROM sysobjects WHERE type='p' and (name
like 'sp_ins_%' or name like 'sp_MSdel_%' or name
like 'sp_MSins_%'or name like 'sp_MSupd_%' or name
like 'sp_sel_%' or name like 'sp_upd_%')
OPEN list_procs
FETCH NEXT FROM list_procs INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping procs ' +@.name
select @.name='drop procedure ' + @.name
EXEC sp_executesql @.name
FETCH NEXT FROM list_procs INTO @.name
END
CLOSE list_procs
DEALLOCATE list_procs
GO
DECLARE @.name nvarchar(129)
DECLARE list_conflict_tables CURSOR FOR
SELECT name From sysobjects WHERE type='u' and name
like '_onflict%'
OPEN list_conflict_tables
FETCH NEXT FROM list_conflict_tables INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping conflict_tables ' +@.name
select @.name='drop Table ' + @.name
EXEC sp_executesql @.name
FETCH NEXT FROM list_conflict_tables INTO @.name
END
CLOSE list_conflict_tables
DEALLOCATE list_conflict_tables
GO
UPDATE syscolumns set colstat=2 WHERE name='rowguid'
GO
Declare @.name nvarchar(129), @.constraint nvarchar(129)
DECLARE list_rowguid_constraints CURSOR FOR
select object_name(sysobjects.parent_obj), sysobjects.name
from sysobjects, syscolumns where sysobjects.type ='d'
and syscolumns.id=sysobjects.parent_obj
and syscolumns.name='rowguid'
OPEN list_rowguid_constraints
FETCH NEXT FROM list_rowguid_constraints INTO @.name,
@.constraint
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping rowguid constraints ' +@.name
select @.name='ALTER TABLE ' + rtrim(@.name ) + '
DROP CONSTRAINT ' +@.constraint
EXEC sp_executesql @.name
FETCH NEXT FROM list_rowguid_constraints INTO
@.name, @.constraint
END
CLOSE list_rowguid_constraints
DEALLOCATE list_rowguid_constraints
GO
Declare @.name nvarchar(129), @.constraint nvarchar(129)
DECLARE list_rowguid_indexes CURSOR FOR
select object_name(id), name from sysindexes where name
like 'index%'
OPEN list_rowguid_indexes
FETCH NEXT FROM list_rowguid_indexes INTO @.name,
@.constraint
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping rowguid indexes ' +@.name
select @.name='drop index ' + rtrim(@.name ) + '.'
+@.constraint
EXEC sp_executesql @.name
FETCH NEXT FROM list_rowguid_indexes INTO @.name,
@.constraint
END
CLOSE list_rowguid_indexes
DEALLOCATE list_rowguid_indexes
GO
Declare @.name nvarchar(129)
DECLARE list_rowguid_columns CURSOR FOR
select object_name(syscolumns.id) from syscolumns,
sysobjects where syscolumns.name like 'rowguid' and
object_Name(sysobjects.id) not like 'msmerge%'
and sysobjects.id=syscolumns.id
and sysobjects.type='u' order by 1
OPEN list_rowguid_columns
FETCH NEXT FROM list_rowguid_columns INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping rowguid columns ' +@.name
select @.name='Alter Table ' + rtrim(@.name ) + '
drop column rowguid'
print @.name
EXEC sp_executesql @.name
FETCH NEXT FROM list_rowguid_columns INTO @.name
END
CLOSE list_rowguid_columns
DEALLOCATE list_rowguid_columns
GO
DELETE FROM sysmergepublications
GO
DELETE FROM sysmergesubscriptions
GO
DELETE FROM syssubscriptions
GO
DELETE FROM sysarticleupdates
GO
DELETE FROM systranschemas
GO
DELETE FROM sysmergearticles
GO
DELETE FROM sysmergeschemaarticles
GO
DELETE FROM sysmergesubscriptions
GO
DELETE FROM sysarticles
GO
DELETE FROM sysschemaarticles
GO
DELETE FROM syspublications
GO
DELETE FROM sysmergeschemachange
GO
DELETE FROM sysmergesubsetfilters
GO
DELETE FROM MSdynamicsnapshotjobs
GO
DELETE FROM MSdynamicsnapshotviews
GO
DELETE FROM MSmerge_altsyncpartners
GO
DELETE FROM MSmerge_contents
GO
DELETE FROM MSmerge_delete_conflicts
GO
DELETE FROM MSmerge_errorlineage
GO
DELETE FROM MSmerge_genhistory
GO
DELETE FROM MSmerge_replinfo
GO
DELETE FROM MSmerge_tombstone
GO
DELETE FROM MSpub_identity_range
GO
DELETE FROM MSrepl_identity_range
GO
DELETE FROM MSreplication_subscriptions
GO
DELETE FROM MSsubscription_agents
GO
|||Thanks folks. The problem was the triggers. I manually deleted them (I didn't see the replies to this message earlier) and now it works. However, I will be making a copy of the script that Hilary provided.
great! - dw
I disabled merge replication via the Ent. Mgr wizard and when I try to update a table that was previously part of the replication (either via stored proc or manually in query analyzer) I get this error:
Invalid object name 'dbo.sysmergearticles'
I am guessing that there are still some references or parts of the replication that were somehow left around even after disabling replication. I don't have this table in my database anymore.
Does anyone know how to resolve this issue?
Thanks
- dw
dw,
if the database is no longer involved in replication, either as a subscriber
or as a publisher, then you can run sp_removedbreplication.
HTH,
Paul Ibison
|||It sounds like the merge triggers are still in place. To get this working correctly you should run this script in your former subscription database.
DECLARE @.name varchar(129)
DECLARE list_pubs CURSOR FOR
SELECT name FROM syspublications
OPEN list_pubs
FETCH NEXT FROM list_pubs INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping publication ' +@.name
EXEC sp_dropsubscription @.publication=@.name,
@.article='all', @.subscriber ='all'
EXEC sp_droppublication @.name
FETCH NEXT FROM list_pubs INTO @.name
END
CLOSE list_pubs
DEALLOCATE list_pubs
GO
DECLARE @.name varchar(129)
DECLARE list_replicated_tables CURSOR FOR
SELECT name FROM sysobjects WHERE replinfo 0
UNION
SELECT name FROM sysmergearticles
OPEN list_replicated_tables
FETCH NEXT FROM list_replicated_tables INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'unmarking replicated table ' +@.name
--select @.name='drop Table ' + @.name
EXEC sp_msunmarkreplinfo @.name
FETCH NEXT FROM list_replicated_tables INTO @.name
END
CLOSE list_replicated_tables
DEALLOCATE list_replicated_tables
GO
UPDATE syscolumns set colstat = colstat & ~4096 WHERE
colstat &4096 0
GO
UPDATE sysobjects set replinfo=0
GO
DECLARE @.name nvarchar(129)
DECLARE list_views CURSOR FOR
SELECT name FROM sysobjects WHERE type='V' and (name
like 'syncobj_%' or name like 'ctsv_%' or name
like 'tsvw_%')
OPEN list_views
FETCH NEXT FROM list_views INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping View ' +@.name
select @.name='drop View ' + @.name
EXEC sp_executesql @.name
FETCH NEXT FROM list_views INTO @.name
END
CLOSE list_views
DEALLOCATE list_views
GO
DECLARE @.name nvarchar(129)
DECLARE list_procs CURSOR FOR
SELECT name FROM sysobjects WHERE type='p' and (name
like 'sp_ins_%' or name like 'sp_MSdel_%' or name
like 'sp_MSins_%'or name like 'sp_MSupd_%' or name
like 'sp_sel_%' or name like 'sp_upd_%')
OPEN list_procs
FETCH NEXT FROM list_procs INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping procs ' +@.name
select @.name='drop procedure ' + @.name
EXEC sp_executesql @.name
FETCH NEXT FROM list_procs INTO @.name
END
CLOSE list_procs
DEALLOCATE list_procs
GO
DECLARE @.name nvarchar(129)
DECLARE list_conflict_tables CURSOR FOR
SELECT name From sysobjects WHERE type='u' and name
like '_onflict%'
OPEN list_conflict_tables
FETCH NEXT FROM list_conflict_tables INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping conflict_tables ' +@.name
select @.name='drop Table ' + @.name
EXEC sp_executesql @.name
FETCH NEXT FROM list_conflict_tables INTO @.name
END
CLOSE list_conflict_tables
DEALLOCATE list_conflict_tables
GO
UPDATE syscolumns set colstat=2 WHERE name='rowguid'
GO
Declare @.name nvarchar(129), @.constraint nvarchar(129)
DECLARE list_rowguid_constraints CURSOR FOR
select object_name(sysobjects.parent_obj), sysobjects.name
from sysobjects, syscolumns where sysobjects.type ='d'
and syscolumns.id=sysobjects.parent_obj
and syscolumns.name='rowguid'
OPEN list_rowguid_constraints
FETCH NEXT FROM list_rowguid_constraints INTO @.name,
@.constraint
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping rowguid constraints ' +@.name
select @.name='ALTER TABLE ' + rtrim(@.name ) + '
DROP CONSTRAINT ' +@.constraint
EXEC sp_executesql @.name
FETCH NEXT FROM list_rowguid_constraints INTO
@.name, @.constraint
END
CLOSE list_rowguid_constraints
DEALLOCATE list_rowguid_constraints
GO
Declare @.name nvarchar(129), @.constraint nvarchar(129)
DECLARE list_rowguid_indexes CURSOR FOR
select object_name(id), name from sysindexes where name
like 'index%'
OPEN list_rowguid_indexes
FETCH NEXT FROM list_rowguid_indexes INTO @.name,
@.constraint
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping rowguid indexes ' +@.name
select @.name='drop index ' + rtrim(@.name ) + '.'
+@.constraint
EXEC sp_executesql @.name
FETCH NEXT FROM list_rowguid_indexes INTO @.name,
@.constraint
END
CLOSE list_rowguid_indexes
DEALLOCATE list_rowguid_indexes
GO
Declare @.name nvarchar(129)
DECLARE list_rowguid_columns CURSOR FOR
select object_name(syscolumns.id) from syscolumns,
sysobjects where syscolumns.name like 'rowguid' and
object_Name(sysobjects.id) not like 'msmerge%'
and sysobjects.id=syscolumns.id
and sysobjects.type='u' order by 1
OPEN list_rowguid_columns
FETCH NEXT FROM list_rowguid_columns INTO @.name
WHILE @.@.FETCH_STATUS = 0
BEGIN
PRINT 'dropping rowguid columns ' +@.name
select @.name='Alter Table ' + rtrim(@.name ) + '
drop column rowguid'
print @.name
EXEC sp_executesql @.name
FETCH NEXT FROM list_rowguid_columns INTO @.name
END
CLOSE list_rowguid_columns
DEALLOCATE list_rowguid_columns
GO
DELETE FROM sysmergepublications
GO
DELETE FROM sysmergesubscriptions
GO
DELETE FROM syssubscriptions
GO
DELETE FROM sysarticleupdates
GO
DELETE FROM systranschemas
GO
DELETE FROM sysmergearticles
GO
DELETE FROM sysmergeschemaarticles
GO
DELETE FROM sysmergesubscriptions
GO
DELETE FROM sysarticles
GO
DELETE FROM sysschemaarticles
GO
DELETE FROM syspublications
GO
DELETE FROM sysmergeschemachange
GO
DELETE FROM sysmergesubsetfilters
GO
DELETE FROM MSdynamicsnapshotjobs
GO
DELETE FROM MSdynamicsnapshotviews
GO
DELETE FROM MSmerge_altsyncpartners
GO
DELETE FROM MSmerge_contents
GO
DELETE FROM MSmerge_delete_conflicts
GO
DELETE FROM MSmerge_errorlineage
GO
DELETE FROM MSmerge_genhistory
GO
DELETE FROM MSmerge_replinfo
GO
DELETE FROM MSmerge_tombstone
GO
DELETE FROM MSpub_identity_range
GO
DELETE FROM MSrepl_identity_range
GO
DELETE FROM MSreplication_subscriptions
GO
DELETE FROM MSsubscription_agents
GO
|||Thanks folks. The problem was the triggers. I manually deleted them (I didn't see the replies to this message earlier) and now it works. However, I will be making a copy of the script that Hilary provided.
great! - dw
Subscribe to:
Posts (Atom)