cannot write to sql 2000 database after about 2 hours uptime

Hi
I have a sql 2000 sp3 database running on SBS 2003 that seems to
ignore any writes after about 2 hours of it being up. It works fine after i
reboot the server or restart the sql service, but after a couple hours it
will not edit the database again. If i restart the service, it works fine
again. Also, i was looking at the sql logs and they are odd. it says
'starting up database {my database name}' about 20 times in a row when the
database is started, then says 'Configuration option 'show advanced options'
changed from 1 to 1. Run the RECONFIGURE statement to install' and then
gives an error 15457. Please help me fix my database.
Thanks in advance.
Leszek
Hi
Error 15457 is just an informational one. Ig gets generated the Enterprise
Manager and has nothing to do with the Db issue.
If there are no other errors in you event log, it means that SQL is Ok and
your application is the problem.
You may want to make sure that your DB is not set as 'Auto Close' as this
affects performance.
Regards
Mike
"Leszek" wrote:

> Hi
>
> I have a sql 2000 sp3 database running on SBS 2003 that seems to
> ignore any writes after about 2 hours of it being up. It works fine after i
> reboot the server or restart the sql service, but after a couple hours it
> will not edit the database again. If i restart the service, it works fine
> again. Also, i was looking at the sql logs and they are odd. it says
> 'starting up database {my database name}' about 20 times in a row when the
> database is started, then says 'Configuration option 'show advanced options'
> changed from 1 to 1. Run the RECONFIGURE statement to install' and then
> gives an error 15457. Please help me fix my database.
> Thanks in advance.
> Leszek
>
>
|||Hi
Db is not set as 'Auto Close'. I have noticed that problem occured when is
more then 100 process in sql .
Regards
Leszek
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:4F13D7AF-1570-47AC-85B5-0515AD58D2AA@.microsoft.com...[vbcol=seagreen]
> Hi
> Error 15457 is just an informational one. Ig gets generated the Enterprise
> Manager and has nothing to do with the Db issue.
> If there are no other errors in you event log, it means that SQL is Ok and
> your application is the problem.
> You may want to make sure that your DB is not set as 'Auto Close' as this
> affects performance.
> Regards
> Mike
> "Leszek" wrote:
after i[vbcol=seagreen]
it[vbcol=seagreen]
fine[vbcol=seagreen]
the[vbcol=seagreen]
options'[vbcol=seagreen]
then[vbcol=seagreen]
|||The problem here is not going to be an easy one to fix.
There are a couple of things you can look at however to
get a bit closer to the proble.
Firstly have you run the performance monitor to see what
is happening to your server i.e. Disk, Memory and the like.
Secondly you may want to set up a trace to see what
commands are being sent to the server.
Finally another thing you can do is send me a copy of your
database script, I don't need the table definitions, sp,
views or functions, just the configuration options when
you create the database, for security purposes leave the
create database statement in, but change the db name. I
will have a quick look at it and see if I can spot
anything odd.
Finally what is your server specification i.e. ram, hard
disk space ect.
My email if you need it is
peter.nolan@.REMOVETHISpinnacle.co.uk, nb its my work one.
Peter
"The length of this document defends it well against the
risk of its being read."
Winston Churchill

