I have a Windows 2003 server running SQL 2000 SP4. I want to start setting
up email alerts and reporting on the SQL server. The network admin team is
not ok with installing any mail client. Is there any other way to have
email alerts setup without installing any mail client?use http://www.sqldev.net/xp/xpsmtp.htm
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"docsql" <docsql@.noemail.nospam> wrote in message
news:OLBxJoIHGHA.2444@.TK2MSFTNGP11.phx.gbl...
>I have a Windows 2003 server running SQL 2000 SP4. I want to start setting
>up email alerts and reporting on the SQL server. The network admin team is
>not ok with installing any mail client. Is there any other way to have
>email alerts setup without installing any mail client?
>
>|||You can use http://www.karaszi.com/SQLServer/util_smtp_alerter.asp. But I haven't looked at the code
for a long while now. If you want to use this and run into problem, I can provide you with source
code (VB.NET) so you can go in and fix stuff.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"docsql" <docsql@.noemail.nospam> wrote in message news:OLBxJoIHGHA.2444@.TK2MSFTNGP11.phx.gbl...
>I have a Windows 2003 server running SQL 2000 SP4. I want to start setting up email alerts and
>reporting on the SQL server. The network admin team is not ok with installing any mail client. Is
>there any other way to have email alerts setup without installing any mail client?
>
>
Showing posts with label admin. Show all posts
Showing posts with label admin. Show all posts
Sunday, March 25, 2012
Alerts
I have a Windows 2003 server running SQL 2000 SP4. I want to start setting
up email alerts and reporting on the SQL server. The network admin team is
not ok with installing any mail client. Is there any other way to have
email alerts setup without installing any mail client?use http://www.sqldev.net/xp/xpsmtp.htm
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"docsql" <docsql@.noemail.nospam> wrote in message
news:OLBxJoIHGHA.2444@.TK2MSFTNGP11.phx.gbl...
>I have a Windows 2003 server running SQL 2000 SP4. I want to start setting
>up email alerts and reporting on the SQL server. The network admin team is
>not ok with installing any mail client. Is there any other way to have
>email alerts setup without installing any mail client?
>
>|||You can use http://www.karaszi.com/SQLServer/util_smtp_alerter.asp. But I ha
ven't looked at the code
for a long while now. If you want to use this and run into problem, I can pr
ovide you with source
code (VB.NET) so you can go in and fix stuff.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"docsql" <docsql@.noemail.nospam> wrote in message news:OLBxJoIHGHA.2444@.TK2MSFTNGP11.phx.gbl
..
>I have a Windows 2003 server running SQL 2000 SP4. I want to start setting
up email alerts and
>reporting on the SQL server. The network admin team is not ok with install
ing any mail client. Is
>there any other way to have email alerts setup without installing any mail
client?
>
>
up email alerts and reporting on the SQL server. The network admin team is
not ok with installing any mail client. Is there any other way to have
email alerts setup without installing any mail client?use http://www.sqldev.net/xp/xpsmtp.htm
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"docsql" <docsql@.noemail.nospam> wrote in message
news:OLBxJoIHGHA.2444@.TK2MSFTNGP11.phx.gbl...
>I have a Windows 2003 server running SQL 2000 SP4. I want to start setting
>up email alerts and reporting on the SQL server. The network admin team is
>not ok with installing any mail client. Is there any other way to have
>email alerts setup without installing any mail client?
>
>|||You can use http://www.karaszi.com/SQLServer/util_smtp_alerter.asp. But I ha
ven't looked at the code
for a long while now. If you want to use this and run into problem, I can pr
ovide you with source
code (VB.NET) so you can go in and fix stuff.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"docsql" <docsql@.noemail.nospam> wrote in message news:OLBxJoIHGHA.2444@.TK2MSFTNGP11.phx.gbl
..
>I have a Windows 2003 server running SQL 2000 SP4. I want to start setting
up email alerts and
>reporting on the SQL server. The network admin team is not ok with install
ing any mail client. Is
>there any other way to have email alerts setup without installing any mail
client?
>
>
Alerts
I have a Windows 2003 server running SQL 2000 SP4. I want to start setting
up email alerts and reporting on the SQL server. The network admin team is
not ok with installing any mail client. Is there any other way to have
email alerts setup without installing any mail client?
use http://www.sqldev.net/xp/xpsmtp.htm
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"docsql" <docsql@.noemail.nospam> wrote in message
news:OLBxJoIHGHA.2444@.TK2MSFTNGP11.phx.gbl...
>I have a Windows 2003 server running SQL 2000 SP4. I want to start setting
>up email alerts and reporting on the SQL server. The network admin team is
>not ok with installing any mail client. Is there any other way to have
>email alerts setup without installing any mail client?
>
>
|||You can use http://www.karaszi.com/SQLServer/util_smtp_alerter.asp. But I haven't looked at the code
for a long while now. If you want to use this and run into problem, I can provide you with source
code (VB.NET) so you can go in and fix stuff.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"docsql" <docsql@.noemail.nospam> wrote in message news:OLBxJoIHGHA.2444@.TK2MSFTNGP11.phx.gbl...
>I have a Windows 2003 server running SQL 2000 SP4. I want to start setting up email alerts and
>reporting on the SQL server. The network admin team is not ok with installing any mail client. Is
>there any other way to have email alerts setup without installing any mail client?
>
>
up email alerts and reporting on the SQL server. The network admin team is
not ok with installing any mail client. Is there any other way to have
email alerts setup without installing any mail client?
use http://www.sqldev.net/xp/xpsmtp.htm
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"docsql" <docsql@.noemail.nospam> wrote in message
news:OLBxJoIHGHA.2444@.TK2MSFTNGP11.phx.gbl...
>I have a Windows 2003 server running SQL 2000 SP4. I want to start setting
>up email alerts and reporting on the SQL server. The network admin team is
>not ok with installing any mail client. Is there any other way to have
>email alerts setup without installing any mail client?
>
>
|||You can use http://www.karaszi.com/SQLServer/util_smtp_alerter.asp. But I haven't looked at the code
for a long while now. If you want to use this and run into problem, I can provide you with source
code (VB.NET) so you can go in and fix stuff.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"docsql" <docsql@.noemail.nospam> wrote in message news:OLBxJoIHGHA.2444@.TK2MSFTNGP11.phx.gbl...
>I have a Windows 2003 server running SQL 2000 SP4. I want to start setting up email alerts and
>reporting on the SQL server. The network admin team is not ok with installing any mail client. Is
>there any other way to have email alerts setup without installing any mail client?
>
>
Sunday, February 19, 2012
after system restore the agent does not start
Hi group,
we have a server that had a server restore (near mirror, the system admin had to work out a few kinks). After the restore, the sql server agent does not start. When trying start it in service, it appears to be trying to start, but at the end the MMC gives a message
Could not start the SQLSERVERAGENT service on local computer. The service did not return an error. This could be an internal error or an internal service error.
Window event log shows the following error:
The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: 17050, initerrlog: Could not open error log file 'e:\MSSQL\log\ERRORLOG'. Operating system error = 32(The process cannot access the file because it is being used by another process.).
Can someone offer the fix? Thanks.
The following is the configuration:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 3)
Quentin
The log mentioned, is the normal name for the SQL Server error log... It looks like SQL is trying to open it a second time, (as if you have 2 instances of SQL Server trying to write to the same log file)... THis can be changed in SEM startup properties...
However it might be possible that your SQL Agent is trying to open the log ( in SEM right click SQL Agent and go to properties to discover the log name it is using..)
All in all it looks to me that the error you are showing is not related to the SQL Agent not starting...Ensure the agent is using an NT login that is a SQL Server administrator.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's community of SQL Server professionals.
www.sqlpass.org
"Quentin Ran" <ab@.who.com> wrote in message news:OwDGnstQEHA.1960@.TK2MSFTNGP10.phx.gbl...
Hi group,
we have a server that had a server restore (near mirror, the system admin had to work out a few kinks). After the restore, the sql server agent does not start. When trying start it in service, it appears to be trying to start, but at the end the MMC gives a message
Could not start the SQLSERVERAGENT service on local computer. The service did not return an error. This could be an internal error or an internal service error.
Window event log shows the following error:
The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: 17050, initerrlog: Could not open error log file 'e:\MSSQL\log\ERRORLOG'. Operating system error = 32(The process cannot access the file because it is being used by another process.).
Can someone offer the fix? Thanks.
The following is the configuration:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 3)
Quentin
|||>>The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer.
sounds like the sqlagent thinks it's running on a different computer.
does this restored server have a different name than the original
server?
[vbcol=seagreen]
system error = 32(The process cannot access the file because it is being
used by another process.).
this, as the other poster pointed out, sounds like something is using
that log file. that log file is for sqlserver. you should specify a
different log file for the agent, generally should be something like
e:\mssql\log\sqlagent.out
Quentin Ran wrote:
> Hi group, we have a server that had a server restore (near mirror, the
> system admin had to work out a few kinks). After the restore, the sql
> server agent does not start. When trying start it in service, it
> appears to be trying to start, but at the end the MMC gives a
> message Could not start the SQLSERVERAGENT service on local computer.
> The service did not return an error. This could be an internal error
> or an internal service error. Window event log shows the following
> error: The description for Event ID ( 17055 ) in Source ( MSSQLSERVER
> ) cannot be found. The local computer may not have the necessary
> registry information or message DLL files to display messages from a
> remote computer. The following information is part of the event:
> 17050, initerrlog: Could not open error log file
> 'e:\MSSQL\log\ERRORLOG'. Operating system error = 32(The process
> cannot access the file because it is being used by another
> process.). Can someone offer the fix? Thanks. The following is the
> configuration: Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> May 31 2003 16:08:15
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack
> 3) Quentin
|||Thanks for both responses.
The restored server has exactly the same name as before. SQL Server Agent
is running off a server admin account.
SQL Server Service uses the error log file e:\MSSQL\log\ERRORLOG, and SQL
Server Agent Service uses the error log file E:\MSSQL\LOG\SQLAGENT.OUT. The
server service log seems to work at least half way -- when the server
service starts, it records what it was doing like opening the databases. In
fact it even recorded a restore of a database. The fact that it did not
record any failure of launching the server agent may be due to it never was
asked to do so -- Windows may not know to direct such event there. The
agent log actually also contains some entries after the starting of the
server service, but not those ones that agent service start failed.
Any additional comments?
Quentin
"ch" <ch@.dontemailme.com> wrote in message
news:40B4980C.B82ABDFE@.dontemailme.com...
> message DLL files to display messages from a remote computer.
> sounds like the sqlagent thinks it's running on a different computer.
> does this restored server have a different name than the original
> server?
>
> system error = 32(The process cannot access the file because it is being
> used by another process.).
> this, as the other poster pointed out, sounds like something is using
> that log file. that log file is for sqlserver. you should specify a
> different log file for the agent, generally should be something like
> e:\mssql\log\sqlagent.out
>
>
> Quentin Ran wrote:
>
|||maybe there are some registry settings incorrect due to the restore of the
server.
try this.
create an nt account that is local admin on the server.
using enterprise manager, change the sqlserver and sqlagent services to use that
account.
restart server. see if agent starts properly.
now go back using enterprise manager and reset your sqlserver and sqlagent
accounts to whatever account(s) they were using before.
restart server. see if agent starts properly.
if that doesn't work, see if you can get them to run properly using the system
account for the two services.
be sure to use enterprise manager to make changes to the accounts the services
use.
Quentin Ran wrote:
[vbcol=seagreen]
> Thanks for both responses.
> The restored server has exactly the same name as before. SQL Server Agent
> is running off a server admin account.
> SQL Server Service uses the error log file e:\MSSQL\log\ERRORLOG, and SQL
> Server Agent Service uses the error log file E:\MSSQL\LOG\SQLAGENT.OUT. The
> server service log seems to work at least half way -- when the server
> service starts, it records what it was doing like opening the databases. In
> fact it even recorded a restore of a database. The fact that it did not
> record any failure of launching the server agent may be due to it never was
> asked to do so -- Windows may not know to direct such event there. The
> agent log actually also contains some entries after the starting of the
> server service, but not those ones that agent service start failed.
> Any additional comments?
> Quentin
> "ch" <ch@.dontemailme.com> wrote in message
> news:40B4980C.B82ABDFE@.dontemailme.com...
|||Neither a local admin account nor the system account would start them.
There must be wrong registry settings, and we don't know which ones and the
correct values.
"ch" <ch@.dontemailme.com> wrote in message
news:40B4BCFB.1AF8E97B@.dontemailme.com...
> maybe there are some registry settings incorrect due to the restore of the
> server.
> try this.
> create an nt account that is local admin on the server.
> using enterprise manager, change the sqlserver and sqlagent services to
use that
> account.
> restart server. see if agent starts properly.
> now go back using enterprise manager and reset your sqlserver and sqlagent
> accounts to whatever account(s) they were using before.
> restart server. see if agent starts properly.
> if that doesn't work, see if you can get them to run properly using the
system
> account for the two services.
> be sure to use enterprise manager to make changes to the accounts the
services[vbcol=seagreen]
> use.
>
> Quentin Ran wrote:
Agent[vbcol=seagreen]
SQL[vbcol=seagreen]
The[vbcol=seagreen]
In[vbcol=seagreen]
was[vbcol=seagreen]
or[vbcol=seagreen]
being[vbcol=seagreen]
the[vbcol=seagreen]
sql[vbcol=seagreen]
computer.[vbcol=seagreen]
error[vbcol=seagreen]
MSSQLSERVER
>
|||check this article
http://support.microsoft.com/default...b;en-us;283811
Quentin Ran wrote:
[vbcol=seagreen]
> Neither a local admin account nor the system account would start them.
> There must be wrong registry settings, and we don't know which ones and the
> correct values.
> "ch" <ch@.dontemailme.com> wrote in message
> news:40B4BCFB.1AF8E97B@.dontemailme.com...
> use that
> system
> services
> Agent
> SQL
> The
> In
> was
> or
> being
> the
> sql
> computer.
> error
> MSSQLSERVER
|||Thanks.
"ch" <ch@.dontemailme.com> wrote in message
news:40B4D8F9.5C7C10D7@.dontemailme.com...[vbcol=seagreen]
> check this article
> http://support.microsoft.com/default...b;en-us;283811
>
> Quentin Ran wrote:
the[vbcol=seagreen]
the[vbcol=seagreen]
to[vbcol=seagreen]
sqlagent[vbcol=seagreen]
the[vbcol=seagreen]
and[vbcol=seagreen]
E:\MSSQL\LOG\SQLAGENT.OUT.[vbcol=seagreen]
server[vbcol=seagreen]
databases.[vbcol=seagreen]
not[vbcol=seagreen]
never[vbcol=seagreen]
The[vbcol=seagreen]
the[vbcol=seagreen]
information[vbcol=seagreen]
computer.[vbcol=seagreen]
using[vbcol=seagreen]
specify a[vbcol=seagreen]
like[vbcol=seagreen]
mirror,[vbcol=seagreen]
the[vbcol=seagreen]
it[vbcol=seagreen]
following[vbcol=seagreen]
from a[vbcol=seagreen]
the
>
we have a server that had a server restore (near mirror, the system admin had to work out a few kinks). After the restore, the sql server agent does not start. When trying start it in service, it appears to be trying to start, but at the end the MMC gives a message
Could not start the SQLSERVERAGENT service on local computer. The service did not return an error. This could be an internal error or an internal service error.
Window event log shows the following error:
The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: 17050, initerrlog: Could not open error log file 'e:\MSSQL\log\ERRORLOG'. Operating system error = 32(The process cannot access the file because it is being used by another process.).
Can someone offer the fix? Thanks.
The following is the configuration:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 3)
Quentin
The log mentioned, is the normal name for the SQL Server error log... It looks like SQL is trying to open it a second time, (as if you have 2 instances of SQL Server trying to write to the same log file)... THis can be changed in SEM startup properties...
However it might be possible that your SQL Agent is trying to open the log ( in SEM right click SQL Agent and go to properties to discover the log name it is using..)
All in all it looks to me that the error you are showing is not related to the SQL Agent not starting...Ensure the agent is using an NT login that is a SQL Server administrator.
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's community of SQL Server professionals.
www.sqlpass.org
"Quentin Ran" <ab@.who.com> wrote in message news:OwDGnstQEHA.1960@.TK2MSFTNGP10.phx.gbl...
Hi group,
we have a server that had a server restore (near mirror, the system admin had to work out a few kinks). After the restore, the sql server agent does not start. When trying start it in service, it appears to be trying to start, but at the end the MMC gives a message
Could not start the SQLSERVERAGENT service on local computer. The service did not return an error. This could be an internal error or an internal service error.
Window event log shows the following error:
The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: 17050, initerrlog: Could not open error log file 'e:\MSSQL\log\ERRORLOG'. Operating system error = 32(The process cannot access the file because it is being used by another process.).
Can someone offer the fix? Thanks.
The following is the configuration:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 3)
Quentin
|||>>The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer.
sounds like the sqlagent thinks it's running on a different computer.
does this restored server have a different name than the original
server?
[vbcol=seagreen]
system error = 32(The process cannot access the file because it is being
used by another process.).
this, as the other poster pointed out, sounds like something is using
that log file. that log file is for sqlserver. you should specify a
different log file for the agent, generally should be something like
e:\mssql\log\sqlagent.out
Quentin Ran wrote:
> Hi group, we have a server that had a server restore (near mirror, the
> system admin had to work out a few kinks). After the restore, the sql
> server agent does not start. When trying start it in service, it
> appears to be trying to start, but at the end the MMC gives a
> message Could not start the SQLSERVERAGENT service on local computer.
> The service did not return an error. This could be an internal error
> or an internal service error. Window event log shows the following
> error: The description for Event ID ( 17055 ) in Source ( MSSQLSERVER
> ) cannot be found. The local computer may not have the necessary
> registry information or message DLL files to display messages from a
> remote computer. The following information is part of the event:
> 17050, initerrlog: Could not open error log file
> 'e:\MSSQL\log\ERRORLOG'. Operating system error = 32(The process
> cannot access the file because it is being used by another
> process.). Can someone offer the fix? Thanks. The following is the
> configuration: Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> May 31 2003 16:08:15
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack
> 3) Quentin
|||Thanks for both responses.
The restored server has exactly the same name as before. SQL Server Agent
is running off a server admin account.
SQL Server Service uses the error log file e:\MSSQL\log\ERRORLOG, and SQL
Server Agent Service uses the error log file E:\MSSQL\LOG\SQLAGENT.OUT. The
server service log seems to work at least half way -- when the server
service starts, it records what it was doing like opening the databases. In
fact it even recorded a restore of a database. The fact that it did not
record any failure of launching the server agent may be due to it never was
asked to do so -- Windows may not know to direct such event there. The
agent log actually also contains some entries after the starting of the
server service, but not those ones that agent service start failed.
Any additional comments?
Quentin
"ch" <ch@.dontemailme.com> wrote in message
news:40B4980C.B82ABDFE@.dontemailme.com...
> message DLL files to display messages from a remote computer.
> sounds like the sqlagent thinks it's running on a different computer.
> does this restored server have a different name than the original
> server?
>
> system error = 32(The process cannot access the file because it is being
> used by another process.).
> this, as the other poster pointed out, sounds like something is using
> that log file. that log file is for sqlserver. you should specify a
> different log file for the agent, generally should be something like
> e:\mssql\log\sqlagent.out
>
>
> Quentin Ran wrote:
>
|||maybe there are some registry settings incorrect due to the restore of the
server.
try this.
create an nt account that is local admin on the server.
using enterprise manager, change the sqlserver and sqlagent services to use that
account.
restart server. see if agent starts properly.
now go back using enterprise manager and reset your sqlserver and sqlagent
accounts to whatever account(s) they were using before.
restart server. see if agent starts properly.
if that doesn't work, see if you can get them to run properly using the system
account for the two services.
be sure to use enterprise manager to make changes to the accounts the services
use.
Quentin Ran wrote:
[vbcol=seagreen]
> Thanks for both responses.
> The restored server has exactly the same name as before. SQL Server Agent
> is running off a server admin account.
> SQL Server Service uses the error log file e:\MSSQL\log\ERRORLOG, and SQL
> Server Agent Service uses the error log file E:\MSSQL\LOG\SQLAGENT.OUT. The
> server service log seems to work at least half way -- when the server
> service starts, it records what it was doing like opening the databases. In
> fact it even recorded a restore of a database. The fact that it did not
> record any failure of launching the server agent may be due to it never was
> asked to do so -- Windows may not know to direct such event there. The
> agent log actually also contains some entries after the starting of the
> server service, but not those ones that agent service start failed.
> Any additional comments?
> Quentin
> "ch" <ch@.dontemailme.com> wrote in message
> news:40B4980C.B82ABDFE@.dontemailme.com...
|||Neither a local admin account nor the system account would start them.
There must be wrong registry settings, and we don't know which ones and the
correct values.
"ch" <ch@.dontemailme.com> wrote in message
news:40B4BCFB.1AF8E97B@.dontemailme.com...
> maybe there are some registry settings incorrect due to the restore of the
> server.
> try this.
> create an nt account that is local admin on the server.
> using enterprise manager, change the sqlserver and sqlagent services to
use that
> account.
> restart server. see if agent starts properly.
> now go back using enterprise manager and reset your sqlserver and sqlagent
> accounts to whatever account(s) they were using before.
> restart server. see if agent starts properly.
> if that doesn't work, see if you can get them to run properly using the
system
> account for the two services.
> be sure to use enterprise manager to make changes to the accounts the
services[vbcol=seagreen]
> use.
>
> Quentin Ran wrote:
Agent[vbcol=seagreen]
SQL[vbcol=seagreen]
The[vbcol=seagreen]
In[vbcol=seagreen]
was[vbcol=seagreen]
or[vbcol=seagreen]
being[vbcol=seagreen]
the[vbcol=seagreen]
sql[vbcol=seagreen]
computer.[vbcol=seagreen]
error[vbcol=seagreen]
MSSQLSERVER
>
|||check this article
http://support.microsoft.com/default...b;en-us;283811
Quentin Ran wrote:
[vbcol=seagreen]
> Neither a local admin account nor the system account would start them.
> There must be wrong registry settings, and we don't know which ones and the
> correct values.
> "ch" <ch@.dontemailme.com> wrote in message
> news:40B4BCFB.1AF8E97B@.dontemailme.com...
> use that
> system
> services
> Agent
> SQL
> The
> In
> was
> or
> being
> the
> sql
> computer.
> error
> MSSQLSERVER
|||Thanks.
"ch" <ch@.dontemailme.com> wrote in message
news:40B4D8F9.5C7C10D7@.dontemailme.com...[vbcol=seagreen]
> check this article
> http://support.microsoft.com/default...b;en-us;283811
>
> Quentin Ran wrote:
the[vbcol=seagreen]
the[vbcol=seagreen]
to[vbcol=seagreen]
sqlagent[vbcol=seagreen]
the[vbcol=seagreen]
and[vbcol=seagreen]
E:\MSSQL\LOG\SQLAGENT.OUT.[vbcol=seagreen]
server[vbcol=seagreen]
databases.[vbcol=seagreen]
not[vbcol=seagreen]
never[vbcol=seagreen]
The[vbcol=seagreen]
the[vbcol=seagreen]
information[vbcol=seagreen]
computer.[vbcol=seagreen]
using[vbcol=seagreen]
specify a[vbcol=seagreen]
like[vbcol=seagreen]
mirror,[vbcol=seagreen]
the[vbcol=seagreen]
it[vbcol=seagreen]
following[vbcol=seagreen]
from a[vbcol=seagreen]
the
>
after system restore the agent does not start
Hi group,
we have a server that had a server restore (near mirror, the system admin ha
d to work out a few kinks). After the restore, the sql server agent does no
t start. When trying start it in service, it appears to be trying to start,
but at the end the MMC gives a message
Could not start the SQLSERVERAGENT service on local computer. The service d
id not return an error. This could be an internal error or an internal serv
ice error.
Window event log shows the following error:
The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be f
ound. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. The following
information is part of the event: 17050, initerrlog: Could not open error lo
g file 'e:\MSSQL\log\ERRORLOG'. Operating system error = 32(The process cann
ot access the file because it is being used by another process.).
Can someone offer the fix? Thanks.
The following is the configuration:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 3)
QuentinThe log mentioned, is the normal name for the SQL Server error log... It lo
oks like SQL is trying to open it a second time, (as if you have 2 instances
of SQL Server trying to write to the same log file)... THis can be changed
in SEM startup properties...
However it might be possible that your SQL Agent is trying to open the log (
in SEM right click SQL Agent and go to properties to discover the log name
it is using..)
All in all it looks to me that the error you are showing is not related to t
he SQL Agent not starting...Ensure the agent is using an NT login that is a
SQL Server administrator.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's communi
ty of SQL Server professionals.
www.sqlpass.org
"Quentin Ran" <ab@.who.com> wrote in message news:OwDGnstQEHA.1960@.TK2MSFTNGP
10.phx.gbl...
Hi group,
we have a server that had a server restore (near mirror, the system admin ha
d to work out a few kinks). After the restore, the sql server agent does no
t start. When trying start it in service, it appears to be trying to start,
but at the end the MMC gives a message
Could not start the SQLSERVERAGENT service on local computer. The service d
id not return an error. This could be an internal error or an internal serv
ice error.
Window event log shows the following error:
The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be f
ound. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. The following
information is part of the event: 17050, initerrlog: Could not open error lo
g file 'e:\MSSQL\log\ERRORLOG'. Operating system error = 32(The process cann
ot access the file because it is being used by another process.).
Can someone offer the fix? Thanks.
The following is the configuration:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 3)
Quentin|||>>The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer.
sounds like the sqlagent thinks it's running on a different computer.
does this restored server have a different name than the original
server?
system error = 32(The process cannot access the file because it is being
used by another process.).
this, as the other poster pointed out, sounds like something is using
that log file. that log file is for sqlserver. you should specify a
different log file for the agent, generally should be something like
e:\mssql\log\sqlagent.out
Quentin Ran wrote:
[vbcol=seagreen]
> Hi group, we have a server that had a server restore (near mirror, the
> system admin had to work out a few kinks). After the restore, the sql
> server agent does not start. When trying start it in service, it
> appears to be trying to start, but at the end the MMC gives a
> message Could not start the SQLSERVERAGENT service on local computer.
> The service did not return an error. This could be an internal error
> or an internal service error. Window event log shows the following
> error: The description for Event ID ( 17055 ) in Source ( MSSQLSERVER
> ) cannot be found. The local computer may not have the necessary
> registry information or message DLL files to display messages from a
> remote computer. The following information is part of the event:
> 17050, initerrlog: Could not open error log file
> 'e:\MSSQL\log\ERRORLOG'. Operating system error = 32(The process
> cannot access the file because it is being used by another
> process.). Can someone offer the fix? Thanks. The following is the
> configuration: Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> May 31 2003 16:08:15
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack
> 3) Quentin|||Thanks for both responses.
The restored server has exactly the same name as before. SQL Server Agent
is running off a server admin account.
SQL Server Service uses the error log file e:\MSSQL\log\ERRORLOG, and SQL
Server Agent Service uses the error log file E:\MSSQL\LOG\SQLAGENT.OUT. The
server service log seems to work at least half way -- when the server
service starts, it records what it was doing like opening the databases. In
fact it even recorded a restore of a database. The fact that it did not
record any failure of launching the server agent may be due to it never was
asked to do so -- Windows may not know to direct such event there. The
agent log actually also contains some entries after the starting of the
server service, but not those ones that agent service start failed.
Any additional comments?
Quentin
"ch" <ch@.dontemailme.com> wrote in message
news:40B4980C.B82ABDFE@.dontemailme.com...
> message DLL files to display messages from a remote computer.
> sounds like the sqlagent thinks it's running on a different computer.
> does this restored server have a different name than the original
> server?
>
> system error = 32(The process cannot access the file because it is being
> used by another process.).
> this, as the other poster pointed out, sounds like something is using
> that log file. that log file is for sqlserver. you should specify a
> different log file for the agent, generally should be something like
> e:\mssql\log\sqlagent.out
>
>
> Quentin Ran wrote:
>
>|||maybe there are some registry settings incorrect due to the restore of the
server.
try this.
create an nt account that is local admin on the server.
using enterprise manager, change the sqlserver and sqlagent services to use
that
account.
restart server. see if agent starts properly.
now go back using enterprise manager and reset your sqlserver and sqlagent
accounts to whatever account(s) they were using before.
restart server. see if agent starts properly.
if that doesn't work, see if you can get them to run properly using the syst
em
account for the two services.
be sure to use enterprise manager to make changes to the accounts the servic
es
use.
Quentin Ran wrote:
[vbcol=seagreen]
> Thanks for both responses.
> The restored server has exactly the same name as before. SQL Server Agent
> is running off a server admin account.
> SQL Server Service uses the error log file e:\MSSQL\log\ERRORLOG, and SQL
> Server Agent Service uses the error log file E:\MSSQL\LOG\SQLAGENT.OUT. T
he
> server service log seems to work at least half way -- when the server
> service starts, it records what it was doing like opening the databases.
In
> fact it even recorded a restore of a database. The fact that it did not
> record any failure of launching the server agent may be due to it never wa
s
> asked to do so -- Windows may not know to direct such event there. The
> agent log actually also contains some entries after the starting of the
> server service, but not those ones that agent service start failed.
> Any additional comments?
> Quentin
> "ch" <ch@.dontemailme.com> wrote in message
> news:40B4980C.B82ABDFE@.dontemailme.com...|||Neither a local admin account nor the system account would start them.
There must be wrong registry settings, and we don't know which ones and the
correct values.
"ch" <ch@.dontemailme.com> wrote in message
news:40B4BCFB.1AF8E97B@.dontemailme.com...
> maybe there are some registry settings incorrect due to the restore of the
> server.
> try this.
> create an nt account that is local admin on the server.
> using enterprise manager, change the sqlserver and sqlagent services to
use that
> account.
> restart server. see if agent starts properly.
> now go back using enterprise manager and reset your sqlserver and sqlagent
> accounts to whatever account(s) they were using before.
> restart server. see if agent starts properly.
> if that doesn't work, see if you can get them to run properly using the
system
> account for the two services.
> be sure to use enterprise manager to make changes to the accounts the
services
> use.
>
> Quentin Ran wrote:
>
Agent[vbcol=seagreen]
SQL[vbcol=seagreen]
The[vbcol=seagreen]
In[vbcol=seagreen]
was[vbcol=seagreen]
or[vbcol=seagreen]
being[vbcol=seagreen]
the[vbcol=seagreen]
sql[vbcol=seagreen]
computer.[vbcol=seagreen]
error[vbcol=seagreen]
MSSQLSERVER[vbcol=seagreen]
>|||check this article
http://support.microsoft.com/defaul...kb;en-us;283811
Quentin Ran wrote:
[vbcol=seagreen]
> Neither a local admin account nor the system account would start them.
> There must be wrong registry settings, and we don't know which ones and th
e
> correct values.
> "ch" <ch@.dontemailme.com> wrote in message
> news:40B4BCFB.1AF8E97B@.dontemailme.com...
> use that
> system
> services
> Agent
> SQL
> The
> In
> was
> or
> being
> the
> sql
> computer.
> error
> MSSQLSERVER|||Thanks.
"ch" <ch@.dontemailme.com> wrote in message
news:40B4D8F9.5C7C10D7@.dontemailme.com...
> check this article
> http://support.microsoft.com/defaul...kb;en-us;283811
>
> Quentin Ran wrote:
>
the[vbcol=seagreen]
the[vbcol=seagreen]
to[vbcol=seagreen]
sqlagent[vbcol=seagreen]
the[vbcol=seagreen]
and[vbcol=seagreen]
E:\MSSQL\LOG\SQLAGENT.OUT.[vbcol=seagreen]
server[vbcol=seagreen]
databases.[vbcol=seagreen]
not[vbcol=seagreen]
never[vbcol=seagreen]
The[vbcol=seagreen]
the[vbcol=seagreen]
information[vbcol=seagreen]
computer.[vbcol=seagreen]
using[vbcol=seagreen]
specify a[vbcol=seagreen]
like[vbcol=seagreen]
mirror,[vbcol=seagreen]
the[vbcol=seagreen]
it[vbcol=seagreen]
following[vbcol=seagreen]
from a[vbcol=seagreen]
the[vbcol=seagreen]
>
we have a server that had a server restore (near mirror, the system admin ha
d to work out a few kinks). After the restore, the sql server agent does no
t start. When trying start it in service, it appears to be trying to start,
but at the end the MMC gives a message
Could not start the SQLSERVERAGENT service on local computer. The service d
id not return an error. This could be an internal error or an internal serv
ice error.
Window event log shows the following error:
The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be f
ound. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. The following
information is part of the event: 17050, initerrlog: Could not open error lo
g file 'e:\MSSQL\log\ERRORLOG'. Operating system error = 32(The process cann
ot access the file because it is being used by another process.).
Can someone offer the fix? Thanks.
The following is the configuration:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 3)
QuentinThe log mentioned, is the normal name for the SQL Server error log... It lo
oks like SQL is trying to open it a second time, (as if you have 2 instances
of SQL Server trying to write to the same log file)... THis can be changed
in SEM startup properties...
However it might be possible that your SQL Agent is trying to open the log (
in SEM right click SQL Agent and go to properties to discover the log name
it is using..)
All in all it looks to me that the error you are showing is not related to t
he SQL Agent not starting...Ensure the agent is using an NT login that is a
SQL Server administrator.
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's communi
ty of SQL Server professionals.
www.sqlpass.org
"Quentin Ran" <ab@.who.com> wrote in message news:OwDGnstQEHA.1960@.TK2MSFTNGP
10.phx.gbl...
Hi group,
we have a server that had a server restore (near mirror, the system admin ha
d to work out a few kinks). After the restore, the sql server agent does no
t start. When trying start it in service, it appears to be trying to start,
but at the end the MMC gives a message
Could not start the SQLSERVERAGENT service on local computer. The service d
id not return an error. This could be an internal error or an internal serv
ice error.
Window event log shows the following error:
The description for Event ID ( 17055 ) in Source ( MSSQLSERVER ) cannot be f
ound. The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer. The following
information is part of the event: 17050, initerrlog: Could not open error lo
g file 'e:\MSSQL\log\ERRORLOG'. Operating system error = 32(The process cann
ot access the file because it is being used by another process.).
Can someone offer the fix? Thanks.
The following is the configuration:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 3)
Quentin|||>>The local computer may not have the necessary registry information or
message DLL files to display messages from a remote computer.
sounds like the sqlagent thinks it's running on a different computer.
does this restored server have a different name than the original
server?
system error = 32(The process cannot access the file because it is being
used by another process.).
this, as the other poster pointed out, sounds like something is using
that log file. that log file is for sqlserver. you should specify a
different log file for the agent, generally should be something like
e:\mssql\log\sqlagent.out
Quentin Ran wrote:
[vbcol=seagreen]
> Hi group, we have a server that had a server restore (near mirror, the
> system admin had to work out a few kinks). After the restore, the sql
> server agent does not start. When trying start it in service, it
> appears to be trying to start, but at the end the MMC gives a
> message Could not start the SQLSERVERAGENT service on local computer.
> The service did not return an error. This could be an internal error
> or an internal service error. Window event log shows the following
> error: The description for Event ID ( 17055 ) in Source ( MSSQLSERVER
> ) cannot be found. The local computer may not have the necessary
> registry information or message DLL files to display messages from a
> remote computer. The following information is part of the event:
> 17050, initerrlog: Could not open error log file
> 'e:\MSSQL\log\ERRORLOG'. Operating system error = 32(The process
> cannot access the file because it is being used by another
> process.). Can someone offer the fix? Thanks. The following is the
> configuration: Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
> May 31 2003 16:08:15
> Copyright (c) 1988-2003 Microsoft Corporation
> Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack
> 3) Quentin|||Thanks for both responses.
The restored server has exactly the same name as before. SQL Server Agent
is running off a server admin account.
SQL Server Service uses the error log file e:\MSSQL\log\ERRORLOG, and SQL
Server Agent Service uses the error log file E:\MSSQL\LOG\SQLAGENT.OUT. The
server service log seems to work at least half way -- when the server
service starts, it records what it was doing like opening the databases. In
fact it even recorded a restore of a database. The fact that it did not
record any failure of launching the server agent may be due to it never was
asked to do so -- Windows may not know to direct such event there. The
agent log actually also contains some entries after the starting of the
server service, but not those ones that agent service start failed.
Any additional comments?
Quentin
"ch" <ch@.dontemailme.com> wrote in message
news:40B4980C.B82ABDFE@.dontemailme.com...
> message DLL files to display messages from a remote computer.
> sounds like the sqlagent thinks it's running on a different computer.
> does this restored server have a different name than the original
> server?
>
> system error = 32(The process cannot access the file because it is being
> used by another process.).
> this, as the other poster pointed out, sounds like something is using
> that log file. that log file is for sqlserver. you should specify a
> different log file for the agent, generally should be something like
> e:\mssql\log\sqlagent.out
>
>
> Quentin Ran wrote:
>
>|||maybe there are some registry settings incorrect due to the restore of the
server.
try this.
create an nt account that is local admin on the server.
using enterprise manager, change the sqlserver and sqlagent services to use
that
account.
restart server. see if agent starts properly.
now go back using enterprise manager and reset your sqlserver and sqlagent
accounts to whatever account(s) they were using before.
restart server. see if agent starts properly.
if that doesn't work, see if you can get them to run properly using the syst
em
account for the two services.
be sure to use enterprise manager to make changes to the accounts the servic
es
use.
Quentin Ran wrote:
[vbcol=seagreen]
> Thanks for both responses.
> The restored server has exactly the same name as before. SQL Server Agent
> is running off a server admin account.
> SQL Server Service uses the error log file e:\MSSQL\log\ERRORLOG, and SQL
> Server Agent Service uses the error log file E:\MSSQL\LOG\SQLAGENT.OUT. T
he
> server service log seems to work at least half way -- when the server
> service starts, it records what it was doing like opening the databases.
In
> fact it even recorded a restore of a database. The fact that it did not
> record any failure of launching the server agent may be due to it never wa
s
> asked to do so -- Windows may not know to direct such event there. The
> agent log actually also contains some entries after the starting of the
> server service, but not those ones that agent service start failed.
> Any additional comments?
> Quentin
> "ch" <ch@.dontemailme.com> wrote in message
> news:40B4980C.B82ABDFE@.dontemailme.com...|||Neither a local admin account nor the system account would start them.
There must be wrong registry settings, and we don't know which ones and the
correct values.
"ch" <ch@.dontemailme.com> wrote in message
news:40B4BCFB.1AF8E97B@.dontemailme.com...
> maybe there are some registry settings incorrect due to the restore of the
> server.
> try this.
> create an nt account that is local admin on the server.
> using enterprise manager, change the sqlserver and sqlagent services to
use that
> account.
> restart server. see if agent starts properly.
> now go back using enterprise manager and reset your sqlserver and sqlagent
> accounts to whatever account(s) they were using before.
> restart server. see if agent starts properly.
> if that doesn't work, see if you can get them to run properly using the
system
> account for the two services.
> be sure to use enterprise manager to make changes to the accounts the
services
> use.
>
> Quentin Ran wrote:
>
Agent[vbcol=seagreen]
SQL[vbcol=seagreen]
The[vbcol=seagreen]
In[vbcol=seagreen]
was[vbcol=seagreen]
or[vbcol=seagreen]
being[vbcol=seagreen]
the[vbcol=seagreen]
sql[vbcol=seagreen]
computer.[vbcol=seagreen]
error[vbcol=seagreen]
MSSQLSERVER[vbcol=seagreen]
>|||check this article
http://support.microsoft.com/defaul...kb;en-us;283811
Quentin Ran wrote:
[vbcol=seagreen]
> Neither a local admin account nor the system account would start them.
> There must be wrong registry settings, and we don't know which ones and th
e
> correct values.
> "ch" <ch@.dontemailme.com> wrote in message
> news:40B4BCFB.1AF8E97B@.dontemailme.com...
> use that
> system
> services
> Agent
> SQL
> The
> In
> was
> or
> being
> the
> sql
> computer.
> error
> MSSQLSERVER|||Thanks.
"ch" <ch@.dontemailme.com> wrote in message
news:40B4D8F9.5C7C10D7@.dontemailme.com...
> check this article
> http://support.microsoft.com/defaul...kb;en-us;283811
>
> Quentin Ran wrote:
>
the[vbcol=seagreen]
the[vbcol=seagreen]
to[vbcol=seagreen]
sqlagent[vbcol=seagreen]
the[vbcol=seagreen]
and[vbcol=seagreen]
E:\MSSQL\LOG\SQLAGENT.OUT.[vbcol=seagreen]
server[vbcol=seagreen]
databases.[vbcol=seagreen]
not[vbcol=seagreen]
never[vbcol=seagreen]
The[vbcol=seagreen]
the[vbcol=seagreen]
information[vbcol=seagreen]
computer.[vbcol=seagreen]
using[vbcol=seagreen]
specify a[vbcol=seagreen]
like[vbcol=seagreen]
mirror,[vbcol=seagreen]
the[vbcol=seagreen]
it[vbcol=seagreen]
following[vbcol=seagreen]
from a[vbcol=seagreen]
the[vbcol=seagreen]
>
Monday, February 13, 2012
After I change Log on of SQL Server 2005, my SQL service agent can not start, any idea?
I use localsystem to start SQL 2005, and use a domain/user to start SQL 2005 agent, the user is an domain admin and local admin, which works.
I had problem to use openrowset, so I changed the SQL 2005 to use the same domain.user to start, which works, after that, I can use openrowset well, but now, I can not start SQL 2005 agent, I get error:
SQLServerAgent could not be started (reason: SQLServerAgent must be able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a member of the SysAdmin role).
and another enry in event viewer, not sure if they are related
SQL Server blocked access to procedure 'dbo.sp_sqlagent_get_startup_info' of component 'Agent XPs' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Agent XPs' by using sp_configure. For more information about enabling 'Agent XPs', see "Surface Area Configuration" in SQL Server Books Online.
It is SQL 2005 on window 2003.
Any idea how to fix it?
thanks!
In sql 2005 the agent xps are turned 'off by default' so I think the first thing you need to do is turn on the Agent Xps.
exec sp_configure 'show advanced options' , 1 ;reconfigure
exec sp_configure 'Agent XPs',1;reconfigure
go
hth,
-Steven Gott
S/DET
SQL Server
p.s. SQL 2005 does not need to run as a domain admin , It would be much safer if you set it to run as a normal user b/c the high privilleges of the service account combined with some of the xps like xp_cmdshell allow a dba who is sysadmin to manipulate your domain as the domain admin.
|||
I had problem to use openrowset, so I changed the SQL 2005 to use the same domain.user to start, which works, after that, I can use openrowset well ...
I suspect that your problem with using OPENROWSET had to do with permissions to access the file you were attempting to open. Since your original SQL Server account was not a domain account, you would not have been able to access domain resources, including files, with the MSSQL service. Once you changed to use the domain account that was set up for SQL Agent, the OPENROWSET worked since it could now access domain resources.
|||Hi,
I think you mixed SQL server account with SQL server agent account, I think it is SQL server account that will access the files for openrowset.
Well, I changed the account for my SQL server from local system to a domain admin, that solves the openrowset problem, but more other problem come in.
First, the Memory used by SQL keeps going up, reached 1.7G, I remember how to solve this, I need give the account "lock page in memory" permission, that solves it
Second, I got error, my CLR reports problem, it says
A .NET Framework error occurred during execution of user-defined routine or aggregate "linkclr_x_pdf_createpdf":
System.DllNotFoundException: Unable to load DLL 'ABCpdfCE6.dll': Not enough storage is available to process this command.
When the error happens, the SQL only use 170M memory, the server has 3G memory.
Really a big problem, how can I just set an account with fully localsystem permssion plus permission to access domain file? Since the localsystem worked fine except the openrowset problem.
thanks
|||My God, after caused me so much trouble, I found the openrowset may have nothing to do with the account. It only works for some time after each restart, even with local system, it works fine, it can access remote files, maybe because I set the permission to the sql server.
But the issue is it stops working after some time, someone said to set permission to temp folder, doesn't work for me yet.
Isn't that a big bug? could someone from the SQL team to shed a light here? I havn't been asking for the solution for many months.
|||Steve,
when I run this command I get
Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
Msg 5845, Level 16, State 1, Line 1
Address Windowing Extensions (AWE) requires the 'lock pages in memory' privilege which is not currently present in the access token of the process.
It just will not let me turn it on ..... is there any other way to change the option?
thank you
mitch
|||You can try using the SQL Server Surface Area Configuration tool.
It will be in the configuration Tools folder under SQL Server
HTH,
-Steven Gott
SDE/T
SQL Server
|||Steve,
I tried this and I assume its the ole component? but I was able to fix some of the problem but it says it is not part of the sysadmin role which it is. I just dont know where to go from here.
thanks
mitch
After I change Log on of SQL Server 2005, my SQL service agent can not start, any idea?
I use localsystem to start SQL 2005, and use a domain/user to start SQL 2005 agent, the user is an domain admin and local admin, which works.
I had problem to use openrowset, so I changed the SQL 2005 to use the same domain.user to start, which works, after that, I can use openrowset well, but now, I can not start SQL 2005 agent, I get error:
SQLServerAgent could not be started (reason: SQLServerAgent must be able to connect to SQLServer as SysAdmin, but '(Unknown)' is not a member of the SysAdmin role).
and another enry in event viewer, not sure if they are related
SQL Server blocked access to procedure 'dbo.sp_sqlagent_get_startup_info' of component 'Agent XPs' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Agent XPs' by using sp_configure. For more information about enabling 'Agent XPs', see "Surface Area Configuration" in SQL Server Books Online.
It is SQL 2005 on window 2003.
Any idea how to fix it?
thanks!
In sql 2005 the agent xps are turned 'off by default' so I think the first thing you need to do is turn on the Agent Xps.
exec sp_configure 'show advanced options' , 1 ;reconfigure
exec sp_configure 'Agent XPs',1;reconfigure
go
hth,
-Steven Gott
S/DET
SQL Server
p.s. SQL 2005 does not need to run as a domain admin , It would be much safer if you set it to run as a normal user b/c the high privilleges of the service account combined with some of the xps like xp_cmdshell allow a dba who is sysadmin to manipulate your domain as the domain admin.
|||
I had problem to use openrowset, so I changed the SQL 2005 to use the same domain.user to start, which works, after that, I can use openrowset well ...
I suspect that your problem with using OPENROWSET had to do with permissions to access the file you were attempting to open. Since your original SQL Server account was not a domain account, you would not have been able to access domain resources, including files, with the MSSQL service. Once you changed to use the domain account that was set up for SQL Agent, the OPENROWSET worked since it could now access domain resources.
|||Hi,
I think you mixed SQL server account with SQL server agent account, I think it is SQL server account that will access the files for openrowset.
Well, I changed the account for my SQL server from local system to a domain admin, that solves the openrowset problem, but more other problem come in.
First, the Memory used by SQL keeps going up, reached 1.7G, I remember how to solve this, I need give the account "lock page in memory" permission, that solves it
Second, I got error, my CLR reports problem, it says
A .NET Framework error occurred during execution of user-defined routine or aggregate "linkclr_x_pdf_createpdf":
System.DllNotFoundException: Unable to load DLL 'ABCpdfCE6.dll': Not enough storage is available to process this command.
When the error happens, the SQL only use 170M memory, the server has 3G memory.
Really a big problem, how can I just set an account with fully localsystem permssion plus permission to access domain file? Since the localsystem worked fine except the openrowset problem.
thanks
|||My God, after caused me so much trouble, I found the openrowset may have nothing to do with the account. It only works for some time after each restart, even with local system, it works fine, it can access remote files, maybe because I set the permission to the sql server.
But the issue is it stops working after some time, someone said to set permission to temp folder, doesn't work for me yet.
Isn't that a big bug? could someone from the SQL team to shed a light here? I havn't been asking for the solution for many months.
|||Steve,
when I run this command I get
Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install.
Msg 5845, Level 16, State 1, Line 1
Address Windowing Extensions (AWE) requires the 'lock pages in memory' privilege which is not currently present in the access token of the process.
It just will not let me turn it on ..... is there any other way to change the option?
thank you
mitch
|||You can try using the SQL Server Surface Area Configuration tool.
It will be in the configuration Tools folder under SQL Server
HTH,
-Steven Gott
SDE/T
SQL Server
|||Steve,
I tried this and I assume its the ole component? but I was able to fix some of the problem but it says it is not part of the sysadmin role which it is. I just dont know where to go from here.
thanks
mitch
Subscribe to:
Posts (Atom)