Showing posts with label sp3. Show all posts
Showing posts with label sp3. Show all posts

Thursday, March 29, 2012

Error accepting connection request via Net-Library 'SSNETLIB'

Hi,
I installed SP3 over SQL2K on NT Server SP6. The Server
hangs on startup. This is after I did an upgrade
installation of SQL 7 to SQL Server 2000 and applied SP3
over it. Everything runs fine for afew hours and then we
get the message below and some of our servers lose the
ability to connect to the sql server.
2003-12-18 10:20:08.84 spid65 Using 'xp_AltaMX.dll' version
'0002.00.00' to execute extended stored
procedure 'xp_AltaMX'.
2003-12-18 11:01:49.43 spid62 Using 'xpipass.dll'
version 'UNKNOWN'to execute extended stored
procedure 'xp_ipass_actualiza'.
2003-12-18 12:24:01.62 server Error: 17882, Severity: 18,
State: 1
2003-12-18 12:24:01.62 server Error accepting connection
request via Net-Library 'SSNETLIB'. Execution continuing..
2003-12-18 12:24:01.62 server Error: 17059, Severity: 18,
State: 0
2003-12-18 12:24:01.62 server Operating system error 1:
Incorrect function...
2003-12-18 12:31:58.09 server SQL Server could not spawn
process_loginread thread.
2003-12-18 12:31:59.09 server Error: 17882, Severity: 18,
State: 1
2003-12-18 12:31:59.09 server Error accepting connection
request via Net-Library 'SSNETLIB'. Execution continuing..
2003-12-18 12:31:59.09 server Error: 17059, Severity: 18,
State: 0
2003-12-18 12:31:59.09 server Operating system error 1:
Incorrect function...
2003-12-18 12:41:30.01 server Error: 17882, Severity: 18,
State: 1
2003-12-18 12:41:30.01 server Error accepting connection
request via Net-Library 'SSNETLIB'. Execution continuing..
2003-12-18 12:41:30.01 server Error: 17059, Severity: 18,
State: 0
2003-12-18 12:41:30.01 server Operating system error 1:
Incorrect function...
2003-12-18 12:51:21.10 server SQL Server is disallowing new
connections due to 'pause' request from Service Control
Manager.
2003-12-18 12:53:09.60 spid3 SQL Server is terminating due
to 'stop' request from Service Control Manager.
I would be greatful if anyone has any ideas on how to deal
with this ?
I already reviewed this article but me it has not been
helpful.
http://support.microsoft.com/default.aspx?scid=kb;en-
us;811887&Product=sql2k
I am of course afraid that someday we will not be able to
access the
sql server.
Regards,
LeoWho supplied you with
xp_AltaMX
xpipass.dll
xp_ipass_actualiza
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi Kevin,
The development area supplied them. Let me tell you=20
something, when this server was working under SQL 7, this=20
error never appeared. After upgrade the error appeared.
Do you think that the problem may be are the xp=B4s?
thanks,
Leo|||Drop /remove the xp's and see if the problem persists. Do this in your
Test environment.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.sql

Thursday, March 22, 2012

error 8198

sql2k sp3
win2k sp4
Im trying to create a Pull Subscription for replication and get "Error 8198:
Could not obtain information about Windows NT group/ user 'domain/ user'".
I read this:
http://support.microsoft.com/?kbid=834124
But both boxes are in the same domain and the same subnet. Both use the same
domain admin account for SQL Server and the Agent accounts.
I also read this:
http://support.microsoft.com/?kbid=838460
But Im not about to install sp4 Beta on anything.
Is there anything else I can do?
TIA, ChrisRright click on your agent and make the agent owner sa. Restart your job.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"ChrisR" <noemail@.bla.com> wrote in message
news:OZAuC21SFHA.2256@.tk2msftngp13.phx.gbl...
> sql2k sp3
> win2k sp4
> Im trying to create a Pull Subscription for replication and get "Error
8198:
> Could not obtain information about Windows NT group/ user 'domain/ user'".
> I read this:
> http://support.microsoft.com/?kbid=834124
> But both boxes are in the same domain and the same subnet. Both use the
same
> domain admin account for SQL Server and the Agent accounts.
> I also read this:
> http://support.microsoft.com/?kbid=838460
> But Im not about to install sp4 Beta on anything.
> Is there anything else I can do?
> TIA, ChrisR
>|||Which Agent are you referring too? All of the jobs are owned by SA.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23RPeZF2SFHA.3544@.TK2MSFTNGP12.phx.gbl...
> right click on your agent and make the agent owner sa. Restart your job.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "ChrisR" <noemail@.bla.com> wrote in message
> news:OZAuC21SFHA.2256@.tk2msftngp13.phx.gbl...
>> sql2k sp3
>> win2k sp4
>> Im trying to create a Pull Subscription for replication and get "Error
> 8198:
>> Could not obtain information about Windows NT group/ user 'domain/
>> user'".
>> I read this:
>> http://support.microsoft.com/?kbid=834124
>> But both boxes are in the same domain and the same subnet. Both use the
> same
>> domain admin account for SQL Server and the Agent accounts.
>> I also read this:
>> http://support.microsoft.com/?kbid=838460
>> But Im not about to install sp4 Beta on anything.
>> Is there anything else I can do?
>> TIA, ChrisR
>>
>

Wednesday, March 7, 2012

Error 3724: Cannot Drop Database