>--Original Message--
>Hi
>Db is not set as 'Auto Close'. I have noticed that
problem occured when is
>more then 100 process in sql .
>Regards
>Leszek
>
>"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in
message[vbcol=seagreen]
>news:4F13D7AF-1570-47AC-85B5-0515AD58D2AA@.microsoft.com...
generated the Enterprise[vbcol=seagreen]
that SQL is Ok and[vbcol=seagreen]
as 'Auto Close' as this[vbcol=seagreen]
2003 that seems to[vbcol=seagreen]
It works fine[vbcol=seagreen]
>after i
after a couple hours[vbcol=seagreen]
>it
service, it works[vbcol=seagreen]
>fine
are odd. it says[vbcol=seagreen]
times in a row when[vbcol=seagreen]
>the
option 'show advanced[vbcol=seagreen]
>options'
to install' and
>then
>
>.
>
|||Aplication works since few monts on other server and there everything is
fine.
Regarding performance monitor. When system works fine and i try to open site
with many difficult query , procesor usage show about 50 % and it take 10
sec - site is loaded. If it doesn't work procesor usage is always about 1%
but i can't load the site.
Sql Profile show that query is sent to server.
Leszek
"Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:158001c4a221$b242cfc0$a301280a@.phx.gbl...[vbcol=seagreen]
> The problem here is not going to be an easy one to fix.
> There are a couple of things you can look at however to
> get a bit closer to the proble.
> Firstly have you run the performance monitor to see what
> is happening to your server i.e. Disk, Memory and the like.
> Secondly you may want to set up a trace to see what
> commands are being sent to the server.
> Finally another thing you can do is send me a copy of your
> database script, I don't need the table definitions, sp,
> views or functions, just the configuration options when
> you create the database, for security purposes leave the
> create database statement in, but change the db name. I
> will have a quick look at it and see if I can spot
> anything odd.
> Finally what is your server specification i.e. ram, hard
> disk space ect.
> My email if you need it is
> peter.nolan@.REMOVETHISpinnacle.co.uk, nb its my work one.
> Peter
> "The length of this document defends it well against the
> risk of its being read."
> Winston Churchill
>
> problem occured when is
> message
> generated the Enterprise
> that SQL is Ok and
> as 'Auto Close' as this
> 2003 that seems to
> It works fine
> after a couple hours
> service, it works
> are odd. it says
> times in a row when
> option 'show advanced
> to install' and
|||Hi Leszek,
Have you used the enterprise manager to see if anything is locking a table
and preventing the updates? Perhaps a certain function or piece of code is
being executed after about 2 hours and that may look like the database won't
accept updates.
Wayne
"Leszek" <aaa@.addressnotexists.com> wrote in message
news:Odc7a3goEHA.2380@.TK2MSFTNGP14.phx.gbl...
> Hi
>
> I have a sql 2000 sp3 database running on SBS 2003 that seems to
> ignore any writes after about 2 hours of it being up. It works fine after
> i
> reboot the server or restart the sql service, but after a couple hours it
> will not edit the database again. If i restart the service, it works fine
> again. Also, i was looking at the sql logs and they are odd. it says
> 'starting up database {my database name}' about 20 times in a row when the
> database is started, then says 'Configuration option 'show advanced
> options'
> changed from 1 to 1. Run the RECONFIGURE statement to install' and then
> gives an error 15457. Please help me fix my database.
> Thanks in advance.
> Leszek
>

cannot write to sql 2000 database after about 2 hours uptime

