OK this is a new error on me.
I have a SQL server 2000 on Windows Server 2003.
I have setup a Maint plan that backs up the user and system databases
and the transaction Logs on my user databases.
Does optimises and integrity checks on those databases as well.
I am not attempting to repair any minor problems.
I am not performing integrity checks before backing up the database
and transaction logs.
All of the databases that I am doing a transaction log backup on have
recovery mode of full.
When the jobs run they fail instantly with error code 22029.
Sqlmaint.exe failed to run. This was working up until the end of the
day on the Thursday before Good Friday. (last week) The transaction
log backup ran fine at 4:00 PM the same job failed at 8:00 PM. No
changes were made to the server during that time.
Another issue that started at the same time. I have a web page used to
grab data from a text file export and pull it into an AS400. I use
this server to house the DTS packages and stored procedures that the
process needs. I suddenly quit working when the jobs quit running.
We are in a mixed enviroment with most clients on AD and this server
and most others still in a NT 4 domain. We have been like this for at
least 3 months and everything has worked fine. I setup the various
users and systems the way the need to be to work.
Originally the SQL Agent was running as a generic NT 4 Domain user with
local administrator rights to the local box and server role of system
administrator. The MSSQLSERVER and DTC services were running as the
built in system account.
Everything was happy then it broke.
When I reboot the server the jobs and the website work fine. Then
after a period of time that I have not figured out yet, but more than
15 minutes and less than 2 hours. Everything quits working.
I have changed all the services to run as a domain admin with SQL
system adminsitrator server role. Still same thing.
I have changed all the services to run as the built in system account.
Still same thing.
I run the sqlmaint from command line with the switches that I am using
in the maint jobs and it runs fine.
I have run dbcc checkdb on all the databases and they are fine.
The DTS packages and the stored procedures used by the website run fine
from with in Query analyzer.
Any help you can provide would be greatly appreciated.A guess: Try disabling the IPSec service. I've seen some similar behavior
when this service was misconfigured.
Also I would make sure the system is configure to log all security failures
and take a good look at the Security event log for any additional clues.|||Kevin,
Thanks for the reply. I already had the security set to log failure
and it is showing nothing but success audits.
I stopped the IPSec service and I still couldn't run the job. Do i
need to restart the server after making that change?
Kevin Joyner
Kevin English wrote:
> A guess: Try disabling the IPSec service. I've seen some similar behavio
r
> when this service was misconfigured.
> Also I would make sure the system is configure to log all security failure
s
> and take a good look at the Security event log for any additional clues.
Showing posts with label system. Show all posts
Showing posts with label system. Show all posts
Monday, March 26, 2012
problem with SQL Agent
OK this is a new error on me.
I have a SQL server 2000 on Windows Server 2003.
I have setup a Maint plan that backs up the user and system databases
and the transaction Logs on my user databases.
Does optimises and integrity checks on those databases as well.
I am not attempting to repair any minor problems.
I am not performing integrity checks before backing up the database
and transaction logs.
All of the databases that I am doing a transaction log backup on have
recovery mode of full.
When the jobs run they fail instantly with error code 22029.
Sqlmaint.exe failed to run. This was working up until the end of the
day on the Thursday before Good Friday. (last week) The transaction
log backup ran fine at 4:00 PM the same job failed at 8:00 PM. No
changes were made to the server during that time.
Another issue that started at the same time. I have a web page used to
grab data from a text file export and pull it into an AS400. I use
this server to house the DTS packages and stored procedures that the
process needs. I suddenly quit working when the jobs quit running.
We are in a mixed enviroment with most clients on AD and this server
and most others still in a NT 4 domain. We have been like this for at
least 3 months and everything has worked fine. I setup the various
users and systems the way the need to be to work.
Originally the SQL Agent was running as a generic NT 4 Domain user with
local administrator rights to the local box and server role of system
administrator. The MSSQLSERVER and DTC services were running as the
built in system account.
Everything was happy then it broke.
When I reboot the server the jobs and the website work fine. Then
after a period of time that I have not figured out yet, but more than
15 minutes and less than 2 hours. Everything quits working.
I have changed all the services to run as a domain admin with SQL
system adminsitrator server role. Still same thing.
I have changed all the services to run as the built in system account.
Still same thing.
I run the sqlmaint from command line with the switches that I am using
in the maint jobs and it runs fine.
I have run dbcc checkdb on all the databases and they are fine.
The DTS packages and the stored procedures used by the website run fine
from with in Query analyzer.
Any help you can provide would be greatly appreciated.A guess: Try disabling the IPSec service. I've seen some similar behavior
when this service was misconfigured.
Also I would make sure the system is configure to log all security failures
and take a good look at the Security event log for any additional clues.|||Kevin,
Thanks for the reply. I already had the security set to log failure
and it is showing nothing but success audits.
I stopped the IPSec service and I still couldn't run the job. Do i
need to restart the server after making that change?
Kevin Joyner
Kevin English wrote:
> A guess: Try disabling the IPSec service. I've seen some similar behavior
> when this service was misconfigured.
> Also I would make sure the system is configure to log all security failures
> and take a good look at the Security event log for any additional clues.
I have a SQL server 2000 on Windows Server 2003.
I have setup a Maint plan that backs up the user and system databases
and the transaction Logs on my user databases.
Does optimises and integrity checks on those databases as well.
I am not attempting to repair any minor problems.
I am not performing integrity checks before backing up the database
and transaction logs.
All of the databases that I am doing a transaction log backup on have
recovery mode of full.
When the jobs run they fail instantly with error code 22029.
Sqlmaint.exe failed to run. This was working up until the end of the
day on the Thursday before Good Friday. (last week) The transaction
log backup ran fine at 4:00 PM the same job failed at 8:00 PM. No
changes were made to the server during that time.
Another issue that started at the same time. I have a web page used to
grab data from a text file export and pull it into an AS400. I use
this server to house the DTS packages and stored procedures that the
process needs. I suddenly quit working when the jobs quit running.
We are in a mixed enviroment with most clients on AD and this server
and most others still in a NT 4 domain. We have been like this for at
least 3 months and everything has worked fine. I setup the various
users and systems the way the need to be to work.
Originally the SQL Agent was running as a generic NT 4 Domain user with
local administrator rights to the local box and server role of system
administrator. The MSSQLSERVER and DTC services were running as the
built in system account.
Everything was happy then it broke.
When I reboot the server the jobs and the website work fine. Then
after a period of time that I have not figured out yet, but more than
15 minutes and less than 2 hours. Everything quits working.
I have changed all the services to run as a domain admin with SQL
system adminsitrator server role. Still same thing.
I have changed all the services to run as the built in system account.
Still same thing.
I run the sqlmaint from command line with the switches that I am using
in the maint jobs and it runs fine.
I have run dbcc checkdb on all the databases and they are fine.
The DTS packages and the stored procedures used by the website run fine
from with in Query analyzer.
Any help you can provide would be greatly appreciated.A guess: Try disabling the IPSec service. I've seen some similar behavior
when this service was misconfigured.
Also I would make sure the system is configure to log all security failures
and take a good look at the Security event log for any additional clues.|||Kevin,
Thanks for the reply. I already had the security set to log failure
and it is showing nothing but success audits.
I stopped the IPSec service and I still couldn't run the job. Do i
need to restart the server after making that change?
Kevin Joyner
Kevin English wrote:
> A guess: Try disabling the IPSec service. I've seen some similar behavior
> when this service was misconfigured.
> Also I would make sure the system is configure to log all security failures
> and take a good look at the Security event log for any additional clues.
Friday, March 23, 2012
Problem with sp_attach_db
Hi!
We have a problem with a database asignation. When we try to make an attach
(sp_attach_db) the system display an error:
Server: Msg 3624, Level 20, State 1, Line 1
Location: recovery.c: 2657
Expression: seenCkptEnd
SPID: 10
Process ID: 560
Connection Broken
We work with SQL Server 7.0 SP2
What can we do?
Thank you in advance.
Did you detach the database first? Does it come from the same SQL Server version?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Israel" <i.rodriguez@.promis.net> wrote in message news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>
|||I do not think that at least half the groups you have included on your To:
line are relevant
It looks as though you may have a problem with the files which you are
trying to attach.
How did you shutdown the database for which these files originally were?
Was it cleanly?
What was your syntax?
The files were not in use by a database were they?
It may be that you need to contact the boys and girls in MS PSS and they may
be able to help you here.
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.Konesans.com
"Israel" <i.rodriguez@.promis.net> wrote in message
news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an
> attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>
We have a problem with a database asignation. When we try to make an attach
(sp_attach_db) the system display an error:
Server: Msg 3624, Level 20, State 1, Line 1
Location: recovery.c: 2657
Expression: seenCkptEnd
SPID: 10
Process ID: 560
Connection Broken
We work with SQL Server 7.0 SP2
What can we do?
Thank you in advance.
Did you detach the database first? Does it come from the same SQL Server version?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Israel" <i.rodriguez@.promis.net> wrote in message news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>
|||I do not think that at least half the groups you have included on your To:
line are relevant
It looks as though you may have a problem with the files which you are
trying to attach.
How did you shutdown the database for which these files originally were?
Was it cleanly?
What was your syntax?
The files were not in use by a database were they?
It may be that you need to contact the boys and girls in MS PSS and they may
be able to help you here.
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.Konesans.com
"Israel" <i.rodriguez@.promis.net> wrote in message
news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an
> attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>
Problem with sp_attach_db
Hi!
We have a problem with a database asignation. When we try to make an attach
(sp_attach_db) the system display an error:
Server: Msg 3624, Level 20, State 1, Line 1
Location: recovery.c: 2657
Expression: seenCkptEnd
SPID: 10
Process ID: 560
Connection Broken
We work with SQL Server 7.0 SP2
What can we do?
Thank you in advance.
Did you detach the database first? Does it come from the same SQL Server version?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Israel" <i.rodriguez@.promis.net> wrote in message news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>
|||I do not think that at least half the groups you have included on your To:
line are relevant
It looks as though you may have a problem with the files which you are
trying to attach.
How did you shutdown the database for which these files originally were?
Was it cleanly?
What was your syntax?
The files were not in use by a database were they?
It may be that you need to contact the boys and girls in MS PSS and they may
be able to help you here.
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.Konesans.com
"Israel" <i.rodriguez@.promis.net> wrote in message
news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an
> attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>
We have a problem with a database asignation. When we try to make an attach
(sp_attach_db) the system display an error:
Server: Msg 3624, Level 20, State 1, Line 1
Location: recovery.c: 2657
Expression: seenCkptEnd
SPID: 10
Process ID: 560
Connection Broken
We work with SQL Server 7.0 SP2
What can we do?
Thank you in advance.
Did you detach the database first? Does it come from the same SQL Server version?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Israel" <i.rodriguez@.promis.net> wrote in message news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>
|||I do not think that at least half the groups you have included on your To:
line are relevant
It looks as though you may have a problem with the files which you are
trying to attach.
How did you shutdown the database for which these files originally were?
Was it cleanly?
What was your syntax?
The files were not in use by a database were they?
It may be that you need to contact the boys and girls in MS PSS and they may
be able to help you here.
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.Konesans.com
"Israel" <i.rodriguez@.promis.net> wrote in message
news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an
> attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>
Problem with sp_attach_db
Hi!
We have a problem with a database asignation. When we try to make an attach
(sp_attach_db) the system display an error:
Server: Msg 3624, Level 20, State 1, Line 1
Location: recovery.c: 2657
Expression: seenCkptEnd
SPID: 10
Process ID: 560
Connection Broken
We work with SQL Server 7.0 SP2
What can we do?
Thank you in advance.
Did you detach the database first? Does it come from the same SQL Server version?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Israel" <i.rodriguez@.promis.net> wrote in message news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>
|||I do not think that at least half the groups you have included on your To:
line are relevant
It looks as though you may have a problem with the files which you are
trying to attach.
How did you shutdown the database for which these files originally were?
Was it cleanly?
What was your syntax?
The files were not in use by a database were they?
It may be that you need to contact the boys and girls in MS PSS and they may
be able to help you here.
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.Konesans.com
"Israel" <i.rodriguez@.promis.net> wrote in message
news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an
> attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>
We have a problem with a database asignation. When we try to make an attach
(sp_attach_db) the system display an error:
Server: Msg 3624, Level 20, State 1, Line 1
Location: recovery.c: 2657
Expression: seenCkptEnd
SPID: 10
Process ID: 560
Connection Broken
We work with SQL Server 7.0 SP2
What can we do?
Thank you in advance.
Did you detach the database first? Does it come from the same SQL Server version?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Israel" <i.rodriguez@.promis.net> wrote in message news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>
|||I do not think that at least half the groups you have included on your To:
line are relevant
It looks as though you may have a problem with the files which you are
trying to attach.
How did you shutdown the database for which these files originally were?
Was it cleanly?
What was your syntax?
The files were not in use by a database were they?
It may be that you need to contact the boys and girls in MS PSS and they may
be able to help you here.
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.Konesans.com
"Israel" <i.rodriguez@.promis.net> wrote in message
news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an
> attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>
Problem with sp_attach_db
Hi!
We have a problem with a database asignation. When we try to make an attach
(sp_attach_db) the system display an error:
Server: Msg 3624, Level 20, State 1, Line 1
Location: recovery.c: 2657
Expression: seenCkptEnd
SPID: 10
Process ID: 560
Connection Broken
We work with SQL Server 7.0 SP2
What can we do?
Thank you in advance.Did you detach the database first? Does it come from the same SQL Server version?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Israel" <i.rodriguez@.promis.net> wrote in message news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>|||I do not think that at least half the groups you have included on your To:
line are relevant
It looks as though you may have a problem with the files which you are
trying to attach.
How did you shutdown the database for which these files originally were?
Was it cleanly?
What was your syntax?
The files were not in use by a database were they?
It may be that you need to contact the boys and girls in MS PSS and they may
be able to help you here.
--
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.Konesans.com
"Israel" <i.rodriguez@.promis.net> wrote in message
news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an
> attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>sql
We have a problem with a database asignation. When we try to make an attach
(sp_attach_db) the system display an error:
Server: Msg 3624, Level 20, State 1, Line 1
Location: recovery.c: 2657
Expression: seenCkptEnd
SPID: 10
Process ID: 560
Connection Broken
We work with SQL Server 7.0 SP2
What can we do?
Thank you in advance.Did you detach the database first? Does it come from the same SQL Server version?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Israel" <i.rodriguez@.promis.net> wrote in message news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>|||I do not think that at least half the groups you have included on your To:
line are relevant
It looks as though you may have a problem with the files which you are
trying to attach.
How did you shutdown the database for which these files originally were?
Was it cleanly?
What was your syntax?
The files were not in use by a database were they?
It may be that you need to contact the boys and girls in MS PSS and they may
be able to help you here.
--
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.Konesans.com
"Israel" <i.rodriguez@.promis.net> wrote in message
news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an
> attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>sql
Problem with sp_attach_db
Hi!
We have a problem with a database asignation. When we try to make an attach
(sp_attach_db) the system display an error:
Server: Msg 3624, Level 20, State 1, Line 1
Location: recovery.c: 2657
Expression: seenCkptEnd
SPID: 10
Process ID: 560
Connection Broken
We work with SQL Server 7.0 SP2
What can we do?
Thank you in advance.Did you detach the database first? Does it come from the same SQL Server ver
sion?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Israel" <i.rodriguez@.promis.net> wrote in message news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl
..
> Hi!
> We have a problem with a database asignation. When we try to make an attac
h
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>|||I do not think that at least half the groups you have included on your To:
line are relevant
It looks as though you may have a problem with the files which you are
trying to attach.
How did you shutdown the database for which these files originally were?
Was it cleanly?
What was your syntax?
The files were not in use by a database were they?
It may be that you need to contact the boys and girls in MS PSS and they may
be able to help you here.
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.Konesans.com
"Israel" <i.rodriguez@.promis.net> wrote in message
news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an
> attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>
We have a problem with a database asignation. When we try to make an attach
(sp_attach_db) the system display an error:
Server: Msg 3624, Level 20, State 1, Line 1
Location: recovery.c: 2657
Expression: seenCkptEnd
SPID: 10
Process ID: 560
Connection Broken
We work with SQL Server 7.0 SP2
What can we do?
Thank you in advance.Did you detach the database first? Does it come from the same SQL Server ver
sion?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Israel" <i.rodriguez@.promis.net> wrote in message news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl
..
> Hi!
> We have a problem with a database asignation. When we try to make an attac
h
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>|||I do not think that at least half the groups you have included on your To:
line are relevant
It looks as though you may have a problem with the files which you are
trying to attach.
How did you shutdown the database for which these files originally were?
Was it cleanly?
What was your syntax?
The files were not in use by a database were they?
It may be that you need to contact the boys and girls in MS PSS and they may
be able to help you here.
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.Konesans.com
"Israel" <i.rodriguez@.promis.net> wrote in message
news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an
> attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>
Problem with sp_attach_db
Hi!
We have a problem with a database asignation. When we try to make an attach
(sp_attach_db) the system display an error:
Server: Msg 3624, Level 20, State 1, Line 1
Location: recovery.c: 2657
Expression: seenCkptEnd
SPID: 10
Process ID: 560
Connection Broken
We work with SQL Server 7.0 SP2
What can we do?
Thank you in advance.
Did you detach the database first? Does it come from the same SQL Server version?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Israel" <i.rodriguez@.promis.net> wrote in message news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>
|||I do not think that at least half the groups you have included on your To:
line are relevant
It looks as though you may have a problem with the files which you are
trying to attach.
How did you shutdown the database for which these files originally were?
Was it cleanly?
What was your syntax?
The files were not in use by a database were they?
It may be that you need to contact the boys and girls in MS PSS and they may
be able to help you here.
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.Konesans.com
"Israel" <i.rodriguez@.promis.net> wrote in message
news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an
> attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>
We have a problem with a database asignation. When we try to make an attach
(sp_attach_db) the system display an error:
Server: Msg 3624, Level 20, State 1, Line 1
Location: recovery.c: 2657
Expression: seenCkptEnd
SPID: 10
Process ID: 560
Connection Broken
We work with SQL Server 7.0 SP2
What can we do?
Thank you in advance.
Did you detach the database first? Does it come from the same SQL Server version?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Israel" <i.rodriguez@.promis.net> wrote in message news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>
|||I do not think that at least half the groups you have included on your To:
line are relevant
It looks as though you may have a problem with the files which you are
trying to attach.
How did you shutdown the database for which these files originally were?
Was it cleanly?
What was your syntax?
The files were not in use by a database were they?
It may be that you need to contact the boys and girls in MS PSS and they may
be able to help you here.
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.Konesans.com
"Israel" <i.rodriguez@.promis.net> wrote in message
news:OYJEL87rEHA.212@.TK2MSFTNGP10.phx.gbl...
> Hi!
> We have a problem with a database asignation. When we try to make an
> attach
> (sp_attach_db) the system display an error:
> Server: Msg 3624, Level 20, State 1, Line 1
> Location: recovery.c: 2657
> Expression: seenCkptEnd
> SPID: 10
> Process ID: 560
> Connection Broken
> We work with SQL Server 7.0 SP2
> What can we do?
> Thank you in advance.
>
Wednesday, March 21, 2012
Problem with source from Books Online - Application.LoadPackage
I'm trying to execute a package in the file system from an c# assembly. In BOL there is the following sample code available:
ms-help://MS.VSCC.v80/MS.VSIPCC.v80/MS.SQLSVR.v9.en/dtsref9mref/html/M_Microsoft_SqlServer_Dts_Runtime_Application_LoadPackage_1_cfc592c3.htm
Application.LoadPackage Method (String, IDTSEvents)
class ApplicationTests
{
static void Main(string[] args)
{
// The variable pkg points to the location of the
// ExecuteProcess package sample installed with
// the SSIS samples.
string pkg = @."C:\Program Files\Microsoft SQL Server\90\Samples\Integration Services\Package Samples\ExecuteProcess Sample\ExecuteProcess\UsingExecuteProcess.dtsx";
Application app = new Application();
Package p = app.LoadPackage(pkg, null);
// Now that the package is loaded, we can query on
// its properties.
int n = p.Configurations.Count;
DtsProperty p2 = p.Properties["VersionGUID"];
DTSProtectionLevel pl = p.ProtectionLevel;
Console.WriteLine("Number of configurations = " + n);
Console.WriteLine("VersionGUID = " + p2);
Console.WriteLine("ProtectionLevel = " + pl);
}
}
I added the reference to "Microsoft.SQLServer.DTSRuntimeWrap" and declared it by
using Microsoft.SqlServer.Dts.Runtime.Wrapper;
No I'm not able to compile because app.LoadPackage(pkg, null); needs an additional IDTSEvents90. After changing the row to
Package p = app.LoadPackage(pkg, true, null);
I'm getting the following errors:
Error 1 Cannot implicitly convert type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPackage90' to 'Microsoft.SqlServer.Dts.Runtime.Wrapper.Package'. An explicit conversion exists (are you missing a cast?)
Error 2 The type or namespace name 'DtsProperty' could not be found (are you missing a using directive or an assembly reference?)
Error 3 'Microsoft.SqlServer.Dts.Runtime.Wrapper.Package' does not contain a definition for 'Properties'
Can someone please give me an example how to start the Package now in the latest code syntax and set the values of a variable from outside?
I am using the following versions
Microsoft Visual Studio 2005
Version 8.0.50727.26 (RTM.050727-2600)
Microsoft .NET Framework
Version 2.0.50727
SQL Server Integration Services
Microsoft SQL Server Integration Services Designer
Version 9.00.1314.00
Best regards,
Dirk
.Wrapper assembly and namespace contain COM interop declarations - i.e. if you want to work with unmanaged object model directly. It is usually more convinient to work with managed object model built on top of it.sql
Problem with simplified chinese
I have a 3 layer system, SQL Server 2000 database, COM+ dll's (VC++ 6) and
ASP frontend, this system has been in production for quite some time using
english, spanish and portuguese versions. Now I've been asked to test the
system to function with Simplified chinese. The development of the system
was outsourced and we don't have communication with the company (some sort
of legal problems i think).
Now, I've been reviewing the code and recompiled one of the core DLL's for
unicode support with no problems, I've tested the database (SQL Server 2000)
inserting Simplified Chinese characters and the DB supports it fine (the DB
fields are NVARCHAR), in the ASP frontend, the retrievel process (calling
the COM+ DLL functions) works fine displaying this data I inserted directly
in the DB.
However, when I try inserting this data through the ASP frontend I'm getting
errors regarding the length of the strings, I'm testing the data insertion
in a field limited to 100 characters, the data I'm testing are 23 Simplified
Chinese symbols or characters and when I insert them directly in the DB
there is no problem, the DB correctly interprets the string as 23 characters
long, but when I test the length of the same string on the ASP page it says
its 183 characters long, so I'm guessing the ASP code is doing some kind of
implicit conversion, I already tried setting the asp session codepage to
65001 for unicode support with the same outcome. Any ideas or tips?
Sorry for the long post, I would reaaly appreciate any kind of help.
David
David A. Caballero J. wrote:
> Sorry for the long post, I would reaaly appreciate any kind of help.
> David
I have a PDF we devised for clients who want to run our ASP package in
Chinese (unicode) - I think it deals with some of the issues you've come
across. Let me know if I can send it to your hotmail address (I'm
assuming it's genuine) and I'll send it over.
The reason you are seeing more characters is because the chars are
displayed in web page HTML source as numerical codes made up of ASCII chars.
captain_flackTONYBLAIRFROMOFFICE@.hotmail.com
(remove Tony Blair from office to contact me)
ASP frontend, this system has been in production for quite some time using
english, spanish and portuguese versions. Now I've been asked to test the
system to function with Simplified chinese. The development of the system
was outsourced and we don't have communication with the company (some sort
of legal problems i think).
Now, I've been reviewing the code and recompiled one of the core DLL's for
unicode support with no problems, I've tested the database (SQL Server 2000)
inserting Simplified Chinese characters and the DB supports it fine (the DB
fields are NVARCHAR), in the ASP frontend, the retrievel process (calling
the COM+ DLL functions) works fine displaying this data I inserted directly
in the DB.
However, when I try inserting this data through the ASP frontend I'm getting
errors regarding the length of the strings, I'm testing the data insertion
in a field limited to 100 characters, the data I'm testing are 23 Simplified
Chinese symbols or characters and when I insert them directly in the DB
there is no problem, the DB correctly interprets the string as 23 characters
long, but when I test the length of the same string on the ASP page it says
its 183 characters long, so I'm guessing the ASP code is doing some kind of
implicit conversion, I already tried setting the asp session codepage to
65001 for unicode support with the same outcome. Any ideas or tips?
Sorry for the long post, I would reaaly appreciate any kind of help.
David
David A. Caballero J. wrote:
> Sorry for the long post, I would reaaly appreciate any kind of help.
> David
I have a PDF we devised for clients who want to run our ASP package in
Chinese (unicode) - I think it deals with some of the issues you've come
across. Let me know if I can send it to your hotmail address (I'm
assuming it's genuine) and I'll send it over.
The reason you are seeing more characters is because the chars are
displayed in web page HTML source as numerical codes made up of ASCII chars.
captain_flackTONYBLAIRFROMOFFICE@.hotmail.com
(remove Tony Blair from office to contact me)
Monday, March 12, 2012
Problem with Scheduled Jobs
I have a scheduled T-SQL job that I need to run as a different user than
system. I am running into two problems. 1, no matter who the owner is, the
job still runs as system (the SQL Server Agent User). The 2nd part is that
the "run as" is grayed out, so I can't attempt to set the step to run as a
different user.
How can I solve the problem, without changing the user that hte SQL Server
Agent runs as?
Thanks.A job will run under the security context of the SQL Agent
service if the job is owned by a sysadmin. If it's not owned
by a sysadmin, it will run under the security context of the
proxy account. So those are your options.
-Sue
On Tue, 13 Sep 2005 09:12:08 -0400, "Kevin Antel"
<kevina@.cqlcorp.com> wrote:
>I have a scheduled T-SQL job that I need to run as a different user than
>system. I am running into two problems. 1, no matter who the owner is, the
>job still runs as system (the SQL Server Agent User). The 2nd part is that
>the "run as" is grayed out, so I can't attempt to set the step to run as a
>different user.
>How can I solve the problem, without changing the user that hte SQL Server
>Agent runs as?
>Thanks.
>
system. I am running into two problems. 1, no matter who the owner is, the
job still runs as system (the SQL Server Agent User). The 2nd part is that
the "run as" is grayed out, so I can't attempt to set the step to run as a
different user.
How can I solve the problem, without changing the user that hte SQL Server
Agent runs as?
Thanks.A job will run under the security context of the SQL Agent
service if the job is owned by a sysadmin. If it's not owned
by a sysadmin, it will run under the security context of the
proxy account. So those are your options.
-Sue
On Tue, 13 Sep 2005 09:12:08 -0400, "Kevin Antel"
<kevina@.cqlcorp.com> wrote:
>I have a scheduled T-SQL job that I need to run as a different user than
>system. I am running into two problems. 1, no matter who the owner is, the
>job still runs as system (the SQL Server Agent User). The 2nd part is that
>the "run as" is grayed out, so I can't attempt to set the step to run as a
>different user.
>How can I solve the problem, without changing the user that hte SQL Server
>Agent runs as?
>Thanks.
>
Wednesday, March 7, 2012
Problem with referencing System.Data.SqlServerCE.dll
Hello
I have referrenced System.Data.SqlServerCE.dll to my web project in order to create a .sdf file. I haven't wrote any code,just referenced it. When I build the project I get this error:
Error 2 'System.Data.SqlServerCe, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' cannot be loaded.
It sounds like you dont have the client dlls installed.
If you already installed the SDK you need to install it from C:\Program Files\Microsoft SQL Server Compact Edition\v3.1\SDK\bin\Desktop
if you dont have the SDK, I suggest you to install it, another option would be to download directly another redist.
|||I have had problems too, related to incorrect referencing. There is a version in the public assemblies folder which causes this error.
C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\PublicAssemblies\System.Data.SqlServerCe.dll
This specific file/version is needed by the data designer in visual studio so dont delete it, just change any references in your projects, for System.Data.SqlServerCe.dll, to point to the correct file.
Usually
C:\Program Files\Microsoft SQL Server Compact Edition\v3.1\System.Data.SqlServerCe.dll
OR
C:\Program Files\Microsoft SQL Server Compact Edition\v3.5\System.Data.SqlServerCe.dll
Cheers
Anton
Subscribe to:
Posts (Atom)