Hello All,
I am trying to delete couple of database in SQL 2000, SP3 and getting this
error:
Error: 3724: Cannot drop database because it is being used for replication.
There are no publications or subscriptions for the databases either. I did
also run one remove publication procedure but that did not help either.
Is there anyway I can delete these databases? Will appreciate all help.
Thanks and Regards
--
Fakhruddin Zavery
Sr. Systems Analyst / Programmer
CATS Tanzania Ltd.
NIC Life House 4th Floor
P. O. Box 2569, Dar es Salaam, Tanzania
Tel. +255-22 2137915, 2112631
Fax +255-22 2113033, 2112916
Mob +255 744 277452
website: http://www.catsgroup.com
----
--
The Irony of Life is that, no one gets out of it Alive
----
--Heck... the easiest way is to just shut down SQL and rename the files. It will come up as suspect then you can delete them. Not the correct way though
Jeff|||I tried that as well Jeff, it came up as suspect but when I try to delete it
still gives me the same error.
I even tried issuing the command DROP database from master but the same
error coems up.
"Jeff Duncan" <anonymous@.discussions.microsoft.com> wrote in message
news:B12D8244-922B-4153-9F2A-FE4ACE793D12@.microsoft.com...
> Heck... the easiest way is to just shut down SQL and rename the files.
It will come up as suspect then you can delete them. Not the correct way
though.
> Jeff|||Can't you just detach the database and delete the files?
"Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
news:uykRwvGKEHA.1392@.TK2MSFTNGP09.phx.gbl...
> I tried that as well Jeff, it came up as suspect but when I try to delete
it
> still gives me the same error.
> I even tried issuing the command DROP database from master but the same
> error coems up.
>
> "Jeff Duncan" <anonymous@.discussions.microsoft.com> wrote in message
> news:B12D8244-922B-4153-9F2A-FE4ACE793D12@.microsoft.com...
> > Heck... the easiest way is to just shut down SQL and rename the files.
> It will come up as suspect then you can delete them. Not the correct way
> though.
> >
> > Jeff
>|||If I try to detach it says cannot be detached because it is being used in
replication.
"Jo Segers" <segers_jo@.hotmail.com> wrote in message
news:#qaFC0GKEHA.3292@.TK2MSFTNGP11.phx.gbl...
> Can't you just detach the database and delete the files?
> "Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
> news:uykRwvGKEHA.1392@.TK2MSFTNGP09.phx.gbl...
> > I tried that as well Jeff, it came up as suspect but when I try to
delete
> it
> > still gives me the same error.
> > I even tried issuing the command DROP database from master but the same
> > error coems up.
> >
> >
> >
> > "Jeff Duncan" <anonymous@.discussions.microsoft.com> wrote in message
> > news:B12D8244-922B-4153-9F2A-FE4ACE793D12@.microsoft.com...
> > > Heck... the easiest way is to just shut down SQL and rename the
files.
> > It will come up as suspect then you can delete them. Not the correct
way
> > though.
> > >
> > > Jeff
> >
> >
>|||Is it not possible to disable replication? (I don't use replication so I
have no experience with it.)
From the BOL:
To disable replication using the SQL Server Enterprise Manager
1.. Expand a server group, and then expand the Distributor (the server
that contains the distribution database).
2.. Right-click the Replication folder, and then click Disable Publishing.
3.. Complete the steps in the Disable Publishing and Distribution Wizard.
"Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
news:eulw24GKEHA.1388@.TK2MSFTNGP09.phx.gbl...
> If I try to detach it says cannot be detached because it is being used in
> replication.
> "Jo Segers" <segers_jo@.hotmail.com> wrote in message
> news:#qaFC0GKEHA.3292@.TK2MSFTNGP11.phx.gbl...
> > Can't you just detach the database and delete the files?
> >
> > "Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
> > news:uykRwvGKEHA.1392@.TK2MSFTNGP09.phx.gbl...
> > > I tried that as well Jeff, it came up as suspect but when I try to
> delete
> > it
> > > still gives me the same error.
> > > I even tried issuing the command DROP database from master but the
same
> > > error coems up.
> > >
> > >
> > >
> > > "Jeff Duncan" <anonymous@.discussions.microsoft.com> wrote in message
> > > news:B12D8244-922B-4153-9F2A-FE4ACE793D12@.microsoft.com...
> > > > Heck... the easiest way is to just shut down SQL and rename the
> files.
> > > It will come up as suspect then you can delete them. Not the correct
> way
> > > though.
> > > >
> > > > Jeff
> > >
> > >
> >
> >
>|||If you post this in the replication group, I'm sure they will point you to the stored procedures you need to
call to make SQL Server forget about the replication.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> wrote in message
news:eulw24GKEHA.1388@.TK2MSFTNGP09.phx.gbl...
> If I try to detach it says cannot be detached because it is being used in
> replication.
> "Jo Segers" <segers_jo@.hotmail.com> wrote in message
> news:#qaFC0GKEHA.3292@.TK2MSFTNGP11.phx.gbl...
> > Can't you just detach the database and delete the files?
> >
> > "Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
> > news:uykRwvGKEHA.1392@.TK2MSFTNGP09.phx.gbl...
> > > I tried that as well Jeff, it came up as suspect but when I try to
> delete
> > it
> > > still gives me the same error.
> > > I even tried issuing the command DROP database from master but the same
> > > error coems up.
> > >
> > >
> > >
> > > "Jeff Duncan" <anonymous@.discussions.microsoft.com> wrote in message
> > > news:B12D8244-922B-4153-9F2A-FE4ACE793D12@.microsoft.com...
> > > > Heck... the easiest way is to just shut down SQL and rename the
> files.
> > > It will come up as suspect then you can delete them. Not the correct
> way
> > > though.
> > > >
> > > > Jeff
> > >
> > >
> >
> >
>|||Jo been down that route as well but no luck, actually I had 3 databases to
delete all similar and perfoming same actions as this one, 2 of them I could
take them offline and delete after removing publications etc but this one I
can not delete for some funny reason.
"Jo Segers" <segers_jo@.hotmail.com> wrote in message
news:e716g#GKEHA.556@.tk2msftngp13.phx.gbl...
> Is it not possible to disable replication? (I don't use replication so I
> have no experience with it.)
> From the BOL:
> To disable replication using the SQL Server Enterprise Manager
> 1.. Expand a server group, and then expand the Distributor (the server
> that contains the distribution database).
>
> 2.. Right-click the Replication folder, and then click Disable
Publishing.
>
> 3.. Complete the steps in the Disable Publishing and Distribution
Wizard.
> "Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
> news:eulw24GKEHA.1388@.TK2MSFTNGP09.phx.gbl...
> > If I try to detach it says cannot be detached because it is being used
in
> > replication.
> >
> > "Jo Segers" <segers_jo@.hotmail.com> wrote in message
> > news:#qaFC0GKEHA.3292@.TK2MSFTNGP11.phx.gbl...
> > > Can't you just detach the database and delete the files?
> > >
> > > "Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
> > > news:uykRwvGKEHA.1392@.TK2MSFTNGP09.phx.gbl...
> > > > I tried that as well Jeff, it came up as suspect but when I try to
> > delete
> > > it
> > > > still gives me the same error.
> > > > I even tried issuing the command DROP database from master but the
> same
> > > > error coems up.
> > > >
> > > >
> > > >
> > > > "Jeff Duncan" <anonymous@.discussions.microsoft.com> wrote in message
> > > > news:B12D8244-922B-4153-9F2A-FE4ACE793D12@.microsoft.com...
> > > > > Heck... the easiest way is to just shut down SQL and rename the
> > files.
> > > > It will come up as suspect then you can delete them. Not the
correct
> > way
> > > > though.
> > > > >
> > > > > Jeff
> > > >
> > > >
> > >
> > >
> >
> >
>|||Thanks Tibor, will try and do that.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:#VwLgAHKEHA.2024@.TK2MSFTNGP11.phx.gbl...
> If you post this in the replication group, I'm sure they will point you to
the stored procedures you need to
> call to make SQL Server forget about the replication.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
>
> "Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> wrote in message
> news:eulw24GKEHA.1388@.TK2MSFTNGP09.phx.gbl...
> > If I try to detach it says cannot be detached because it is being used
in
> > replication.
> >
> > "Jo Segers" <segers_jo@.hotmail.com> wrote in message
> > news:#qaFC0GKEHA.3292@.TK2MSFTNGP11.phx.gbl...
> > > Can't you just detach the database and delete the files?
> > >
> > > "Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
> > > news:uykRwvGKEHA.1392@.TK2MSFTNGP09.phx.gbl...
> > > > I tried that as well Jeff, it came up as suspect but when I try to
> > delete
> > > it
> > > > still gives me the same error.
> > > > I even tried issuing the command DROP database from master but the
same
> > > > error coems up.
> > > >
> > > >
> > > >
> > > > "Jeff Duncan" <anonymous@.discussions.microsoft.com> wrote in message
> > > > news:B12D8244-922B-4153-9F2A-FE4ACE793D12@.microsoft.com...
> > > > > Heck... the easiest way is to just shut down SQL and rename the
> > files.
> > > > It will come up as suspect then you can delete them. Not the
correct
> > way
> > > > though.
> > > > >
> > > > > Jeff
> > > >
> > > >
> > >
> > >
> >
> >
>|||If you run:
sp_removedbreplication 'dbname'
go
exec sp_dboption 'dbname','published',false
go
exec sp_dboption 'dbname','merge publish',false
go
this should do it for you.
Regards,
Paul Ibison

Error 3724: Cannot Drop Database