Hi
I have a sql 2000 sp3 database running on SBS 2003 that seems to
ignore any writes after about 2 hours of it being up. It works fine after i
reboot the server or restart the sql service, but after a couple hours it
will not edit the database again. If i restart the service, it works fine
again. Also, i was looking at the sql logs and they are odd. it says
'starting up database {my database name}' about 20 times in a row when the
database is started, then says 'Configuration option 'show advanced options'
changed from 1 to 1. Run the RECONFIGURE statement to install' and then
gives an error 15457. Please help me fix my database.
Thanks in advance.
LeszekHi
Error 15457 is just an informational one. Ig gets generated the Enterprise
Manager and has nothing to do with the Db issue.
If there are no other errors in you event log, it means that SQL is Ok and
your application is the problem.
You may want to make sure that your DB is not set as 'Auto Close' as this
affects performance.
Regards
Mike
"Leszek" wrote:
> Hi
>
> I have a sql 2000 sp3 database running on SBS 2003 that seems to
> ignore any writes after about 2 hours of it being up. It works fine after i
> reboot the server or restart the sql service, but after a couple hours it
> will not edit the database again. If i restart the service, it works fine
> again. Also, i was looking at the sql logs and they are odd. it says
> 'starting up database {my database name}' about 20 times in a row when the
> database is started, then says 'Configuration option 'show advanced options'
> changed from 1 to 1. Run the RECONFIGURE statement to install' and then
> gives an error 15457. Please help me fix my database.
> Thanks in advance.
> Leszek
>
>|||Hi
Db is not set as 'Auto Close'. I have noticed that problem occured when is
more then 100 process in sql .
Regards
Leszek
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:4F13D7AF-1570-47AC-85B5-0515AD58D2AA@.microsoft.com...
> Hi
> Error 15457 is just an informational one. Ig gets generated the Enterprise
> Manager and has nothing to do with the Db issue.
> If there are no other errors in you event log, it means that SQL is Ok and
> your application is the problem.
> You may want to make sure that your DB is not set as 'Auto Close' as this
> affects performance.
> Regards
> Mike
> "Leszek" wrote:
> > Hi
> >
> >
> > I have a sql 2000 sp3 database running on SBS 2003 that seems to
> > ignore any writes after about 2 hours of it being up. It works fine
after i
> > reboot the server or restart the sql service, but after a couple hours
it
> > will not edit the database again. If i restart the service, it works
fine
> > again. Also, i was looking at the sql logs and they are odd. it says
> > 'starting up database {my database name}' about 20 times in a row when
the
> > database is started, then says 'Configuration option 'show advanced
options'
> > changed from 1 to 1. Run the RECONFIGURE statement to install' and
then
> > gives an error 15457. Please help me fix my database.
> >
> > Thanks in advance.
> >
> > Leszek
> >
> >
> >|||The problem here is not going to be an easy one to fix.
There are a couple of things you can look at however to
get a bit closer to the proble.
Firstly have you run the performance monitor to see what
is happening to your server i.e. Disk, Memory and the like.
Secondly you may want to set up a trace to see what
commands are being sent to the server.
Finally another thing you can do is send me a copy of your
database script, I don't need the table definitions, sp,
views or functions, just the configuration options when
you create the database, for security purposes leave the
create database statement in, but change the db name. I
will have a quick look at it and see if I can spot
anything odd.
Finally what is your server specification i.e. ram, hard
disk space ect.
My email if you need it is
peter.nolan@.REMOVETHISpinnacle.co.uk, nb its my work one.
Peter
"The length of this document defends it well against the
risk of its being read."
Winston Churchill
>--Original Message--
>Hi
>Db is not set as 'Auto Close'. I have noticed that
problem occured when is
>more then 100 process in sql .
>Regards
>Leszek
>
>"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in
message
>news:4F13D7AF-1570-47AC-85B5-0515AD58D2AA@.microsoft.com...
>> Hi
>> Error 15457 is just an informational one. Ig gets
generated the Enterprise
>> Manager and has nothing to do with the Db issue.
>> If there are no other errors in you event log, it means
that SQL is Ok and
>> your application is the problem.
>> You may want to make sure that your DB is not set
as 'Auto Close' as this
>> affects performance.
>> Regards
>> Mike
>> "Leszek" wrote:
>> > Hi
>> >
>> >
>> > I have a sql 2000 sp3 database running on SBS
2003 that seems to
>> > ignore any writes after about 2 hours of it being up.
It works fine
>after i
>> > reboot the server or restart the sql service, but
after a couple hours
>it
>> > will not edit the database again. If i restart the
service, it works
>fine
>> > again. Also, i was looking at the sql logs and they
are odd. it says
>> > 'starting up database {my database name}' about 20
times in a row when
>the
>> > database is started, then says 'Configuration
option 'show advanced
>options'
>> > changed from 1 to 1. Run the RECONFIGURE statement
to install' and
>then
>> > gives an error 15457. Please help me fix my database.
>> >
>> > Thanks in advance.
>> >
>> > Leszek
>> >
>> >
>> >
>
>.
>|||Aplication works since few monts on other server and there everything is
fine.
Regarding performance monitor. When system works fine and i try to open site
with many difficult query , procesor usage show about 50 % and it take 10
sec - site is loaded. If it doesn't work procesor usage is always about 1%
but i can't load the site.
Sql Profile show that query is sent to server.
Leszek
"Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:158001c4a221$b242cfc0$a301280a@.phx.gbl...
> The problem here is not going to be an easy one to fix.
> There are a couple of things you can look at however to
> get a bit closer to the proble.
> Firstly have you run the performance monitor to see what
> is happening to your server i.e. Disk, Memory and the like.
> Secondly you may want to set up a trace to see what
> commands are being sent to the server.
> Finally another thing you can do is send me a copy of your
> database script, I don't need the table definitions, sp,
> views or functions, just the configuration options when
> you create the database, for security purposes leave the
> create database statement in, but change the db name. I
> will have a quick look at it and see if I can spot
> anything odd.
> Finally what is your server specification i.e. ram, hard
> disk space ect.
> My email if you need it is
> peter.nolan@.REMOVETHISpinnacle.co.uk, nb its my work one.
> Peter
> "The length of this document defends it well against the
> risk of its being read."
> Winston Churchill
>
> >--Original Message--
> >Hi
> >
> >Db is not set as 'Auto Close'. I have noticed that
> problem occured when is
> >more then 100 process in sql .
> >
> >Regards
> >Leszek
> >
> >
> >"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in
> message
> >news:4F13D7AF-1570-47AC-85B5-0515AD58D2AA@.microsoft.com...
> >> Hi
> >>
> >> Error 15457 is just an informational one. Ig gets
> generated the Enterprise
> >> Manager and has nothing to do with the Db issue.
> >>
> >> If there are no other errors in you event log, it means
> that SQL is Ok and
> >> your application is the problem.
> >>
> >> You may want to make sure that your DB is not set
> as 'Auto Close' as this
> >> affects performance.
> >>
> >> Regards
> >> Mike
> >>
> >> "Leszek" wrote:
> >>
> >> > Hi
> >> >
> >> >
> >> > I have a sql 2000 sp3 database running on SBS
> 2003 that seems to
> >> > ignore any writes after about 2 hours of it being up.
> It works fine
> >after i
> >> > reboot the server or restart the sql service, but
> after a couple hours
> >it
> >> > will not edit the database again. If i restart the
> service, it works
> >fine
> >> > again. Also, i was looking at the sql logs and they
> are odd. it says
> >> > 'starting up database {my database name}' about 20
> times in a row when
> >the
> >> > database is started, then says 'Configuration
> option 'show advanced
> >options'
> >> > changed from 1 to 1. Run the RECONFIGURE statement
> to install' and
> >then
> >> > gives an error 15457. Please help me fix my database.
> >> >
> >> > Thanks in advance.
> >> >
> >> > Leszek
> >> >
> >> >
> >> >
> >
> >
> >.
> >|||Hi Leszek,
Have you used the enterprise manager to see if anything is locking a table
and preventing the updates? Perhaps a certain function or piece of code is
being executed after about 2 hours and that may look like the database won't
accept updates.
Wayne
"Leszek" <aaa@.addressnotexists.com> wrote in message
news:Odc7a3goEHA.2380@.TK2MSFTNGP14.phx.gbl...
> Hi
>
> I have a sql 2000 sp3 database running on SBS 2003 that seems to
> ignore any writes after about 2 hours of it being up. It works fine after
> i
> reboot the server or restart the sql service, but after a couple hours it
> will not edit the database again. If i restart the service, it works fine
> again. Also, i was looking at the sql logs and they are odd. it says
> 'starting up database {my database name}' about 20 times in a row when the
> database is started, then says 'Configuration option 'show advanced
> options'
> changed from 1 to 1. Run the RECONFIGURE statement to install' and then
> gives an error 15457. Please help me fix my database.
> Thanks in advance.
> Leszek
>

