I have a stored procedure running from Query Analyzer that runs for a long
time and would like to have status messages print out during the procedure.
They all seem to come when the procedure is complete - is there any way to
have them print while it is running. I 've actually tried having the main
SP call a smaller SP with prints, but they don't come out till the end as
well.
Help to a new Transact SQL writer,
Thanks
TW
TW,
I don't know how to do just what you want, but you could try pumping your
messages into a trace table. Then you could query that table while the
long-running stored procedure continues. Transaction isolation levels would
affect how this works for you.
Russell Fields
"Weave" <tweaver60@.suscom.net> wrote in message
news:10apu6dm256v76@.corp.supernews.com...
> I have a stored procedure running from Query Analyzer that runs for a long
> time and would like to have status messages print out during the
procedure.
> They all seem to come when the procedure is complete - is there any way to
> have them print while it is running. I 've actually tried having the main
> SP call a smaller SP with prints, but they don't come out till the end as
> well.
> Help to a new Transact SQL writer,
> Thanks
> TW
>
|||You could use RAISERROR and the NOWAIT option instead of PRINT.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Weave" <tweaver60@.suscom.net> wrote in message news:10apu6dm256v76@.corp.supernews.com...
> I have a stored procedure running from Query Analyzer that runs for a long
> time and would like to have status messages print out during the procedure.
> They all seem to come when the procedure is complete - is there any way to
> have them print while it is running. I 've actually tried having the main
> SP call a smaller SP with prints, but they don't come out till the end as
> well.
> Help to a new Transact SQL writer,
> Thanks
> TW
>
Showing posts with label runs. Show all posts
Showing posts with label runs. Show all posts
Tuesday, March 20, 2012
Monday, March 19, 2012
Can''t see 64-bit FTS performance counters from 32-bit application
I have a 32-bit application which sometimes runs against 64-bit servers. When it does, I can't read the performance counters published by the FTS service because they're 64-bit only. I get event #1022 from PerfLib in the event log:
Does Microsoft make available 32-bit counter libraries for 32-bit clients of the 64-bit FTS? How do I obtain those bits?
Windows cannot open the 64-bit extensible counter DLL msftesqlFD in a 32-bit environment. Contact the file vendor to obtain a 32-bit version. Alternatively if you are running a 64-bit native environment, you can open the 64-bit extensible counter DLL by using the 64-bit version of Performance Monitor. To use this tool, open the Windows folder, open the System32 folder, and then start Perfmon.exe.
Does Microsoft make available 32-bit counter libraries for 32-bit clients of the 64-bit FTS? How do I obtain those bits?
.B ekiM
Are 32-bit applications not supported by 64-bit servers?
Can''t see 64-bit FTS performance counters from 32-bit application
I have a 32-bit application which sometimes runs against 64-bit servers. When it does, I can't read the performance counters published by the FTS service because they're 64-bit only. I get event #1022 from PerfLib in the event log:
Does Microsoft make available 32-bit counter libraries for 32-bit clients of the 64-bit FTS? How do I obtain those bits?
Windows cannot open the 64-bit extensible counter DLL msftesqlFD in a 32-bit environment. Contact the file vendor to obtain a 32-bit version. Alternatively if you are running a 64-bit native environment, you can open the 64-bit extensible counter DLL by using the 64-bit version of Performance Monitor. To use this tool, open the Windows folder, open the System32 folder, and then start Perfmon.exe.
Does Microsoft make available 32-bit counter libraries for 32-bit clients of the 64-bit FTS? How do I obtain those bits?
.B ekiM
Are 32-bit applications not supported by 64-bit servers?
Sunday, March 11, 2012
Can't run deployed report that runs in development (BIDS)
I have a number of reports that use one of two shared data sources. All of
these reports used to work/run fine in both BIDS and on the server after
deployment. However, recently I cannot run any of them from the
reportserver - but they still all work fine in BIDS.
One datasoure is a SQL2005 database and the other is an older Gupta SQLBase
database (via OLEDB).
The error I get in the report window is bad username or password.
The only thing that's changed recently is that I was forced to change my
domain password. But I also changed any reporting reference to the
username/password as well - and like I said all runs well from BIDS.
I've fiddled with the shared datasource properties/security - trying out
different options but I still can't get this to work. Can anyone provide
some pointers/insight?
Thanks.Michael,
The default behavior in Visual Studio (BIDS) is not to push a datasource if
one already exists with the same name. Thus if you make a change in BIDS, it
will not get updated to the server if it already exists, unless you change
the default behavior.
Right click on the Project icon in Solution Explorer and select Properties,
and then change the OverwriteDataSources to true and re-deploy the datasource
with the updates.
I suggest changing it back when you are done. This is a great option for
deployments into different environments.
Reeves
"Michael K. Walter" wrote:
> I have a number of reports that use one of two shared data sources. All of
> these reports used to work/run fine in both BIDS and on the server after
> deployment. However, recently I cannot run any of them from the
> reportserver - but they still all work fine in BIDS.
> One datasoure is a SQL2005 database and the other is an older Gupta SQLBase
> database (via OLEDB).
> The error I get in the report window is bad username or password.
> The only thing that's changed recently is that I was forced to change my
> domain password. But I also changed any reporting reference to the
> username/password as well - and like I said all runs well from BIDS.
> I've fiddled with the shared datasource properties/security - trying out
> different options but I still can't get this to work. Can anyone provide
> some pointers/insight?
> Thanks.
>
>|||Thanks Reeves.
However, I'm pretty sure I tried that already. I'll go back into the
projects and double check though.
Michael
"Reeves Smith" <ReevesSmith@.discussions.microsoft.com> wrote in message
news:F378170C-9297-4177-9BAF-7ACD30ACE5E3@.microsoft.com...
> Michael,
> The default behavior in Visual Studio (BIDS) is not to push a datasource
> if
> one already exists with the same name. Thus if you make a change in BIDS,
> it
> will not get updated to the server if it already exists, unless you change
> the default behavior.
> Right click on the Project icon in Solution Explorer and select
> Properties,
> and then change the OverwriteDataSources to true and re-deploy the
> datasource
> with the updates.
> I suggest changing it back when you are done. This is a great option for
> deployments into different environments.
> Reeves
> "Michael K. Walter" wrote:
>> I have a number of reports that use one of two shared data sources. All
>> of
>> these reports used to work/run fine in both BIDS and on the server after
>> deployment. However, recently I cannot run any of them from the
>> reportserver - but they still all work fine in BIDS.
>> One datasoure is a SQL2005 database and the other is an older Gupta
>> SQLBase
>> database (via OLEDB).
>> The error I get in the report window is bad username or password.
>> The only thing that's changed recently is that I was forced to change my
>> domain password. But I also changed any reporting reference to the
>> username/password as well - and like I said all runs well from BIDS.
>> I've fiddled with the shared datasource properties/security - trying out
>> different options but I still can't get this to work. Can anyone provide
>> some pointers/insight?
>> Thanks.
>>
these reports used to work/run fine in both BIDS and on the server after
deployment. However, recently I cannot run any of them from the
reportserver - but they still all work fine in BIDS.
One datasoure is a SQL2005 database and the other is an older Gupta SQLBase
database (via OLEDB).
The error I get in the report window is bad username or password.
The only thing that's changed recently is that I was forced to change my
domain password. But I also changed any reporting reference to the
username/password as well - and like I said all runs well from BIDS.
I've fiddled with the shared datasource properties/security - trying out
different options but I still can't get this to work. Can anyone provide
some pointers/insight?
Thanks.Michael,
The default behavior in Visual Studio (BIDS) is not to push a datasource if
one already exists with the same name. Thus if you make a change in BIDS, it
will not get updated to the server if it already exists, unless you change
the default behavior.
Right click on the Project icon in Solution Explorer and select Properties,
and then change the OverwriteDataSources to true and re-deploy the datasource
with the updates.
I suggest changing it back when you are done. This is a great option for
deployments into different environments.
Reeves
"Michael K. Walter" wrote:
> I have a number of reports that use one of two shared data sources. All of
> these reports used to work/run fine in both BIDS and on the server after
> deployment. However, recently I cannot run any of them from the
> reportserver - but they still all work fine in BIDS.
> One datasoure is a SQL2005 database and the other is an older Gupta SQLBase
> database (via OLEDB).
> The error I get in the report window is bad username or password.
> The only thing that's changed recently is that I was forced to change my
> domain password. But I also changed any reporting reference to the
> username/password as well - and like I said all runs well from BIDS.
> I've fiddled with the shared datasource properties/security - trying out
> different options but I still can't get this to work. Can anyone provide
> some pointers/insight?
> Thanks.
>
>|||Thanks Reeves.
However, I'm pretty sure I tried that already. I'll go back into the
projects and double check though.
Michael
"Reeves Smith" <ReevesSmith@.discussions.microsoft.com> wrote in message
news:F378170C-9297-4177-9BAF-7ACD30ACE5E3@.microsoft.com...
> Michael,
> The default behavior in Visual Studio (BIDS) is not to push a datasource
> if
> one already exists with the same name. Thus if you make a change in BIDS,
> it
> will not get updated to the server if it already exists, unless you change
> the default behavior.
> Right click on the Project icon in Solution Explorer and select
> Properties,
> and then change the OverwriteDataSources to true and re-deploy the
> datasource
> with the updates.
> I suggest changing it back when you are done. This is a great option for
> deployments into different environments.
> Reeves
> "Michael K. Walter" wrote:
>> I have a number of reports that use one of two shared data sources. All
>> of
>> these reports used to work/run fine in both BIDS and on the server after
>> deployment. However, recently I cannot run any of them from the
>> reportserver - but they still all work fine in BIDS.
>> One datasoure is a SQL2005 database and the other is an older Gupta
>> SQLBase
>> database (via OLEDB).
>> The error I get in the report window is bad username or password.
>> The only thing that's changed recently is that I was forced to change my
>> domain password. But I also changed any reporting reference to the
>> username/password as well - and like I said all runs well from BIDS.
>> I've fiddled with the shared datasource properties/security - trying out
>> different options but I still can't get this to work. Can anyone provide
>> some pointers/insight?
>> Thanks.
>>
Tuesday, February 14, 2012
Can't Install SQL 2000 service pack 4
We are having trouble installing SQL2000 service pack 4 on our server. The package runs through and looks like it installs files to c:\, but the install never asks us for any of the questions regarding the install of service pack 4. One issue we were thinking about was that MSDE was installed on the server also. We have a 2003 server with SQL 2000 sp3 (8.00.760)
Are you running this through a command line or through the UI? If it is command line, can you supply the command line you are running?
Thanks,
Sam Lester (MSFT)
Can't install RS 2000
I am trying to install RS 2000 on my local SQL 2000 that runs on XP Pro.
I am getting an error after installation verifies credentials. The error
says something about a wrong version of RS I am trying to install. I have
tried Ent, Dev, and Stand versions. Only Dev version gets to the point of
the error. What is a solution of that problem?
ThanksWhat version of SQL 2000 do you have installed? I've had an issue where I
have tried to install RS (Standard) with SQL 2000 (Dev). Make sure the
versions are compatible.
"Mark Goldin" wrote:
> I am trying to install RS 2000 on my local SQL 2000 that runs on XP Pro.
> I am getting an error after installation verifies credentials. The error
> says something about a wrong version of RS I am trying to install. I have
> tried Ent, Dev, and Stand versions. Only Dev version gets to the point of
> the error. What is a solution of that problem?
> Thanks
>
>
I am getting an error after installation verifies credentials. The error
says something about a wrong version of RS I am trying to install. I have
tried Ent, Dev, and Stand versions. Only Dev version gets to the point of
the error. What is a solution of that problem?
ThanksWhat version of SQL 2000 do you have installed? I've had an issue where I
have tried to install RS (Standard) with SQL 2000 (Dev). Make sure the
versions are compatible.
"Mark Goldin" wrote:
> I am trying to install RS 2000 on my local SQL 2000 that runs on XP Pro.
> I am getting an error after installation verifies credentials. The error
> says something about a wrong version of RS I am trying to install. I have
> tried Ent, Dev, and Stand versions. Only Dev version gets to the point of
> the error. What is a solution of that problem?
> Thanks
>
>
Friday, February 10, 2012
Can't get SQL 2000 agent to run
Need urgent help. The sql 2000 agent service never runs. Tried to run under a
domain admin acct which belongs to SysAdmins role and still doesn't run. Ran
the sqlagent with -c -v switches from command line and got foll. 2 errors:
[298] sql server error 170, line 47: incorrect syntax near 'collate'.
[sqlstate 42000] (connisloginsysadmin)
[000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
but '(Unknown)' is not a member of the SysAdmin role
Tried the microsoft kb solns and still not running. Need this resolved
urgently. Pls help. Thks. We use sql 2000, sp4.
Hi
How about using Service Control Manager.
EXEC master..xp_servicecontrol 'QUERYSTATE', 'SQLSERVERAGENT'
"duchov" <duchov@.discussions.microsoft.com> wrote in message
news:588DF7E4-D96A-4BAD-A1A5-44636138EE54@.microsoft.com...
> Need urgent help. The sql 2000 agent service never runs. Tried to run
> under a
> domain admin acct which belongs to SysAdmins role and still doesn't run.
> Ran
> the sqlagent with -c -v switches from command line and got foll. 2 errors:
> [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> [sqlstate 42000] (connisloginsysadmin)
> [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> but '(Unknown)' is not a member of the SysAdmin role
> Tried the microsoft kb solns and still not running. Need this resolved
> urgently. Pls help. Thks. We use sql 2000, sp4.
|||Hi
I don't see collate in any of the statements issued when SQL Agent is
stopped or started. You may want to profile the agent starting (including
errors and exception events) to see what is being processed.
Is there any other messages in the SQL Server logs?
Have you tried running this as the system account?
John
John
"duchov" wrote:
> Need urgent help. The sql 2000 agent service never runs. Tried to run under a
> domain admin acct which belongs to SysAdmins role and still doesn't run. Ran
> the sqlagent with -c -v switches from command line and got foll. 2 errors:
> [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> [sqlstate 42000] (connisloginsysadmin)
> [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> but '(Unknown)' is not a member of the SysAdmin role
> Tried the microsoft kb solns and still not running. Need this resolved
> urgently. Pls help. Thks. We use sql 2000, sp4.
|||"John Bell" wrote:
[vbcol=seagreen]
> Hi
> I don't see collate in any of the statements issued when SQL Agent is
> stopped or started. You may want to profile the agent starting (including
> errors and exception events) to see what is being processed.
> Is there any other messages in the SQL Server logs?
> Have you tried running this as the system account?
> John
> John
> "duchov" wrote:
|||Hi John/Uri
setting the agent acct from either EM or service ctrl mngr has same result.
Only other errors in the sql logs are:
1) Operating system error = 31(A device attached to the system is not
functioning.).
This error is in multiple logs though not the current log. Any ideas on this?
2) spid52 Error: 15457, Severity: 0, State: 1 (a sql support site said You
will see that 15457 error
popup if you pull up your SQL Server properties.)
3) Configuration option 'show advanced options' changed from 1 to 1. Run the
RECONFIGURE statement
to install..
Errors 2 & 3 are in today's log only and seems to be b/c checked the sql
server properties
Initially agent was under local sys acct n it never ran which is y tried a
domain admin acct but still no success
How do I profile the agent startup/shutdown? I ran a trace via sql profiler
(included errors/exceptions) and manually tried to start agent. the trace
showed 2 records under an application name of sqlAgent - initial boot probe
with no info really. is this what u meant?
Reason this is important is b/c I scheduled some nightly sql backups to disk
n they never run b/c the agent service never starts. Hope u can help.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> I don't see collate in any of the statements issued when SQL Agent is
> stopped or started. You may want to profile the agent starting (including
> errors and exception events) to see what is being processed.
> Is there any other messages in the SQL Server logs?
> Have you tried running this as the system account?
> John
> John
> "duchov" wrote:
|||Hi
An Operating System Errors seems like the problem is external to SQL server,
is there anything in the System Event logs?
John
"duchov" <duchov@.discussions.microsoft.com> wrote in message
news:885311AD-1FAC-4745-9430-D1F1A573796E@.microsoft.com...[vbcol=seagreen]
> Hi John/Uri
> setting the agent acct from either EM or service ctrl mngr has same
> result.
> Only other errors in the sql logs are:
> 1) Operating system error = 31(A device attached to the system is not
> functioning.).
> This error is in multiple logs though not the current log. Any ideas on
> this?
> 2) spid52 Error: 15457, Severity: 0, State: 1 (a sql support site said You
> will see that 15457 error
> popup if you pull up your SQL Server properties.)
> 3) Configuration option 'show advanced options' changed from 1 to 1. Run
> the
> RECONFIGURE statement
> to install..
> Errors 2 & 3 are in today's log only and seems to be b/c checked the sql
> server properties
> Initially agent was under local sys acct n it never ran which is y tried a
> domain admin acct but still no success
> How do I profile the agent startup/shutdown? I ran a trace via sql
> profiler
> (included errors/exceptions) and manually tried to start agent. the trace
> showed 2 records under an application name of sqlAgent - initial boot
> probe
> with no info really. is this what u meant?
> Reason this is important is b/c I scheduled some nightly sql backups to
> disk
> n they never run b/c the agent service never starts. Hope u can help.
> "John Bell" wrote:
domain admin acct which belongs to SysAdmins role and still doesn't run. Ran
the sqlagent with -c -v switches from command line and got foll. 2 errors:
[298] sql server error 170, line 47: incorrect syntax near 'collate'.
[sqlstate 42000] (connisloginsysadmin)
[000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
but '(Unknown)' is not a member of the SysAdmin role
Tried the microsoft kb solns and still not running. Need this resolved
urgently. Pls help. Thks. We use sql 2000, sp4.
Hi
How about using Service Control Manager.
EXEC master..xp_servicecontrol 'QUERYSTATE', 'SQLSERVERAGENT'
"duchov" <duchov@.discussions.microsoft.com> wrote in message
news:588DF7E4-D96A-4BAD-A1A5-44636138EE54@.microsoft.com...
> Need urgent help. The sql 2000 agent service never runs. Tried to run
> under a
> domain admin acct which belongs to SysAdmins role and still doesn't run.
> Ran
> the sqlagent with -c -v switches from command line and got foll. 2 errors:
> [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> [sqlstate 42000] (connisloginsysadmin)
> [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> but '(Unknown)' is not a member of the SysAdmin role
> Tried the microsoft kb solns and still not running. Need this resolved
> urgently. Pls help. Thks. We use sql 2000, sp4.
|||Hi
I don't see collate in any of the statements issued when SQL Agent is
stopped or started. You may want to profile the agent starting (including
errors and exception events) to see what is being processed.
Is there any other messages in the SQL Server logs?
Have you tried running this as the system account?
John
John
"duchov" wrote:
> Need urgent help. The sql 2000 agent service never runs. Tried to run under a
> domain admin acct which belongs to SysAdmins role and still doesn't run. Ran
> the sqlagent with -c -v switches from command line and got foll. 2 errors:
> [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> [sqlstate 42000] (connisloginsysadmin)
> [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> but '(Unknown)' is not a member of the SysAdmin role
> Tried the microsoft kb solns and still not running. Need this resolved
> urgently. Pls help. Thks. We use sql 2000, sp4.
|||"John Bell" wrote:
[vbcol=seagreen]
> Hi
> I don't see collate in any of the statements issued when SQL Agent is
> stopped or started. You may want to profile the agent starting (including
> errors and exception events) to see what is being processed.
> Is there any other messages in the SQL Server logs?
> Have you tried running this as the system account?
> John
> John
> "duchov" wrote:
|||Hi John/Uri
setting the agent acct from either EM or service ctrl mngr has same result.
Only other errors in the sql logs are:
1) Operating system error = 31(A device attached to the system is not
functioning.).
This error is in multiple logs though not the current log. Any ideas on this?
2) spid52 Error: 15457, Severity: 0, State: 1 (a sql support site said You
will see that 15457 error
popup if you pull up your SQL Server properties.)
3) Configuration option 'show advanced options' changed from 1 to 1. Run the
RECONFIGURE statement
to install..
Errors 2 & 3 are in today's log only and seems to be b/c checked the sql
server properties
Initially agent was under local sys acct n it never ran which is y tried a
domain admin acct but still no success
How do I profile the agent startup/shutdown? I ran a trace via sql profiler
(included errors/exceptions) and manually tried to start agent. the trace
showed 2 records under an application name of sqlAgent - initial boot probe
with no info really. is this what u meant?
Reason this is important is b/c I scheduled some nightly sql backups to disk
n they never run b/c the agent service never starts. Hope u can help.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> I don't see collate in any of the statements issued when SQL Agent is
> stopped or started. You may want to profile the agent starting (including
> errors and exception events) to see what is being processed.
> Is there any other messages in the SQL Server logs?
> Have you tried running this as the system account?
> John
> John
> "duchov" wrote:
|||Hi
An Operating System Errors seems like the problem is external to SQL server,
is there anything in the System Event logs?
John
"duchov" <duchov@.discussions.microsoft.com> wrote in message
news:885311AD-1FAC-4745-9430-D1F1A573796E@.microsoft.com...[vbcol=seagreen]
> Hi John/Uri
> setting the agent acct from either EM or service ctrl mngr has same
> result.
> Only other errors in the sql logs are:
> 1) Operating system error = 31(A device attached to the system is not
> functioning.).
> This error is in multiple logs though not the current log. Any ideas on
> this?
> 2) spid52 Error: 15457, Severity: 0, State: 1 (a sql support site said You
> will see that 15457 error
> popup if you pull up your SQL Server properties.)
> 3) Configuration option 'show advanced options' changed from 1 to 1. Run
> the
> RECONFIGURE statement
> to install..
> Errors 2 & 3 are in today's log only and seems to be b/c checked the sql
> server properties
> Initially agent was under local sys acct n it never ran which is y tried a
> domain admin acct but still no success
> How do I profile the agent startup/shutdown? I ran a trace via sql
> profiler
> (included errors/exceptions) and manually tried to start agent. the trace
> showed 2 records under an application name of sqlAgent - initial boot
> probe
> with no info really. is this what u meant?
> Reason this is important is b/c I scheduled some nightly sql backups to
> disk
> n they never run b/c the agent service never starts. Hope u can help.
> "John Bell" wrote:
Can't get SQL 2000 agent to run
Need urgent help. The sql 2000 agent service never runs. Tried to run under
a
domain admin acct which belongs to SysAdmins role and still doesn't run. Ran
the sqlagent with -c -v switches from command line and got foll. 2 errors:
[298] sql server error 170, line 47: incorrect syntax near 'collate'.
[sqlstate 42000] (connisloginsysadmin)
[000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
but '(Unknown)' is not a member of the SysAdmin role
Tried the microsoft kb solns and still not running. Need this resolved
urgently. Pls help. Thks. We use sql 2000, sp4.Hi
How about using Service Control Manager.
EXEC master..xp_servicecontrol 'QUERYSTATE', 'SQLSERVERAGENT'
"duchov" <duchov@.discussions.microsoft.com> wrote in message
news:588DF7E4-D96A-4BAD-A1A5-44636138EE54@.microsoft.com...
> Need urgent help. The sql 2000 agent service never runs. Tried to run
> under a
> domain admin acct which belongs to SysAdmins role and still doesn't run.
> Ran
> the sqlagent with -c -v switches from command line and got foll. 2 errors:
> [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> [sqlstate 42000] (connisloginsysadmin)
> [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> but '(Unknown)' is not a member of the SysAdmin role
> Tried the microsoft kb solns and still not running. Need this resolved
> urgently. Pls help. Thks. We use sql 2000, sp4.|||Hi
I don't see collate in any of the statements issued when SQL Agent is
stopped or started. You may want to profile the agent starting (including
errors and exception events) to see what is being processed.
Is there any other messages in the SQL Server logs?
Have you tried running this as the system account?
John
John
"duchov" wrote:
> Need urgent help. The sql 2000 agent service never runs. Tried to run unde
r a
> domain admin acct which belongs to SysAdmins role and still doesn't run. R
an
> the sqlagent with -c -v switches from command line and got foll. 2 errors:
> [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> [sqlstate 42000] (connisloginsysadmin)
> [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> but '(Unknown)' is not a member of the SysAdmin role
> Tried the microsoft kb solns and still not running. Need this resolved
> urgently. Pls help. Thks. We use sql 2000, sp4.|||"John Bell" wrote:
[vbcol=seagreen]
> Hi
> I don't see collate in any of the statements issued when SQL Agent is
> stopped or started. You may want to profile the agent starting (including
> errors and exception events) to see what is being processed.
> Is there any other messages in the SQL Server logs?
> Have you tried running this as the system account?
> John
> John
> "duchov" wrote:
>|||Hi John/Uri
setting the agent acct from either EM or service ctrl mngr has same result.
Only other errors in the sql logs are:
1) Operating system error = 31(A device attached to the system is not
functioning.).
This error is in multiple logs though not the current log. Any ideas on this
?
2) spid52 Error: 15457, Severity: 0, State: 1 (a sql support site said You
will see that 15457 error
popup if you pull up your SQL Server properties.)
3) Configuration option 'show advanced options' changed from 1 to 1. Run the
RECONFIGURE statement
to install..
Errors 2 & 3 are in today's log only and seems to be b/c checked the sql
server properties
Initially agent was under local sys acct n it never ran which is y tried a
domain admin acct but still no success
How do I profile the agent startup/shutdown? I ran a trace via sql profiler
(included errors/exceptions) and manually tried to start agent. the trace
showed 2 records under an application name of sqlAgent - initial boot probe
with no info really. is this what u meant?
Reason this is important is b/c I scheduled some nightly sql backups to disk
n they never run b/c the agent service never starts. Hope u can help.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> I don't see collate in any of the statements issued when SQL Agent is
> stopped or started. You may want to profile the agent starting (including
> errors and exception events) to see what is being processed.
> Is there any other messages in the SQL Server logs?
> Have you tried running this as the system account?
> John
> John
> "duchov" wrote:
>|||Hi
An Operating System Errors seems like the problem is external to SQL server,
is there anything in the System Event logs?
John
"duchov" <duchov@.discussions.microsoft.com> wrote in message
news:885311AD-1FAC-4745-9430-D1F1A573796E@.microsoft.com...[vbcol=seagreen]
> Hi John/Uri
> setting the agent acct from either EM or service ctrl mngr has same
> result.
> Only other errors in the sql logs are:
> 1) Operating system error = 31(A device attached to the system is not
> functioning.).
> This error is in multiple logs though not the current log. Any ideas on
> this?
> 2) spid52 Error: 15457, Severity: 0, State: 1 (a sql support site said You
> will see that 15457 error
> popup if you pull up your SQL Server properties.)
> 3) Configuration option 'show advanced options' changed from 1 to 1. Run
> the
> RECONFIGURE statement
> to install..
> Errors 2 & 3 are in today's log only and seems to be b/c checked the sql
> server properties
> Initially agent was under local sys acct n it never ran which is y tried a
> domain admin acct but still no success
> How do I profile the agent startup/shutdown? I ran a trace via sql
> profiler
> (included errors/exceptions) and manually tried to start agent. the trace
> showed 2 records under an application name of sqlAgent - initial boot
> probe
> with no info really. is this what u meant?
> Reason this is important is b/c I scheduled some nightly sql backups to
> disk
> n they never run b/c the agent service never starts. Hope u can help.
> "John Bell" wrote:
>
a
domain admin acct which belongs to SysAdmins role and still doesn't run. Ran
the sqlagent with -c -v switches from command line and got foll. 2 errors:
[298] sql server error 170, line 47: incorrect syntax near 'collate'.
[sqlstate 42000] (connisloginsysadmin)
[000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
but '(Unknown)' is not a member of the SysAdmin role
Tried the microsoft kb solns and still not running. Need this resolved
urgently. Pls help. Thks. We use sql 2000, sp4.Hi
How about using Service Control Manager.
EXEC master..xp_servicecontrol 'QUERYSTATE', 'SQLSERVERAGENT'
"duchov" <duchov@.discussions.microsoft.com> wrote in message
news:588DF7E4-D96A-4BAD-A1A5-44636138EE54@.microsoft.com...
> Need urgent help. The sql 2000 agent service never runs. Tried to run
> under a
> domain admin acct which belongs to SysAdmins role and still doesn't run.
> Ran
> the sqlagent with -c -v switches from command line and got foll. 2 errors:
> [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> [sqlstate 42000] (connisloginsysadmin)
> [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> but '(Unknown)' is not a member of the SysAdmin role
> Tried the microsoft kb solns and still not running. Need this resolved
> urgently. Pls help. Thks. We use sql 2000, sp4.|||Hi
I don't see collate in any of the statements issued when SQL Agent is
stopped or started. You may want to profile the agent starting (including
errors and exception events) to see what is being processed.
Is there any other messages in the SQL Server logs?
Have you tried running this as the system account?
John
John
"duchov" wrote:
> Need urgent help. The sql 2000 agent service never runs. Tried to run unde
r a
> domain admin acct which belongs to SysAdmins role and still doesn't run. R
an
> the sqlagent with -c -v switches from command line and got foll. 2 errors:
> [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> [sqlstate 42000] (connisloginsysadmin)
> [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> but '(Unknown)' is not a member of the SysAdmin role
> Tried the microsoft kb solns and still not running. Need this resolved
> urgently. Pls help. Thks. We use sql 2000, sp4.|||"John Bell" wrote:
[vbcol=seagreen]
> Hi
> I don't see collate in any of the statements issued when SQL Agent is
> stopped or started. You may want to profile the agent starting (including
> errors and exception events) to see what is being processed.
> Is there any other messages in the SQL Server logs?
> Have you tried running this as the system account?
> John
> John
> "duchov" wrote:
>|||Hi John/Uri
setting the agent acct from either EM or service ctrl mngr has same result.
Only other errors in the sql logs are:
1) Operating system error = 31(A device attached to the system is not
functioning.).
This error is in multiple logs though not the current log. Any ideas on this
?
2) spid52 Error: 15457, Severity: 0, State: 1 (a sql support site said You
will see that 15457 error
popup if you pull up your SQL Server properties.)
3) Configuration option 'show advanced options' changed from 1 to 1. Run the
RECONFIGURE statement
to install..
Errors 2 & 3 are in today's log only and seems to be b/c checked the sql
server properties
Initially agent was under local sys acct n it never ran which is y tried a
domain admin acct but still no success
How do I profile the agent startup/shutdown? I ran a trace via sql profiler
(included errors/exceptions) and manually tried to start agent. the trace
showed 2 records under an application name of sqlAgent - initial boot probe
with no info really. is this what u meant?
Reason this is important is b/c I scheduled some nightly sql backups to disk
n they never run b/c the agent service never starts. Hope u can help.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> I don't see collate in any of the statements issued when SQL Agent is
> stopped or started. You may want to profile the agent starting (including
> errors and exception events) to see what is being processed.
> Is there any other messages in the SQL Server logs?
> Have you tried running this as the system account?
> John
> John
> "duchov" wrote:
>|||Hi
An Operating System Errors seems like the problem is external to SQL server,
is there anything in the System Event logs?
John
"duchov" <duchov@.discussions.microsoft.com> wrote in message
news:885311AD-1FAC-4745-9430-D1F1A573796E@.microsoft.com...[vbcol=seagreen]
> Hi John/Uri
> setting the agent acct from either EM or service ctrl mngr has same
> result.
> Only other errors in the sql logs are:
> 1) Operating system error = 31(A device attached to the system is not
> functioning.).
> This error is in multiple logs though not the current log. Any ideas on
> this?
> 2) spid52 Error: 15457, Severity: 0, State: 1 (a sql support site said You
> will see that 15457 error
> popup if you pull up your SQL Server properties.)
> 3) Configuration option 'show advanced options' changed from 1 to 1. Run
> the
> RECONFIGURE statement
> to install..
> Errors 2 & 3 are in today's log only and seems to be b/c checked the sql
> server properties
> Initially agent was under local sys acct n it never ran which is y tried a
> domain admin acct but still no success
> How do I profile the agent startup/shutdown? I ran a trace via sql
> profiler
> (included errors/exceptions) and manually tried to start agent. the trace
> showed 2 records under an application name of sqlAgent - initial boot
> probe
> with no info really. is this what u meant?
> Reason this is important is b/c I scheduled some nightly sql backups to
> disk
> n they never run b/c the agent service never starts. Hope u can help.
> "John Bell" wrote:
>
Can't get SQL 2000 agent to run
Need urgent help. The sql 2000 agent service never runs. Tried to run under a
domain admin acct which belongs to SysAdmins role and still doesn't run. Ran
the sqlagent with -c -v switches from command line and got foll. 2 errors:
[298] sql server error 170, line 47: incorrect syntax near 'collate'.
[sqlstate 42000] (connisloginsysadmin)
[000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
but '(Unknown)' is not a member of the SysAdmin role
Tried the microsoft kb solns and still not running. Need this resolved
urgently. Pls help. Thks. We use sql 2000, sp4.Hi
How about using Service Control Manager.
EXEC master..xp_servicecontrol 'QUERYSTATE', 'SQLSERVERAGENT'
"duchov" <duchov@.discussions.microsoft.com> wrote in message
news:588DF7E4-D96A-4BAD-A1A5-44636138EE54@.microsoft.com...
> Need urgent help. The sql 2000 agent service never runs. Tried to run
> under a
> domain admin acct which belongs to SysAdmins role and still doesn't run.
> Ran
> the sqlagent with -c -v switches from command line and got foll. 2 errors:
> [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> [sqlstate 42000] (connisloginsysadmin)
> [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> but '(Unknown)' is not a member of the SysAdmin role
> Tried the microsoft kb solns and still not running. Need this resolved
> urgently. Pls help. Thks. We use sql 2000, sp4.|||Hi
I don't see collate in any of the statements issued when SQL Agent is
stopped or started. You may want to profile the agent starting (including
errors and exception events) to see what is being processed.
Is there any other messages in the SQL Server logs?
Have you tried running this as the system account?
John
John
"duchov" wrote:
> Need urgent help. The sql 2000 agent service never runs. Tried to run under a
> domain admin acct which belongs to SysAdmins role and still doesn't run. Ran
> the sqlagent with -c -v switches from command line and got foll. 2 errors:
> [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> [sqlstate 42000] (connisloginsysadmin)
> [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> but '(Unknown)' is not a member of the SysAdmin role
> Tried the microsoft kb solns and still not running. Need this resolved
> urgently. Pls help. Thks. We use sql 2000, sp4.|||"John Bell" wrote:
> Hi
> I don't see collate in any of the statements issued when SQL Agent is
> stopped or started. You may want to profile the agent starting (including
> errors and exception events) to see what is being processed.
> Is there any other messages in the SQL Server logs?
> Have you tried running this as the system account?
> John
> John
> "duchov" wrote:
> > Need urgent help. The sql 2000 agent service never runs. Tried to run under a
> > domain admin acct which belongs to SysAdmins role and still doesn't run. Ran
> > the sqlagent with -c -v switches from command line and got foll. 2 errors:
> >
> > [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> >
> > [sqlstate 42000] (connisloginsysadmin)
> >
> > [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> >
> > but '(Unknown)' is not a member of the SysAdmin role
> > Tried the microsoft kb solns and still not running. Need this resolved
> > urgently. Pls help. Thks. We use sql 2000, sp4.|||Hi John/Uri
setting the agent acct from either EM or service ctrl mngr has same result.
Only other errors in the sql logs are:
1) Operating system error = 31(A device attached to the system is not
functioning.).
This error is in multiple logs though not the current log. Any ideas on this?
2) spid52 Error: 15457, Severity: 0, State: 1 (a sql support site said You
will see that 15457 error
popup if you pull up your SQL Server properties.)
3) Configuration option 'show advanced options' changed from 1 to 1. Run the
RECONFIGURE statement
to install..
Errors 2 & 3 are in today's log only and seems to be b/c checked the sql
server properties
Initially agent was under local sys acct n it never ran which is y tried a
domain admin acct but still no success
How do I profile the agent startup/shutdown? I ran a trace via sql profiler
(included errors/exceptions) and manually tried to start agent. the trace
showed 2 records under an application name of sqlAgent - initial boot probe
with no info really. is this what u meant?
Reason this is important is b/c I scheduled some nightly sql backups to disk
n they never run b/c the agent service never starts. Hope u can help.
"John Bell" wrote:
> Hi
> I don't see collate in any of the statements issued when SQL Agent is
> stopped or started. You may want to profile the agent starting (including
> errors and exception events) to see what is being processed.
> Is there any other messages in the SQL Server logs?
> Have you tried running this as the system account?
> John
> John
> "duchov" wrote:
> > Need urgent help. The sql 2000 agent service never runs. Tried to run under a
> > domain admin acct which belongs to SysAdmins role and still doesn't run. Ran
> > the sqlagent with -c -v switches from command line and got foll. 2 errors:
> >
> > [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> >
> > [sqlstate 42000] (connisloginsysadmin)
> >
> > [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> >
> > but '(Unknown)' is not a member of the SysAdmin role
> > Tried the microsoft kb solns and still not running. Need this resolved
> > urgently. Pls help. Thks. We use sql 2000, sp4.|||Hi
An Operating System Errors seems like the problem is external to SQL server,
is there anything in the System Event logs?
John
"duchov" <duchov@.discussions.microsoft.com> wrote in message
news:885311AD-1FAC-4745-9430-D1F1A573796E@.microsoft.com...
> Hi John/Uri
> setting the agent acct from either EM or service ctrl mngr has same
> result.
> Only other errors in the sql logs are:
> 1) Operating system error = 31(A device attached to the system is not
> functioning.).
> This error is in multiple logs though not the current log. Any ideas on
> this?
> 2) spid52 Error: 15457, Severity: 0, State: 1 (a sql support site said You
> will see that 15457 error
> popup if you pull up your SQL Server properties.)
> 3) Configuration option 'show advanced options' changed from 1 to 1. Run
> the
> RECONFIGURE statement
> to install..
> Errors 2 & 3 are in today's log only and seems to be b/c checked the sql
> server properties
> Initially agent was under local sys acct n it never ran which is y tried a
> domain admin acct but still no success
> How do I profile the agent startup/shutdown? I ran a trace via sql
> profiler
> (included errors/exceptions) and manually tried to start agent. the trace
> showed 2 records under an application name of sqlAgent - initial boot
> probe
> with no info really. is this what u meant?
> Reason this is important is b/c I scheduled some nightly sql backups to
> disk
> n they never run b/c the agent service never starts. Hope u can help.
> "John Bell" wrote:
>> Hi
>> I don't see collate in any of the statements issued when SQL Agent is
>> stopped or started. You may want to profile the agent starting (including
>> errors and exception events) to see what is being processed.
>> Is there any other messages in the SQL Server logs?
>> Have you tried running this as the system account?
>> John
>> John
>> "duchov" wrote:
>> > Need urgent help. The sql 2000 agent service never runs. Tried to run
>> > under a
>> > domain admin acct which belongs to SysAdmins role and still doesn't
>> > run. Ran
>> > the sqlagent with -c -v switches from command line and got foll. 2
>> > errors:
>> >
>> > [298] sql server error 170, line 47: incorrect syntax near 'collate'.
>> >
>> > [sqlstate 42000] (connisloginsysadmin)
>> >
>> > [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
>> >
>> > but '(Unknown)' is not a member of the SysAdmin role
>> > Tried the microsoft kb solns and still not running. Need this resolved
>> > urgently. Pls help. Thks. We use sql 2000, sp4.
domain admin acct which belongs to SysAdmins role and still doesn't run. Ran
the sqlagent with -c -v switches from command line and got foll. 2 errors:
[298] sql server error 170, line 47: incorrect syntax near 'collate'.
[sqlstate 42000] (connisloginsysadmin)
[000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
but '(Unknown)' is not a member of the SysAdmin role
Tried the microsoft kb solns and still not running. Need this resolved
urgently. Pls help. Thks. We use sql 2000, sp4.Hi
How about using Service Control Manager.
EXEC master..xp_servicecontrol 'QUERYSTATE', 'SQLSERVERAGENT'
"duchov" <duchov@.discussions.microsoft.com> wrote in message
news:588DF7E4-D96A-4BAD-A1A5-44636138EE54@.microsoft.com...
> Need urgent help. The sql 2000 agent service never runs. Tried to run
> under a
> domain admin acct which belongs to SysAdmins role and still doesn't run.
> Ran
> the sqlagent with -c -v switches from command line and got foll. 2 errors:
> [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> [sqlstate 42000] (connisloginsysadmin)
> [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> but '(Unknown)' is not a member of the SysAdmin role
> Tried the microsoft kb solns and still not running. Need this resolved
> urgently. Pls help. Thks. We use sql 2000, sp4.|||Hi
I don't see collate in any of the statements issued when SQL Agent is
stopped or started. You may want to profile the agent starting (including
errors and exception events) to see what is being processed.
Is there any other messages in the SQL Server logs?
Have you tried running this as the system account?
John
John
"duchov" wrote:
> Need urgent help. The sql 2000 agent service never runs. Tried to run under a
> domain admin acct which belongs to SysAdmins role and still doesn't run. Ran
> the sqlagent with -c -v switches from command line and got foll. 2 errors:
> [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> [sqlstate 42000] (connisloginsysadmin)
> [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> but '(Unknown)' is not a member of the SysAdmin role
> Tried the microsoft kb solns and still not running. Need this resolved
> urgently. Pls help. Thks. We use sql 2000, sp4.|||"John Bell" wrote:
> Hi
> I don't see collate in any of the statements issued when SQL Agent is
> stopped or started. You may want to profile the agent starting (including
> errors and exception events) to see what is being processed.
> Is there any other messages in the SQL Server logs?
> Have you tried running this as the system account?
> John
> John
> "duchov" wrote:
> > Need urgent help. The sql 2000 agent service never runs. Tried to run under a
> > domain admin acct which belongs to SysAdmins role and still doesn't run. Ran
> > the sqlagent with -c -v switches from command line and got foll. 2 errors:
> >
> > [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> >
> > [sqlstate 42000] (connisloginsysadmin)
> >
> > [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> >
> > but '(Unknown)' is not a member of the SysAdmin role
> > Tried the microsoft kb solns and still not running. Need this resolved
> > urgently. Pls help. Thks. We use sql 2000, sp4.|||Hi John/Uri
setting the agent acct from either EM or service ctrl mngr has same result.
Only other errors in the sql logs are:
1) Operating system error = 31(A device attached to the system is not
functioning.).
This error is in multiple logs though not the current log. Any ideas on this?
2) spid52 Error: 15457, Severity: 0, State: 1 (a sql support site said You
will see that 15457 error
popup if you pull up your SQL Server properties.)
3) Configuration option 'show advanced options' changed from 1 to 1. Run the
RECONFIGURE statement
to install..
Errors 2 & 3 are in today's log only and seems to be b/c checked the sql
server properties
Initially agent was under local sys acct n it never ran which is y tried a
domain admin acct but still no success
How do I profile the agent startup/shutdown? I ran a trace via sql profiler
(included errors/exceptions) and manually tried to start agent. the trace
showed 2 records under an application name of sqlAgent - initial boot probe
with no info really. is this what u meant?
Reason this is important is b/c I scheduled some nightly sql backups to disk
n they never run b/c the agent service never starts. Hope u can help.
"John Bell" wrote:
> Hi
> I don't see collate in any of the statements issued when SQL Agent is
> stopped or started. You may want to profile the agent starting (including
> errors and exception events) to see what is being processed.
> Is there any other messages in the SQL Server logs?
> Have you tried running this as the system account?
> John
> John
> "duchov" wrote:
> > Need urgent help. The sql 2000 agent service never runs. Tried to run under a
> > domain admin acct which belongs to SysAdmins role and still doesn't run. Ran
> > the sqlagent with -c -v switches from command line and got foll. 2 errors:
> >
> > [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> >
> > [sqlstate 42000] (connisloginsysadmin)
> >
> > [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> >
> > but '(Unknown)' is not a member of the SysAdmin role
> > Tried the microsoft kb solns and still not running. Need this resolved
> > urgently. Pls help. Thks. We use sql 2000, sp4.|||Hi
An Operating System Errors seems like the problem is external to SQL server,
is there anything in the System Event logs?
John
"duchov" <duchov@.discussions.microsoft.com> wrote in message
news:885311AD-1FAC-4745-9430-D1F1A573796E@.microsoft.com...
> Hi John/Uri
> setting the agent acct from either EM or service ctrl mngr has same
> result.
> Only other errors in the sql logs are:
> 1) Operating system error = 31(A device attached to the system is not
> functioning.).
> This error is in multiple logs though not the current log. Any ideas on
> this?
> 2) spid52 Error: 15457, Severity: 0, State: 1 (a sql support site said You
> will see that 15457 error
> popup if you pull up your SQL Server properties.)
> 3) Configuration option 'show advanced options' changed from 1 to 1. Run
> the
> RECONFIGURE statement
> to install..
> Errors 2 & 3 are in today's log only and seems to be b/c checked the sql
> server properties
> Initially agent was under local sys acct n it never ran which is y tried a
> domain admin acct but still no success
> How do I profile the agent startup/shutdown? I ran a trace via sql
> profiler
> (included errors/exceptions) and manually tried to start agent. the trace
> showed 2 records under an application name of sqlAgent - initial boot
> probe
> with no info really. is this what u meant?
> Reason this is important is b/c I scheduled some nightly sql backups to
> disk
> n they never run b/c the agent service never starts. Hope u can help.
> "John Bell" wrote:
>> Hi
>> I don't see collate in any of the statements issued when SQL Agent is
>> stopped or started. You may want to profile the agent starting (including
>> errors and exception events) to see what is being processed.
>> Is there any other messages in the SQL Server logs?
>> Have you tried running this as the system account?
>> John
>> John
>> "duchov" wrote:
>> > Need urgent help. The sql 2000 agent service never runs. Tried to run
>> > under a
>> > domain admin acct which belongs to SysAdmins role and still doesn't
>> > run. Ran
>> > the sqlagent with -c -v switches from command line and got foll. 2
>> > errors:
>> >
>> > [298] sql server error 170, line 47: incorrect syntax near 'collate'.
>> >
>> > [sqlstate 42000] (connisloginsysadmin)
>> >
>> > [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
>> >
>> > but '(Unknown)' is not a member of the SysAdmin role
>> > Tried the microsoft kb solns and still not running. Need this resolved
>> > urgently. Pls help. Thks. We use sql 2000, sp4.
Subscribe to:
Posts (Atom)