Hello All,
I am trying to delete couple of database in SQL 2000, SP3 and getting this
error:
Error: 3724: Cannot drop database because it is being used for replication.
There are no publications or subscriptions for the databases either. I did
also run one remove publication procedure but that did not help either.
Is there anyway I can delete these databases? Will appreciate all help.
Thanks and Regards
Fakhruddin Zavery
Sr. Systems Analyst / Programmer
CATS Tanzania Ltd.
NIC Life House 4th Floor
P. O. Box 2569, Dar es Salaam, Tanzania
Tel. +255-22 2137915, 2112631
Fax +255-22 2113033, 2112916
Mob +255 744 277452
website: http://www.catsgroup.com
The Irony of Life is that, no one gets out of it Alive
Heck... the easiest way is to just shut down SQL and rename the files. It will come up as suspect then you can delete them. Not the correct way though.
Jeff
|||I tried that as well Jeff, it came up as suspect but when I try to delete it
still gives me the same error.
I even tried issuing the command DROP database from master but the same
error coems up.
"Jeff Duncan" <anonymous@.discussions.microsoft.com> wrote in message
news:B12D8244-922B-4153-9F2A-FE4ACE793D12@.microsoft.com...
> Heck... the easiest way is to just shut down SQL and rename the files.
It will come up as suspect then you can delete them. Not the correct way
though.
> Jeff
|||Can't you just detach the database and delete the files?
"Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
news:uykRwvGKEHA.1392@.TK2MSFTNGP09.phx.gbl...
> I tried that as well Jeff, it came up as suspect but when I try to delete
it
> still gives me the same error.
> I even tried issuing the command DROP database from master but the same
> error coems up.
>
> "Jeff Duncan" <anonymous@.discussions.microsoft.com> wrote in message
> news:B12D8244-922B-4153-9F2A-FE4ACE793D12@.microsoft.com...
> It will come up as suspect then you can delete them. Not the correct way
> though.
>
|||If I try to detach it says cannot be detached because it is being used in
replication.
"Jo Segers" <segers_jo@.hotmail.com> wrote in message
news:#qaFC0GKEHA.3292@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Can't you just detach the database and delete the files?
> "Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
> news:uykRwvGKEHA.1392@.TK2MSFTNGP09.phx.gbl...
delete[vbcol=seagreen]
> it
files.[vbcol=seagreen]
way
>
|||Is it not possible to disable replication? (I don't use replication so I
have no experience with it.)
From the BOL:
To disable replication using the SQL Server Enterprise Manager
1.. Expand a server group, and then expand the Distributor (the server
that contains the distribution database).
2.. Right-click the Replication folder, and then click Disable Publishing.
3.. Complete the steps in the Disable Publishing and Distribution Wizard.
"Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
news:eulw24GKEHA.1388@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> If I try to detach it says cannot be detached because it is being used in
> replication.
> "Jo Segers" <segers_jo@.hotmail.com> wrote in message
> news:#qaFC0GKEHA.3292@.TK2MSFTNGP11.phx.gbl...
> delete
same
> files.
> way
>
|||If you post this in the replication group, I'm sure they will point you to the stored procedures you need to
call to make SQL Server forget about the replication.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> wrote in message
news:eulw24GKEHA.1388@.TK2MSFTNGP09.phx.gbl...
> If I try to detach it says cannot be detached because it is being used in
> replication.
> "Jo Segers" <segers_jo@.hotmail.com> wrote in message
> news:#qaFC0GKEHA.3292@.TK2MSFTNGP11.phx.gbl...
> delete
> files.
> way
>
|||Jo been down that route as well but no luck, actually I had 3 databases to
delete all similar and perfoming same actions as this one, 2 of them I could
take them offline and delete after removing publications etc but this one I
can not delete for some funny reason.
"Jo Segers" <segers_jo@.hotmail.com> wrote in message
news:e716g#GKEHA.556@.tk2msftngp13.phx.gbl...
> Is it not possible to disable replication? (I don't use replication so I
> have no experience with it.)
> From the BOL:
> To disable replication using the SQL Server Enterprise Manager
> 1.. Expand a server group, and then expand the Distributor (the server
> that contains the distribution database).
>
> 2.. Right-click the Replication folder, and then click Disable
Publishing.
>
> 3.. Complete the steps in the Disable Publishing and Distribution
Wizard.[vbcol=seagreen]
> "Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
> news:eulw24GKEHA.1388@.TK2MSFTNGP09.phx.gbl...
in[vbcol=seagreen]
> same
correct
>
|||Thanks Tibor, will try and do that.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:#VwLgAHKEHA.2024@.TK2MSFTNGP11.phx.gbl...
> If you post this in the replication group, I'm sure they will point you to
the stored procedures you need to[vbcol=seagreen]
> call to make SQL Server forget about the replication.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
>
> "Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> wrote in message
> news:eulw24GKEHA.1388@.TK2MSFTNGP09.phx.gbl...
in[vbcol=seagreen]
same[vbcol=seagreen]
correct
>
|||If you run:
sp_removedbreplication 'dbname'
go
exec sp_dboption 'dbname','published',false
go
exec sp_dboption 'dbname','merge publish',false
go
this should do it for you.
Regards,
Paul Ibison

Error 3724: Cannot Drop Database

Hello All,
I am trying to delete couple of database in SQL 2000, SP3 and getting this
error:
Error: 3724: Cannot drop database because it is being used for replication.
There are no publications or subscriptions for the databases either. I did
also run one remove publication procedure but that did not help either.
Is there anyway I can delete these databases? Will appreciate all help.
Thanks and Regards
Fakhruddin Zavery
Sr. Systems Analyst / Programmer
CATS Tanzania Ltd.
NIC Life House 4th Floor
P. O. Box 2569, Dar es Salaam, Tanzania
Tel. +255-22 2137915, 2112631
Fax +255-22 2113033, 2112916
Mob +255 744 277452
website: http://www.catsgroup.com
----
--
The Irony of Life is that, no one gets out of it Alive
----
--Heck... the easiest way is to just shut down SQL and rename the files. It
will come up as suspect then you can delete them. Not the correct way thoug
h.
Jeff|||I tried that as well Jeff, it came up as suspect but when I try to delete it
still gives me the same error.
I even tried issuing the command DROP database from master but the same
error coems up.
"Jeff Duncan" <anonymous@.discussions.microsoft.com> wrote in message
news:B12D8244-922B-4153-9F2A-FE4ACE793D12@.microsoft.com...
> Heck... the easiest way is to just shut down SQL and rename the files.
It will come up as suspect then you can delete them. Not the correct way
though.
> Jeff|||Can't you just detach the database and delete the files?
"Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
news:uykRwvGKEHA.1392@.TK2MSFTNGP09.phx.gbl...
> I tried that as well Jeff, it came up as suspect but when I try to delete
it
> still gives me the same error.
> I even tried issuing the command DROP database from master but the same
> error coems up.
>
> "Jeff Duncan" <anonymous@.discussions.microsoft.com> wrote in message
> news:B12D8244-922B-4153-9F2A-FE4ACE793D12@.microsoft.com...
> It will come up as suspect then you can delete them. Not the correct way
> though.
>|||If I try to detach it says cannot be detached because it is being used in
replication.
"Jo Segers" <segers_jo@.hotmail.com> wrote in message
news:#qaFC0GKEHA.3292@.TK2MSFTNGP11.phx.gbl...
> Can't you just detach the database and delete the files?
> "Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
> news:uykRwvGKEHA.1392@.TK2MSFTNGP09.phx.gbl...
delete[vbcol=seagreen]
> it
files.[vbcol=seagreen]
way[vbcol=seagreen]
>|||Is it not possible to disable replication? (I don't use replication so I
have no experience with it.)
From the BOL:
To disable replication using the SQL Server Enterprise Manager
1.. Expand a server group, and then expand the Distributor (the server
that contains the distribution database).
2.. Right-click the Replication folder, and then click Disable Publishing.
3.. Complete the steps in the Disable Publishing and Distribution Wizard.
"Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
news:eulw24GKEHA.1388@.TK2MSFTNGP09.phx.gbl...
> If I try to detach it says cannot be detached because it is being used in
> replication.
> "Jo Segers" <segers_jo@.hotmail.com> wrote in message
> news:#qaFC0GKEHA.3292@.TK2MSFTNGP11.phx.gbl...
> delete
same[vbcol=seagreen]
> files.
> way
>|||If you post this in the replication group, I'm sure they will point you to t
he stored procedures you need to
call to make SQL Server forget about the replication.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> wrote in message
news:eulw24GKEHA.1388@.TK2MSFTNGP09.phx.gbl...
> If I try to detach it says cannot be detached because it is being used in
> replication.
> "Jo Segers" <segers_jo@.hotmail.com> wrote in message
> news:#qaFC0GKEHA.3292@.TK2MSFTNGP11.phx.gbl...
> delete
> files.
> way
>|||Jo been down that route as well but no luck, actually I had 3 databases to
delete all similar and perfoming same actions as this one, 2 of them I could
take them offline and delete after removing publications etc but this one I
can not delete for some funny reason.
"Jo Segers" <segers_jo@.hotmail.com> wrote in message
news:e716g#GKEHA.556@.tk2msftngp13.phx.gbl...
> Is it not possible to disable replication? (I don't use replication so I
> have no experience with it.)
> From the BOL:
> To disable replication using the SQL Server Enterprise Manager
> 1.. Expand a server group, and then expand the Distributor (the server
> that contains the distribution database).
>
> 2.. Right-click the Replication folder, and then click Disable
Publishing.
>
> 3.. Complete the steps in the Disable Publishing and Distribution
Wizard.
> "Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> schreef in bericht
> news:eulw24GKEHA.1388@.TK2MSFTNGP09.phx.gbl...
in[vbcol=seagreen]
> same
correct[vbcol=seagreen]
>|||Thanks Tibor, will try and do that.
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:#VwLgAHKEHA.2024@.TK2MSFTNGP11.phx.gbl...
> If you post this in the replication group, I'm sure they will point you to
the stored procedures you need to
> call to make SQL Server forget about the replication.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
>
> "Fakhruddin Zavery" <fakhru.zavery@.cats-net.com> wrote in message
> news:eulw24GKEHA.1388@.TK2MSFTNGP09.phx.gbl...
in[vbcol=seagreen]
same[vbcol=seagreen]
correct[vbcol=seagreen]
>|||If you run:
sp_removedbreplication 'dbname'
go
exec sp_dboption 'dbname','published',false
go
exec sp_dboption 'dbname','merge publish',false
go
this should do it for you.
Regards,
Paul Ibison