cannot write to column in updatable RecordSet

Hi. I receive the SQLException:

[Microsoft][SQLServer 2000 Driver for JDBC]Can not update, the specified column is not writable.

when I attempt to call updateString() on a RecordSet column. I have set the Statement object on which I execute the query to obtain the RecordSet to be scrollable and updatable.

My goal is to replace the ID value contained in a particular column of each row with a longer text string that includes the ID value. If I can't alter the column values via the RecordSet, can I write SQL as part of the query to generate the text string?

Thank you.

RajCan You write a little example: what You have and what You want...
And your table's structure... if it is possible. and sqlsrv version.|||Hi. We run SQL Server 2000. I call the code that creates the Statement, executes the ResultSet, and outputs the results in separate methods, so here I include a summary of the code.

Statement statement = connection.createStatement(ResultSet.TYPE_SCROLL_I NSENSITIVE, ResultSet.CONCUR_UPDATABLE);

...

rs = statement.executeQuery(queryString);

...

WriteEditSCRLinks(rs);

Here's the definition of WriteEditSCRLinks().

//Replaces each SCR ID with a hyperlink that opens the edit SCR page on the ID.
//Method needs to input an updatable, scrollable RecordSet.
void WriteEditSCRLinks(ResultSet rs) throws SQLException
{
String FieldName = "SCRID";

while (rs.next())
{
String IDValue = rs.getString(FieldName);

String UpdateString = "<A HREF=\"" + SiteConfigHelper.getEditSoftwareChangeRequestURL() + "?" + FieldName + "=" + IDValue + "\">" + IDValue + "</A>";

rs.updateString(FieldName, UpdateString);
}

//Need to move the cursor to the position before the first row
//so as not to break GraphingHelper methods.
rs.beforeFirst();
}

Since someone told me that the JDBC object model does not intend for me to alter the ResultSet if I shall not alter the database, I have to solve this problem in a different way anyway. However, I would appreciate knowing whether the concept of updating the ResultSet differs from the concept of writing to a column.

Thank you.

Raj

cannot write logfile Error 1059 : Circular service dependency

I have a problem that looks like it has not been discussed before in
these groups.
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on SQL,
but using the same admin domain service account) fails?
Thanks in advance for any info you might have.
On Feb 13, 6:33 pm, donn...@.fastmail.fm wrote:
> I have a problem that looks like it has not been discussed before in
> these groups.
> I have a simple SQLAgent job that runs sp_who (could be anything, but
> let's just say sp_who for this example). I have set the jobstep to
> write to an output file "T:\out.txt". If the job is owned by an
> admin, it runs fine and writes the output file. If it is owned by a
> non-admin user, it gets the following error msg:
> Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
> service dependency was specified. The step failed.
> I know about setting up the SQLAgent CMDExec proxy account, and have
> done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
> the same domain account, which is in the administrator group of the
> local server. So, I know that security is not the issue.
> When a simple job runs and writes to an output file, what service or
> service group could it be trying to start or modify? I looked through
> the list of Services, and could not find any circular dependencies.
> Is there a utility to detect this? Why would running under one
> context (as an admin) be ok while the other context (non-admin on SQL,
> but using the same admin domain service account) fails?
> Thanks in advance for any info you might have.
Googling it returns:
Circular service dependency was specified.
Explanation:
An application tried to change the service dependency list for a
service. A check of the other service dependency lists in the service
database reveals at least one circular relationship between the
proposed new list and existing lists. For instance, service A must
start before service B in one list, but service B must start before
service A in another list. Your computer has not been configured
properly.
Do both accounts have the same permissions to the directory the file
is output to?
|||There is really only one account, because both SQLAgent and SQLAgent
cmdexec proxy (which is what is used when a non-admin runs a job)
both use this account, which is an admin on the local server. So,
yes, they both have the same permissions. SQLAgent seems to be trying
to start or modify some other service. I looked through services, and
could not find any circular dependencies.
On Feb 13, 9:48 pm, "Steve" <morrisz...@.hotmail.com> wrote:
> Googling it returns:
> Circular service dependency was specified.
> Explanation:
> An application tried to change the service dependency list for a
> service. A check of the other service dependency lists in the service
> database reveals at least one circular relationship between the
> proposed new list and existing lists. For instance, service A must
> start before service B in one list, but service B must start before
> service A in another list. Your computer has not been configured
> properly.
> Do both accounts have the same permissions to the directory the file
> is output to?>
|||Has anyone run into this problem?
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy
use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked
through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on
SQL,
but using the same admin domain service account) fails?
Thanks in advance for any info you might have.

cannot write logfile Error 1059 : Circular service dependency