error 3624 severity 20 SQL server was stopped often

hi~~
anyone met this error message
server is SQL2000(sp3)
below is the error log
---
spid66 Using 'dbghelp.dll' version '4.0.5'...
spid66 Stack Signature for the dump is 0x50347D98
spid66 SQL Server assertion : file : <recbase.cpp>,line=1378 ...
spid66 Using 'dbghelp.dll' version '4.0.5'...
spid66 SQL Server assertion: file: <umsio.cpp>,line=117 ...
spid66 Stack Signature for the dump is 0x57421D8E
Using 'dbghelp.dll' version '4.0.5'...
spid119 error: 3624, severity 20, state: 1.
spid66 SQL Server assertion file: <umsio.cpp>,line=563 ...
---
help me~~~~These types of problems are most often bugs in SQL Server. If you are up on service pack and didn't
find anything in KB about your problems you should open a case with MS Support.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"changsoon" <pcs73@.chol.com> wrote in message news:OrsfPMOrDHA.920@.TK2MSFTNGP10.phx.gbl...
> hi~~
> anyone met this error message
> server is SQL2000(sp3)
> below is the error log
> ---
> spid66 Using 'dbghelp.dll' version '4.0.5'...
> spid66 Stack Signature for the dump is 0x50347D98
> spid66 SQL Server assertion : file : <recbase.cpp>,line=1378 ...
> spid66 Using 'dbghelp.dll' version '4.0.5'...
> spid66 SQL Server assertion: file: <umsio.cpp>,line=117 ...
> spid66 Stack Signature for the dump is 0x57421D8E
> Using 'dbghelp.dll' version '4.0.5'...
> spid119 error: 3624, severity 20, state: 1.
> spid66 SQL Server assertion file: <umsio.cpp>,line=563 ...
> ---
> help me~~~~
>

Sunday, February 19, 2012

Error 22022: SQLServerAgent Error

Would anyone know why sql server agent fails to send e-mail. We are using
outlook 2000 cleint on sql 2000 server with window 2000 sp3. The exchange
server is 5.5.
We are able to correct the problem by stopping and restaring the sql agent
and it would work for a little while then stops.
JamalI had a simelar problem. Have you completely removed
Exchange from the server?
Also I had to install Windows server 2000 SP4 and the
latest SQL2k SP
>--Original Message--
>Would anyone know why sql server agent fails to send e-
mail. We are using
>outlook 2000 cleint on sql 2000 server with window 2000
sp3. The exchange
>server is 5.5.
>We are able to correct the problem by stopping and
restaring the sql agent
>and it would work for a little while then stops.
>
>Jamal
>
>.
>|||Further to my earlier reply, i only had the problem with
the standard edition of SQL2k...
>--Original Message--
>Would anyone know why sql server agent fails to send e-
mail. We are using
>outlook 2000 cleint on sql 2000 server with window 2000
sp3. The exchange
>server is 5.5.
>We are able to correct the problem by stopping and
restaring the sql agent
>and it would work for a little while then stops.
>
>Jamal
>
>.
>

Friday, February 17, 2012

Error 22002

Hi!
This is my first time in this fourm!

I've got SQL Server Standrad Edition version 8.00.760 (SP3) on Windows 2K. I'm logged in with my domain account, which is member of sysadmin

I get
"Autostart server agent" but following error appearred:
"Error 22002: Reg Create key ex() returened error 5:Access is denied"

when I check for Autostart MSDTC in SQL Server properties.

Why? Any ideas?

Thanks for all helpWhat accounts (including their permissions) are being used for the mssqlserver, agent and dtc services ?|||Originally posted by rnealejr
What accounts (including their permissions) are being used for the mssqlserver, agent and dtc services ?

Mssqlserver service and agent have the same local admin account.|||What about dtc ? Also, when you say local administrator account, do you mean .\Administrator ? Have you rebooted/restarted all the services ?|||Originally posted by rnealejr
What about dtc ? Also, when you say local administrator account, do you mean .\Administrator ? Have you rebooted/restarted all the services ?

Yes, they are .\Administrator. I don't know which dtc account use. I donot know where to look for this account! I 'm rather new at this job!|||Look for the distributed transaction coordinator service.|||Originally posted by rnealejr
Look for the distributed transaction coordinator service.
Local system account
Allow service to interact with desktop|||Originally posted by rnealejr
Look for the distributed transaction coordinator service.
I succeded starting this servicve automaticlly in Contral Panel, Services.

Thanks for your time and help!

Wednesday, February 15, 2012

Error 195 from withing Ent Mgr

From SQL 2000 Ent Ed. sp3
When I try to view permissions via the enterrpise mgr for any object from
any database on this server I receive the following error:
<title>= Microsoft SQL-DMO (ODBC SQLState: 42000)
<msg>= Error 195: 'schema_name' is not a recognized function name.
Research I googled relates to mal-formed queries or 3rd party software as
the cause. Any ideas...?
Thanks in advance,
ScottOne more thing...
I just found out that MS Operations Management Agent was installed (w/out my
knowledge). Could this be the cause?
"Scott O'Donnell" wrote:
> From SQL 2000 Ent Ed. sp3
> When I try to view permissions via the enterrpise mgr for any object from
> any database on this server I receive the following error:
> <title>= Microsoft SQL-DMO (ODBC SQLState: 42000)
> <msg>= Error 195: 'schema_name' is not a recognized function name.
> Research I googled relates to mal-formed queries or 3rd party software as
> the cause. Any ideas...?
> Thanks in advance,
> Scott|||i have this problem:
when i execute this
SqlCommand mCmd = new SqlCommand( sQry,mConn );
mCmd.CommandType = System.Data.CommandType.Text;
mCmd.ExecuteNonQuery();
where sQry = "UPDATE StoreOperation SET Data=DateAdd(HH,FreqOra,DataAdd(
d,FreqData,Data )) WHERE IDStoreOperation=1"
i have this error message
"DateAdd is not a recognized function name"
in C++ the same sQry work fine. in .NET no.