I have a problem that looks like it has not been discussed before in
these groups.
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on SQL,
but using the same admin domain service account) fails?
Thanks in advance for any info you might have.On Feb 13, 6:33 pm, donn...@.fastmail.fm wrote:
> I have a problem that looks like it has not been discussed before in
> these groups.
> I have a simple SQLAgent job that runs sp_who (could be anything, but
> let's just say sp_who for this example). I have set the jobstep to
> write to an output file "T:\out.txt". If the job is owned by an
> admin, it runs fine and writes the output file. If it is owned by a
> non-admin user, it gets the following error msg:
> Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
> service dependency was specified. The step failed.
> I know about setting up the SQLAgent CMDExec proxy account, and have
> done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
> the same domain account, which is in the administrator group of the
> local server. So, I know that security is not the issue.
> When a simple job runs and writes to an output file, what service or
> service group could it be trying to start or modify? I looked through
> the list of Services, and could not find any circular dependencies.
> Is there a utility to detect this? Why would running under one
> context (as an admin) be ok while the other context (non-admin on SQL,
> but using the same admin domain service account) fails?
> Thanks in advance for any info you might have.
Googling it returns:
Circular service dependency was specified.
Explanation:
An application tried to change the service dependency list for a
service. A check of the other service dependency lists in the service
database reveals at least one circular relationship between the
proposed new list and existing lists. For instance, service A must
start before service B in one list, but service B must start before
service A in another list. Your computer has not been configured
properly.
Do both accounts have the same permissions to the directory the file
is output to?|||There is really only one account, because both SQLAgent and SQLAgent
cmdexec proxy (which is what is used when a non-admin runs a job)
both use this account, which is an admin on the local server. So,
yes, they both have the same permissions. SQLAgent seems to be trying
to start or modify some other service. I looked through services, and
could not find any circular dependencies.
On Feb 13, 9:48 pm, "Steve" <morrisz...@.hotmail.com> wrote:
> Googling it returns:
> Circular service dependency was specified.
> Explanation:
> An application tried to change the service dependency list for a
> service. A check of the other service dependency lists in the service
> database reveals at least one circular relationship between the
> proposed new list and existing lists. For instance, service A must
> start before service B in one list, but service B must start before
> service A in another list. Your computer has not been configured
> properly.
> Do both accounts have the same permissions to the directory the file
> is output to?>|||Has anyone run into this problem'
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy
use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked
through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on
SQL,
but using the same admin domain service account) fails?
Thanks in advance for any info you might have.

cannot write logfile Error 1059 : Circular service dependency

I have a problem that looks like it has not been discussed before in
these groups.

I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:

Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.

I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.

When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on SQL,
but using the same admin domain service account) fails?

Thanks in advance for any info you might have.On Feb 13, 6:33 pm, donn...@.fastmail.fm wrote:

Quote:

Originally Posted by

I have a problem that looks like it has not been discussed before in
these groups.
>
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
>
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
>
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
>
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on SQL,
but using the same admin domain service account) fails?
>
Thanks in advance for any info you might have.

Googling it returns:
Circular service dependency was specified.
Explanation:
An application tried to change the service dependency list for a
service. A check of the other service dependency lists in the service
database reveals at least one circular relationship between the
proposed new list and existing lists. For instance, service A must
start before service B in one list, but service B must start before
service A in another list. Your computer has not been configured
properly.

Do both accounts have the same permissions to the directory the file
is output to?|||There is really only one account, because both SQLAgent and SQLAgent
cmdexec proxy (which is what is used when a non-admin runs a job)
both use this account, which is an admin on the local server. So,
yes, they both have the same permissions. SQLAgent seems to be trying
to start or modify some other service. I looked through services, and
could not find any circular dependencies.

On Feb 13, 9:48 pm, "Steve" <morrisz...@.hotmail.comwrote:

Quote:

Originally Posted by

Googling it returns:
Circular service dependency was specified.
Explanation:
An application tried to change the service dependency list for a
service. A check of the other service dependency lists in the service
database reveals at least one circular relationship between the
proposed new list and existing lists. For instance, service A must
start before service B in one list, but service B must start before
service A in another list. Your computer has not been configured
properly.
>
Do both accounts have the same permissions to the directory the file
is output to?>

|||Has anyone run into this problem??

I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:

Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.

I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy
use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.

When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked
through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on
SQL,
but using the same admin domain service account) fails?

Thanks in advance for any info you might have.

cannot write logfile Error 1059 : Circular service dependency

I have a problem that looks like it has not been discussed before in
these groups.
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on SQL,
but using the same admin domain service account) fails?
Thanks in advance for any info you might have.On Feb 13, 6:33 pm, donn...@.fastmail.fm wrote:
> I have a problem that looks like it has not been discussed before in
> these groups.
> I have a simple SQLAgent job that runs sp_who (could be anything, but
> let's just say sp_who for this example). I have set the jobstep to
> write to an output file "T:\out.txt". If the job is owned by an
> admin, it runs fine and writes the output file. If it is owned by a
> non-admin user, it gets the following error msg:
> Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
> service dependency was specified. The step failed.
> I know about setting up the SQLAgent CMDExec proxy account, and have
> done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy use
> the same domain account, which is in the administrator group of the
> local server. So, I know that security is not the issue.
> When a simple job runs and writes to an output file, what service or
> service group could it be trying to start or modify? I looked through
> the list of Services, and could not find any circular dependencies.
> Is there a utility to detect this? Why would running under one
> context (as an admin) be ok while the other context (non-admin on SQL,
> but using the same admin domain service account) fails?
> Thanks in advance for any info you might have.
Googling it returns:
Circular service dependency was specified.
Explanation:
An application tried to change the service dependency list for a
service. A check of the other service dependency lists in the service
database reveals at least one circular relationship between the
proposed new list and existing lists. For instance, service A must
start before service B in one list, but service B must start before
service A in another list. Your computer has not been configured
properly.
Do both accounts have the same permissions to the directory the file
is output to?|||There is really only one account, because both SQLAgent and SQLAgent
cmdexec proxy (which is what is used when a non-admin runs a job)
both use this account, which is an admin on the local server. So,
yes, they both have the same permissions. SQLAgent seems to be trying
to start or modify some other service. I looked through services, and
could not find any circular dependencies.
On Feb 13, 9:48 pm, "Steve" <morrisz...@.hotmail.com> wrote:
> Googling it returns:
> Circular service dependency was specified.
> Explanation:
> An application tried to change the service dependency list for a
> service. A check of the other service dependency lists in the service
> database reveals at least one circular relationship between the
> proposed new list and existing lists. For instance, service A must
> start before service B in one list, but service B must start before
> service A in another list. Your computer has not been configured
> properly.
> Do both accounts have the same permissions to the directory the file
> is output to?>|||Has anyone run into this problem'
I have a simple SQLAgent job that runs sp_who (could be anything, but
let's just say sp_who for this example). I have set the jobstep to
write to an output file "T:\out.txt". If the job is owned by an
admin, it runs fine and writes the output file. If it is owned by a
non-admin user, it gets the following error msg:
Warning: cannot write logfile t:\out.txt. Error 1059 : Circular
service dependency was specified. The step failed.
I know about setting up the SQLAgent CMDExec proxy account, and have
done that. In fact, both SQLAgent and the SQLAgent cmdexec proxy
use
the same domain account, which is in the administrator group of the
local server. So, I know that security is not the issue.
When a simple job runs and writes to an output file, what service or
service group could it be trying to start or modify? I looked
through
the list of Services, and could not find any circular dependencies.
Is there a utility to detect this? Why would running under one
context (as an admin) be ok while the other context (non-admin on
SQL,
but using the same admin domain service account) fails?
Thanks in advance for any info you might have.

Cannot write a small row! Please help...

Hi everyone,
This is weird. Please help!
I have a long row in the form:
WordA WordB WordC WordD etc...
The above row is 5,294 bytes in size.
I got the soundex equivalent of this row. It now became:
SoundexA SoundexB SoundexC SoundexD etc...
It's size is now 2,898 bytes. AS you would expect as soundex returns a
4 letter code.
I attempt to write the soundex field to its place in the database. I
get the followign error message:
Cannot create a row of size 9602 which is greater than the allowable
maximum of 8060.
The statement has been terminated.
Now, I am totally confused - Does anyone know why this is happening?
Any ideas/suggestions/comments/diagnostics that I could run would be
great. Please help me!
Confused,
Al.Could it be that your possible row size is exceeded ? Not the actual
used one, but the highest possible. Therefore you should have gotten an
error while creating or altering the table once upon a time.
SELECT Sum(ISNULL(CHARACTER_MAXIMUM_LENGTH,length)) from
INFORMATION_SCHEMA.Columns col
INNER join systypes
on systypes.name = col.Data_type
Where table_name = 'YourTable'
HTH, jens Suessmeyer.|||Thanks jens,
I ran this cool command on my table and get the answer: 8392
Unfortunately I don't know where it is! Can you help me locate it or
suggest possible solutions? Can you recommend what I should do please?
Any assistance much appreciated.
Thank you,
Al.|||Sure, you should narrow down your datatypes that these fit on a
datapage of 8060 bytes. In some cases some columns use wasted datatypes
as somebody just assumes how many bytes are to go in that column. If
there is in some cases reengineering,l the people narrow down the
datatypes because they know the actual data size of the columns later.
Or you can split out the table to some "Soundex table" qwhich
references 1by1 the original table and just point with the same PK on
this.
HTH, jens Suessmeyer.

Cannot write a small row! Please help...

Hi everyone,
This is weird. Please help!
I have a long row in the form:
WordAWordBWordCWordD etc...
The above row is 5,294 bytes in size.
I got the soundex equivalent of this row. It now became:
SoundexASoundexBSoundexCSoundexD etc...
It's size is now 2,898 bytes. AS you would expect as soundex returns a
4 letter code.
I attempt to write the soundex field to its place in the database. I
get the followign error message:
Cannot create a row of size 9602 which is greater than the allowable
maximum of 8060.
The statement has been terminated.
Now, I am totally confused - Does anyone know why this is happening?
Any ideas/suggestions/comments/diagnostics that I could run would be
great. Please help me!
Confused,
Al.
Could it be that your possible row size is exceeded ? Not the actual
used one, but the highest possible. Therefore you should have gotten an
error while creating or altering the table once upon a time.
SELECT Sum(ISNULL(CHARACTER_MAXIMUM_LENGTH,length)) from
INFORMATION_SCHEMA.Columns col
INNER join systypes
on systypes.name = col.Data_type
Where table_name = 'YourTable'
HTH, jens Suessmeyer.
|||Thanks jens,
I ran this cool command on my table and get the answer: 8392
Unfortunately I don't know where it is! Can you help me locate it or
suggest possible solutions? Can you recommend what I should do please?
Any assistance much appreciated.
Thank you,
Al.
|||Sure, you should narrow down your datatypes that these fit on a
datapage of 8060 bytes. In some cases some columns use wasted datatypes
as somebody just assumes how many bytes are to go in that column. If
there is in some cases reengineering,l the people narrow down the
datatypes because they know the actual data size of the columns later.
Or you can split out the table to some "Soundex table" qwhich
references 1by1 the original table and just point with the same PK on
this.
HTH, jens Suessmeyer.

Cannot write a small row! Please help...

Hi everyone,
This is weird. Please help!
I have a long row in the form:
WordA WordB WordC WordD etc...
The above row is 5,294 bytes in size.
I got the soundex equivalent of this row. It now became:
SoundexA SoundexB SoundexC SoundexD etc...
It's size is now 2,898 bytes. AS you would expect as soundex returns a
4 letter code.
I attempt to write the soundex field to its place in the database. I
get the followign error message:
Cannot create a row of size 9602 which is greater than the allowable
maximum of 8060.
The statement has been terminated.
Now, I am totally confused - Does anyone know why this is happening?
Any ideas/suggestions/comments/diagnostics that I could run would be
great. Please help me!
Confused,
Al.Could it be that your possible row size is exceeded ? Not the actual
used one, but the highest possible. Therefore you should have gotten an
error while creating or altering the table once upon a time.
SELECT Sum(ISNULL(CHARACTER_MAXIMUM_LENGTH,leng
th)) from
INFORMATION_SCHEMA.Columns col
INNER join systypes
on systypes.name = col.Data_type
Where table_name = 'YourTable'
HTH, jens Suessmeyer.|||Thanks jens,
I ran this cool command on my table and get the answer: 8392
Unfortunately I don't know where it is! Can you help me locate it or
suggest possible solutions? Can you recommend what I should do please?
Any assistance much appreciated.
Thank you,
Al.|||Sure, you should narrow down your datatypes that these fit on a
datapage of 8060 bytes. In some cases some columns use wasted datatypes
as somebody just assumes how many bytes are to go in that column. If
there is in some cases reengineering,l the people narrow down the
datatypes because they know the actual data size of the columns later.
Or you can split out the table to some "Soundex table" qwhich
references 1by1 the original table and just point with the same PK on
this.
HTH, jens Suessmeyer.