Error 1934 Severity 16 State 1

SQL Server 2000 Standard Sp3. on Windows 2003
What is Error 1934.
I can't find documentaiton on this anywhere. There's only one article in KB
in relation to merge replication. And other stuff on the web about ANSI
settings and indexed views (which I'm not using).
I get these errors in different contexts.
Here's one:
Profiler screenshot
http://www.vinnychi.com/vince/images/sql.jpg
This is a stored procedure that SQL Agent is running from a job. When i run
it this way, I get the 1934 error. If I run it from Query Analyzer I get no
error, and it runs to completion.
SP:
CREATE PROCEDURE FFIMPORT_DAILY_CLEANUP
AS
exec UTIL_DEFRAG
RETURN
========
UTIL_DEFRAG is:
CREATE procedure UTIL_DEFRAG
AS
TRUNCATE TABLE BLCSO
TRUNCATE TABLE IBFF_BOL_Temp
TRUNCATE TABLE IBFF_Container_Temp
TRUNCATE TABLE IBFFContainerImportPhase2
TRUNCATE TABLE JobOrderDoor_Temp
TRUNCATE TABLE JobOrderDoorContainer_Temp
TRUNCATE TABLE JobOrderITM_Temp
TRUNCATE TABLE JobOrderITMContainer_Temp
TRUNCATE TABLE JTQ510
TRUNCATE TABLE JTQ520
TRUNCATE TABLE NAIBFF
TRUNCATE TABLE NAIBFF_DeleteTable
TRUNCATE TABLE SpecialRequirementMilestone
declare @.tablename nvarchar(125)
declare cur CURSOR
FORWARD_ONLY
STATIC
READ_ONLY
FOR SELECT name FROM sysobjects where xtype = N'u' and type = N'u'
and name not like 'conflict_%' and name not like 'dt%' and name not like
'MS%' and name not like 'sys%'
order by name
open cur
fetch next from cur
into @.tablename
while @.@.fetch_status = 0
BEGIN
PRINT 'REINDEXING ' + @.tablename
dbcc dbreindex (@.tablename)
fetch next from cur
into @.tablename
END
CLOSE cur
DEALLOCATE curI wouldn't rule out the ANSI settings. This issue has come
up before. SQL Agent and Query Analyzer use different set
options/ansi settings when they connect to SQL Server.
Whatever the set option errors you are seeing as missing,
add to your job script and make sure they are just before
the calling of your stored procedures.
-Sue
On Sat, 22 Jan 2005 09:44:42 -0600, "Vince P"
<remove@.pacelviATspeakeasy.net> wrote:

>SQL Server 2000 Standard Sp3. on Windows 2003
>What is Error 1934.
>I can't find documentaiton on this anywhere. There's only one article in K
B
>in relation to merge replication. And other stuff on the web about ANSI
>settings and indexed views (which I'm not using).
>I get these errors in different contexts.
>Here's one:
>Profiler screenshot
>http://www.vinnychi.com/vince/images/sql.jpg
>This is a stored procedure that SQL Agent is running from a job. When i ru
n
>it this way, I get the 1934 error. If I run it from Query Analyzer I get no
>error, and it runs to completion.
>SP:
>CREATE PROCEDURE FFIMPORT_DAILY_CLEANUP
>AS
>exec UTIL_DEFRAG
> RETURN
>
>========
>UTIL_DEFRAG is:
>CREATE procedure UTIL_DEFRAG
>AS
>TRUNCATE TABLE BLCSO
>TRUNCATE TABLE IBFF_BOL_Temp
>TRUNCATE TABLE IBFF_Container_Temp
>TRUNCATE TABLE IBFFContainerImportPhase2
>TRUNCATE TABLE JobOrderDoor_Temp
>TRUNCATE TABLE JobOrderDoorContainer_Temp
>TRUNCATE TABLE JobOrderITM_Temp
>TRUNCATE TABLE JobOrderITMContainer_Temp
>TRUNCATE TABLE JTQ510
>TRUNCATE TABLE JTQ520
>TRUNCATE TABLE NAIBFF
>TRUNCATE TABLE NAIBFF_DeleteTable
>TRUNCATE TABLE SpecialRequirementMilestone
>declare @.tablename nvarchar(125)
>declare cur CURSOR
>FORWARD_ONLY
>STATIC
>READ_ONLY
>FOR SELECT name FROM sysobjects where xtype = N'u' and type = N'u'
>and name not like 'conflict_%' and name not like 'dt%' and name not like
>'MS%' and name not like 'sys%'
>order by name
>open cur
>fetch next from cur
>into @.tablename
>while @.@.fetch_status = 0
>BEGIN
>PRINT 'REINDEXING ' + @.tablename
>dbcc dbreindex (@.tablename)
>fetch next from cur
>into @.tablename
>END
>CLOSE cur
>DEALLOCATE cur
>|||It ended up being
Set ArithAbort ON
needed to be set.
How come this error isn't documented anywhere "official?
I'm also gettinga lot of error 1933 and 1935
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:a76bv0dvssmog6r5j5af4unelg5q7bfn7q@.
4ax.com...
>I wouldn't rule out the ANSI settings. This issue has come
> up before. SQL Agent and Query Analyzer use different set
> options/ansi settings when they connect to SQL Server.
> Whatever the set option errors you are seeing as missing,
> add to your job script and make sure they are just before
> the calling of your stored procedures.
> -Sue
> On Sat, 22 Jan 2005 09:44:42 -0600, "Vince P"
> <remove@.pacelviATspeakeasy.net> wrote:
>
>|||Based on your errors, I would guess that you have computed
columns. ANSI settings and computed columns is addressed in
books online under the topics:
SET Options That Affect Results
Creating Indexes on Computed Columns
The Arithabort setting is addressed in the books online
topic Create Index
The article does mention the following:
It is strongly recommended that the ARITHABORT user option
be set server-wide to ON as soon as the first indexed view
or index on a computed column is created in any database on
the server.
You can also find related information in the following:
http://www.microsoft.com/sql/techin...pment/july2.asp
-Sue
On Wed, 26 Jan 2005 02:49:32 -0600, "Vince P"
<remove@.pacelviATspeakeasy.net> wrote:

>It ended up being
>Set ArithAbort ON
>needed to be set.
>
>How come this error isn't documented anywhere "official?
>I'm also gettinga lot of error 1933 and 1935
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:a76bv0dvssmog6r5j5af4unelg5q7bfn7q@.
4ax.com...
>|||Sue: Thanks for your leads. A large part of the problem was ArithAbort.
Thank you very much.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:4c6fv0l327hq7dm20npbajt0vv2nsf10u1@.
4ax.com...
> Based on your errors, I would guess that you have computed
> columns. ANSI settings and computed columns is addressed in
> books online under the topics:
> SET Options That Affect Results
> Creating Indexes on Computed Columns
> The Arithabort setting is addressed in the books online
> topic Create Index
> The article does mention the following:
> It is strongly recommended that the ARITHABORT user option
> be set server-wide to ON as soon as the first indexed view
> or index on a computed column is created in any database on
> the server.
> You can also find related information in the following:
> http://www.microsoft.com/sql/techin...pment/july2.asp
> -Sue
> On Wed, 26 Jan 2005 02:49:32 -0600, "Vince P"
> <remove@.pacelviATspeakeasy.net> wrote:
>
>

Error 1934 Severity 16 State 1

SQL Server 2000 Standard Sp3. on Windows 2003
What is Error 1934.
I can't find documentaiton on this anywhere. There's only one article in KB
in relation to merge replication. And other stuff on the web about ANSI
settings and indexed views (which I'm not using).
I get these errors in different contexts.
Here's one:
Profiler screenshot
http://www.vinnychi.com/vince/images/sql.jpg
This is a stored procedure that SQL Agent is running from a job. When i run
it this way, I get the 1934 error. If I run it from Query Analyzer I get no
error, and it runs to completion.
SP:
CREATE PROCEDURE FFIMPORT_DAILY_CLEANUP
AS
exec UTIL_DEFRAG
RETURN
========
UTIL_DEFRAG is:
CREATE procedure UTIL_DEFRAG
AS
TRUNCATE TABLE BLCSO
TRUNCATE TABLE IBFF_BOL_Temp
TRUNCATE TABLE IBFF_Container_Temp
TRUNCATE TABLE IBFFContainerImportPhase2
TRUNCATE TABLE JobOrderDoor_Temp
TRUNCATE TABLE JobOrderDoorContainer_Temp
TRUNCATE TABLE JobOrderITM_Temp
TRUNCATE TABLE JobOrderITMContainer_Temp
TRUNCATE TABLE JTQ510
TRUNCATE TABLE JTQ520
TRUNCATE TABLE NAIBFF
TRUNCATE TABLE NAIBFF_DeleteTable
TRUNCATE TABLE SpecialRequirementMilestone
declare @.tablename nvarchar(125)
declare cur CURSOR
FORWARD_ONLY
STATIC
READ_ONLY
FOR SELECT name FROM sysobjects where xtype = N'u' and type = N'u'
and name not like 'conflict_%' and name not like 'dt%' and name not like
'MS%' and name not like 'sys%'
order by name
open cur
fetch next from cur
into @.tablename
while @.@.fetch_status = 0
BEGIN
PRINT 'REINDEXING ' + @.tablename
dbcc dbreindex (@.tablename)
fetch next from cur
into @.tablename
END
CLOSE cur
DEALLOCATE cur
I wouldn't rule out the ANSI settings. This issue has come
up before. SQL Agent and Query Analyzer use different set
options/ansi settings when they connect to SQL Server.
Whatever the set option errors you are seeing as missing,
add to your job script and make sure they are just before
the calling of your stored procedures.
-Sue
On Sat, 22 Jan 2005 09:44:42 -0600, "Vince P"
<remove@.pacelviATspeakeasy.net> wrote:

>SQL Server 2000 Standard Sp3. on Windows 2003
>What is Error 1934.
>I can't find documentaiton on this anywhere. There's only one article in KB
>in relation to merge replication. And other stuff on the web about ANSI
>settings and indexed views (which I'm not using).
>I get these errors in different contexts.
>Here's one:
>Profiler screenshot
>http://www.vinnychi.com/vince/images/sql.jpg
>This is a stored procedure that SQL Agent is running from a job. When i run
>it this way, I get the 1934 error. If I run it from Query Analyzer I get no
>error, and it runs to completion.
>SP:
>CREATE PROCEDURE FFIMPORT_DAILY_CLEANUP
>AS
>exec UTIL_DEFRAG
> RETURN
>
>========
>UTIL_DEFRAG is:
>CREATE procedure UTIL_DEFRAG
>AS
>TRUNCATE TABLE BLCSO
>TRUNCATE TABLE IBFF_BOL_Temp
>TRUNCATE TABLE IBFF_Container_Temp
>TRUNCATE TABLE IBFFContainerImportPhase2
>TRUNCATE TABLE JobOrderDoor_Temp
>TRUNCATE TABLE JobOrderDoorContainer_Temp
>TRUNCATE TABLE JobOrderITM_Temp
>TRUNCATE TABLE JobOrderITMContainer_Temp
>TRUNCATE TABLE JTQ510
>TRUNCATE TABLE JTQ520
>TRUNCATE TABLE NAIBFF
>TRUNCATE TABLE NAIBFF_DeleteTable
>TRUNCATE TABLE SpecialRequirementMilestone
>declare @.tablename nvarchar(125)
>declare cur CURSOR
>FORWARD_ONLY
>STATIC
>READ_ONLY
>FOR SELECT name FROM sysobjects where xtype = N'u' and type = N'u'
>and name not like 'conflict_%' and name not like 'dt%' and name not like
>'MS%' and name not like 'sys%'
>order by name
>open cur
>fetch next from cur
>into @.tablename
>while @.@.fetch_status = 0
>BEGIN
>PRINT 'REINDEXING ' + @.tablename
>dbcc dbreindex (@.tablename)
>fetch next from cur
>into @.tablename
>END
>CLOSE cur
>DEALLOCATE cur
>
|||It ended up being
Set ArithAbort ON
needed to be set.
How come this error isn't documented anywhere "official?
I'm also gettinga lot of error 1933 and 1935
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:a76bv0dvssmog6r5j5af4unelg5q7bfn7q@.4ax.com...
>I wouldn't rule out the ANSI settings. This issue has come
> up before. SQL Agent and Query Analyzer use different set
> options/ansi settings when they connect to SQL Server.
> Whatever the set option errors you are seeing as missing,
> add to your job script and make sure they are just before
> the calling of your stored procedures.
> -Sue
> On Sat, 22 Jan 2005 09:44:42 -0600, "Vince P"
> <remove@.pacelviATspeakeasy.net> wrote:
>
|||Based on your errors, I would guess that you have computed
columns. ANSI settings and computed columns is addressed in
books online under the topics:
SET Options That Affect Results
Creating Indexes on Computed Columns
The Arithabort setting is addressed in the books online
topic Create Index
The article does mention the following:
It is strongly recommended that the ARITHABORT user option
be set server-wide to ON as soon as the first indexed view
or index on a computed column is created in any database on
the server.
You can also find related information in the following:
http://www.microsoft.com/sql/techinf...ment/july2.asp
-Sue
On Wed, 26 Jan 2005 02:49:32 -0600, "Vince P"
<remove@.pacelviATspeakeasy.net> wrote:

>It ended up being
>Set ArithAbort ON
>needed to be set.
>
>How come this error isn't documented anywhere "official?
>I'm also gettinga lot of error 1933 and 1935
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:a76bv0dvssmog6r5j5af4unelg5q7bfn7q@.4ax.com.. .
>
|||Sue: Thanks for your leads. A large part of the problem was ArithAbort.
Thank you very much.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:4c6fv0l327hq7dm20npbajt0vv2nsf10u1@.4ax.com...
> Based on your errors, I would guess that you have computed
> columns. ANSI settings and computed columns is addressed in
> books online under the topics:
> SET Options That Affect Results
> Creating Indexes on Computed Columns
> The Arithabort setting is addressed in the books online
> topic Create Index
> The article does mention the following:
> It is strongly recommended that the ARITHABORT user option
> be set server-wide to ON as soon as the first indexed view
> or index on a computed column is created in any database on
> the server.
> You can also find related information in the following:
> http://www.microsoft.com/sql/techinf...ment/july2.asp
> -Sue
> On Wed, 26 Jan 2005 02:49:32 -0600, "Vince P"
> <remove@.pacelviATspeakeasy.net> wrote:
>

Error 1934 Severity 16 State 1

SQL Server 2000 Standard Sp3. on Windows 2003
What is Error 1934.
I can't find documentaiton on this anywhere. There's only one article in KB
in relation to merge replication. And other stuff on the web about ANSI
settings and indexed views (which I'm not using).
I get these errors in different contexts.
Here's one:
Profiler screenshot
http://www.vinnychi.com/vince/images/sql.jpg
This is a stored procedure that SQL Agent is running from a job. When i run
it this way, I get the 1934 error. If I run it from Query Analyzer I get no
error, and it runs to completion.
SP:
CREATE PROCEDURE FFIMPORT_DAILY_CLEANUP
AS
exec UTIL_DEFRAG
RETURN
======== UTIL_DEFRAG is:
CREATE procedure UTIL_DEFRAG
AS
TRUNCATE TABLE BLCSO
TRUNCATE TABLE IBFF_BOL_Temp
TRUNCATE TABLE IBFF_Container_Temp
TRUNCATE TABLE IBFFContainerImportPhase2
TRUNCATE TABLE JobOrderDoor_Temp
TRUNCATE TABLE JobOrderDoorContainer_Temp
TRUNCATE TABLE JobOrderITM_Temp
TRUNCATE TABLE JobOrderITMContainer_Temp
TRUNCATE TABLE JTQ510
TRUNCATE TABLE JTQ520
TRUNCATE TABLE NAIBFF
TRUNCATE TABLE NAIBFF_DeleteTable
TRUNCATE TABLE SpecialRequirementMilestone
declare @.tablename nvarchar(125)
declare cur CURSOR
FORWARD_ONLY
STATIC
READ_ONLY
FOR SELECT name FROM sysobjects where xtype = N'u' and type = N'u'
and name not like 'conflict_%' and name not like 'dt%' and name not like
'MS%' and name not like 'sys%'
order by name
open cur
fetch next from cur
into @.tablename
while @.@.fetch_status = 0
BEGIN
PRINT 'REINDEXING ' + @.tablename
dbcc dbreindex (@.tablename)
fetch next from cur
into @.tablename
END
CLOSE cur
DEALLOCATE curI wouldn't rule out the ANSI settings. This issue has come
up before. SQL Agent and Query Analyzer use different set
options/ansi settings when they connect to SQL Server.
Whatever the set option errors you are seeing as missing,
add to your job script and make sure they are just before
the calling of your stored procedures.
-Sue
On Sat, 22 Jan 2005 09:44:42 -0600, "Vince P"
<remove@.pacelviATspeakeasy.net> wrote:
>SQL Server 2000 Standard Sp3. on Windows 2003
>What is Error 1934.
>I can't find documentaiton on this anywhere. There's only one article in KB
>in relation to merge replication. And other stuff on the web about ANSI
>settings and indexed views (which I'm not using).
>I get these errors in different contexts.
>Here's one:
>Profiler screenshot
>http://www.vinnychi.com/vince/images/sql.jpg
>This is a stored procedure that SQL Agent is running from a job. When i run
>it this way, I get the 1934 error. If I run it from Query Analyzer I get no
>error, and it runs to completion.
>SP:
>CREATE PROCEDURE FFIMPORT_DAILY_CLEANUP
>AS
>exec UTIL_DEFRAG
> RETURN
>
>========>UTIL_DEFRAG is:
>CREATE procedure UTIL_DEFRAG
>AS
>TRUNCATE TABLE BLCSO
>TRUNCATE TABLE IBFF_BOL_Temp
>TRUNCATE TABLE IBFF_Container_Temp
>TRUNCATE TABLE IBFFContainerImportPhase2
>TRUNCATE TABLE JobOrderDoor_Temp
>TRUNCATE TABLE JobOrderDoorContainer_Temp
>TRUNCATE TABLE JobOrderITM_Temp
>TRUNCATE TABLE JobOrderITMContainer_Temp
>TRUNCATE TABLE JTQ510
>TRUNCATE TABLE JTQ520
>TRUNCATE TABLE NAIBFF
>TRUNCATE TABLE NAIBFF_DeleteTable
>TRUNCATE TABLE SpecialRequirementMilestone
>declare @.tablename nvarchar(125)
>declare cur CURSOR
>FORWARD_ONLY
>STATIC
>READ_ONLY
>FOR SELECT name FROM sysobjects where xtype = N'u' and type = N'u'
>and name not like 'conflict_%' and name not like 'dt%' and name not like
>'MS%' and name not like 'sys%'
>order by name
>open cur
>fetch next from cur
>into @.tablename
>while @.@.fetch_status = 0
>BEGIN
>PRINT 'REINDEXING ' + @.tablename
>dbcc dbreindex (@.tablename)
>fetch next from cur
>into @.tablename
>END
>CLOSE cur
>DEALLOCATE cur
>|||It ended up being
Set ArithAbort ON
needed to be set.
How come this error isn't documented anywhere "official?
I'm also gettinga lot of error 1933 and 1935
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:a76bv0dvssmog6r5j5af4unelg5q7bfn7q@.4ax.com...
>I wouldn't rule out the ANSI settings. This issue has come
> up before. SQL Agent and Query Analyzer use different set
> options/ansi settings when they connect to SQL Server.
> Whatever the set option errors you are seeing as missing,
> add to your job script and make sure they are just before
> the calling of your stored procedures.
> -Sue
> On Sat, 22 Jan 2005 09:44:42 -0600, "Vince P"
> <remove@.pacelviATspeakeasy.net> wrote:
>>SQL Server 2000 Standard Sp3. on Windows 2003
>>What is Error 1934.
>>I can't find documentaiton on this anywhere. There's only one article in
>>KB
>>in relation to merge replication. And other stuff on the web about ANSI
>>settings and indexed views (which I'm not using).
>>I get these errors in different contexts.
>>Here's one:
>>Profiler screenshot
>>http://www.vinnychi.com/vince/images/sql.jpg
>>This is a stored procedure that SQL Agent is running from a job. When i
>>run
>>it this way, I get the 1934 error. If I run it from Query Analyzer I get
>>no
>>error, and it runs to completion.
>>SP:
>>CREATE PROCEDURE FFIMPORT_DAILY_CLEANUP
>>AS
>>exec UTIL_DEFRAG
>> RETURN
>>
>>========>>UTIL_DEFRAG is:
>>CREATE procedure UTIL_DEFRAG
>>AS
>>TRUNCATE TABLE BLCSO
>>TRUNCATE TABLE IBFF_BOL_Temp
>>TRUNCATE TABLE IBFF_Container_Temp
>>TRUNCATE TABLE IBFFContainerImportPhase2
>>TRUNCATE TABLE JobOrderDoor_Temp
>>TRUNCATE TABLE JobOrderDoorContainer_Temp
>>TRUNCATE TABLE JobOrderITM_Temp
>>TRUNCATE TABLE JobOrderITMContainer_Temp
>>TRUNCATE TABLE JTQ510
>>TRUNCATE TABLE JTQ520
>>TRUNCATE TABLE NAIBFF
>>TRUNCATE TABLE NAIBFF_DeleteTable
>>TRUNCATE TABLE SpecialRequirementMilestone
>>declare @.tablename nvarchar(125)
>>declare cur CURSOR
>>FORWARD_ONLY
>>STATIC
>>READ_ONLY
>>FOR SELECT name FROM sysobjects where xtype = N'u' and type = N'u'
>>and name not like 'conflict_%' and name not like 'dt%' and name not like
>>'MS%' and name not like 'sys%'
>>order by name
>>open cur
>>fetch next from cur
>>into @.tablename
>>while @.@.fetch_status = 0
>>BEGIN
>>PRINT 'REINDEXING ' + @.tablename
>>dbcc dbreindex (@.tablename)
>>fetch next from cur
>>into @.tablename
>>END
>>CLOSE cur
>>DEALLOCATE cur
>|||Based on your errors, I would guess that you have computed
columns. ANSI settings and computed columns is addressed in
books online under the topics:
SET Options That Affect Results
Creating Indexes on Computed Columns
The Arithabort setting is addressed in the books online
topic Create Index
The article does mention the following:
It is strongly recommended that the ARITHABORT user option
be set server-wide to ON as soon as the first indexed view
or index on a computed column is created in any database on
the server.
You can also find related information in the following:
http://www.microsoft.com/sql/techinfo/tips/development/july2.asp
-Sue
On Wed, 26 Jan 2005 02:49:32 -0600, "Vince P"
<remove@.pacelviATspeakeasy.net> wrote:
>It ended up being
>Set ArithAbort ON
>needed to be set.
>
>How come this error isn't documented anywhere "official?
>I'm also gettinga lot of error 1933 and 1935
>
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:a76bv0dvssmog6r5j5af4unelg5q7bfn7q@.4ax.com...
>>I wouldn't rule out the ANSI settings. This issue has come
>> up before. SQL Agent and Query Analyzer use different set
>> options/ansi settings when they connect to SQL Server.
>> Whatever the set option errors you are seeing as missing,
>> add to your job script and make sure they are just before
>> the calling of your stored procedures.
>> -Sue
>> On Sat, 22 Jan 2005 09:44:42 -0600, "Vince P"
>> <remove@.pacelviATspeakeasy.net> wrote:
>>SQL Server 2000 Standard Sp3. on Windows 2003
>>What is Error 1934.
>>I can't find documentaiton on this anywhere. There's only one article in
>>KB
>>in relation to merge replication. And other stuff on the web about ANSI
>>settings and indexed views (which I'm not using).
>>I get these errors in different contexts.
>>Here's one:
>>Profiler screenshot
>>http://www.vinnychi.com/vince/images/sql.jpg
>>This is a stored procedure that SQL Agent is running from a job. When i
>>run
>>it this way, I get the 1934 error. If I run it from Query Analyzer I get
>>no
>>error, and it runs to completion.
>>SP:
>>CREATE PROCEDURE FFIMPORT_DAILY_CLEANUP
>>AS
>>exec UTIL_DEFRAG
>> RETURN
>>
>>========>>UTIL_DEFRAG is:
>>CREATE procedure UTIL_DEFRAG
>>AS
>>TRUNCATE TABLE BLCSO
>>TRUNCATE TABLE IBFF_BOL_Temp
>>TRUNCATE TABLE IBFF_Container_Temp
>>TRUNCATE TABLE IBFFContainerImportPhase2
>>TRUNCATE TABLE JobOrderDoor_Temp
>>TRUNCATE TABLE JobOrderDoorContainer_Temp
>>TRUNCATE TABLE JobOrderITM_Temp
>>TRUNCATE TABLE JobOrderITMContainer_Temp
>>TRUNCATE TABLE JTQ510
>>TRUNCATE TABLE JTQ520
>>TRUNCATE TABLE NAIBFF
>>TRUNCATE TABLE NAIBFF_DeleteTable
>>TRUNCATE TABLE SpecialRequirementMilestone
>>declare @.tablename nvarchar(125)
>>declare cur CURSOR
>>FORWARD_ONLY
>>STATIC
>>READ_ONLY
>>FOR SELECT name FROM sysobjects where xtype = N'u' and type = N'u'
>>and name not like 'conflict_%' and name not like 'dt%' and name not like
>>'MS%' and name not like 'sys%'
>>order by name
>>open cur
>>fetch next from cur
>>into @.tablename
>>while @.@.fetch_status = 0
>>BEGIN
>>PRINT 'REINDEXING ' + @.tablename
>>dbcc dbreindex (@.tablename)
>>fetch next from cur
>>into @.tablename
>>END
>>CLOSE cur
>>DEALLOCATE cur
>>
>|||Sue: Thanks for your leads. A large part of the problem was ArithAbort.
Thank you very much.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:4c6fv0l327hq7dm20npbajt0vv2nsf10u1@.4ax.com...
> Based on your errors, I would guess that you have computed
> columns. ANSI settings and computed columns is addressed in
> books online under the topics:
> SET Options That Affect Results
> Creating Indexes on Computed Columns
> The Arithabort setting is addressed in the books online
> topic Create Index
> The article does mention the following:
> It is strongly recommended that the ARITHABORT user option
> be set server-wide to ON as soon as the first indexed view
> or index on a computed column is created in any database on
> the server.
> You can also find related information in the following:
> http://www.microsoft.com/sql/techinfo/tips/development/july2.asp
> -Sue
> On Wed, 26 Jan 2005 02:49:32 -0600, "Vince P"
> <remove@.pacelviATspeakeasy.net> wrote:
>>It ended up being
>>Set ArithAbort ON
>>needed to be set.
>>
>>How come this error isn't documented anywhere "official?
>>I'm also gettinga lot of error 1933 and 1935
>>
>>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>>news:a76bv0dvssmog6r5j5af4unelg5q7bfn7q@.4ax.com...
>>I wouldn't rule out the ANSI settings. This issue has come
>> up before. SQL Agent and Query Analyzer use different set
>> options/ansi settings when they connect to SQL Server.
>> Whatever the set option errors you are seeing as missing,
>> add to your job script and make sure they are just before
>> the calling of your stored procedures.
>> -Sue
>> On Sat, 22 Jan 2005 09:44:42 -0600, "Vince P"
>> <remove@.pacelviATspeakeasy.net> wrote:
>>SQL Server 2000 Standard Sp3. on Windows 2003
>>What is Error 1934.
>>I can't find documentaiton on this anywhere. There's only one article
>>in
>>KB
>>in relation to merge replication. And other stuff on the web about ANSI
>>settings and indexed views (which I'm not using).
>>I get these errors in different contexts.
>>Here's one:
>>Profiler screenshot
>>http://www.vinnychi.com/vince/images/sql.jpg
>>This is a stored procedure that SQL Agent is running from a job. When i
>>run
>>it this way, I get the 1934 error. If I run it from Query Analyzer I get
>>no
>>error, and it runs to completion.
>>SP:
>>CREATE PROCEDURE FFIMPORT_DAILY_CLEANUP
>>AS
>>exec UTIL_DEFRAG
>> RETURN
>>
>>========>>UTIL_DEFRAG is:
>>CREATE procedure UTIL_DEFRAG
>>AS
>>TRUNCATE TABLE BLCSO
>>TRUNCATE TABLE IBFF_BOL_Temp
>>TRUNCATE TABLE IBFF_Container_Temp
>>TRUNCATE TABLE IBFFContainerImportPhase2
>>TRUNCATE TABLE JobOrderDoor_Temp
>>TRUNCATE TABLE JobOrderDoorContainer_Temp
>>TRUNCATE TABLE JobOrderITM_Temp
>>TRUNCATE TABLE JobOrderITMContainer_Temp
>>TRUNCATE TABLE JTQ510
>>TRUNCATE TABLE JTQ520
>>TRUNCATE TABLE NAIBFF
>>TRUNCATE TABLE NAIBFF_DeleteTable
>>TRUNCATE TABLE SpecialRequirementMilestone
>>declare @.tablename nvarchar(125)
>>declare cur CURSOR
>>FORWARD_ONLY
>>STATIC
>>READ_ONLY
>>FOR SELECT name FROM sysobjects where xtype = N'u' and type = N'u'
>>and name not like 'conflict_%' and name not like 'dt%' and name not like
>>'MS%' and name not like 'sys%'
>>order by name
>>open cur
>>fetch next from cur
>>into @.tablename
>>while @.@.fetch_status = 0
>>BEGIN
>>PRINT 'REINDEXING ' + @.tablename
>>dbcc dbreindex (@.tablename)
>>fetch next from cur
>>into @.tablename
>>END
>>CLOSE cur
>>DEALLOCATE cur
>>
>