Error when starting SQLSERVER AGENT

Hello!, I have the following error message when I want to start the
sqlserver agent: "The SQLSERVER AGENT SERVICE on local computer started and
then stopped. Some services stop automatically if they have no work to do,
for example the performance logs and alerts service"
In this server I have windows 2003 and sql server 2000 (it has the service
pack already), actually some days ago it had no problem, suddenly the jobs
did not run so I realized this problem.
Help!!!!!!!!
Message posted via http://www.droptable.com
The MSDB database has some problem,maybe it is running in single user mode.
maybe you moved it from another BD check the MSDB for any thing out of the
normal.

Error when starting SQLSERVER AGENT

Hello!, I have the following error message when I want to start the
sqlserver agent: "The SQLSERVER AGENT SERVICE on local computer started and
then stopped. Some services stop automatically if they have no work to do,
for example the performance logs and alerts service"
In this server I have windows 2003 and sql server 2000 (it has the service
pack already), actually some days ago it had no problem, suddenly the jobs
did not run so I realized this problem.
Help!!!!!!!!
--
Message posted via http://www.sqlmonster.comThe MSDB database has some problem,maybe it is running in single user mode.
maybe you moved it from another BD check the MSDB for any thing out of the
normal.

Error when starting SQLSERVER AGENT

Hello!, I have the following error message when I want to start the
sqlserver agent: "The SQLSERVER AGENT SERVICE on local computer started and
then stopped. Some services stop automatically if they have no work to do,
for example the performance logs and alerts service"
In this server I have windows 2003 and sql server 2000 (it has the service
pack already), actually some days ago it had no problem, suddenly the jobs
did not run so I realized this problem.
Help!!!!!!!!
Message posted via http://www.droptable.comThe MSDB database has some problem,maybe it is running in single user mode.
maybe you moved it from another BD check the MSDB for any thing out of the
normal.sql

error when running the DTSRUN command

Hi
We're using SqlServer 2000.

I want to run a DTS using the DTSRUN command.
The commmand is inside a ".bat" file which my application is running
from an SQL client.
No matter how I run it from the client it fails giving me the message:

[ConnectionOpen (Connect()).]SQL Server does not exist or access denied

I've tried to run it from the client from the application, from the
command prompt and it fails.
I went into enterprise on the client and tried to run the DTS from
there. The run failed already on the 1st step which is a call to a
stored procedure, also giving me the same message. This really stuck me
as wierd because in enterprise I'm accessing the server successfully so
why the above messgae. It identifies the server and I am accessing it.

Because it failed on the 1st step which is a call to a stored procedure
I tried running the sp from within query analyzer and it succeeded.

Has anyone got any idea what the problem is and ghow to solve it.

Thanks !

David GreenbergDavid Greenberg (davidgr@.iba.org.il) writes:

Quote:

Originally Posted by

I want to run a DTS using the DTSRUN command.
The commmand is inside a ".bat" file which my application is running
from an SQL client.
No matter how I run it from the client it fails giving me the message:
>
[ConnectionOpen (Connect()).]SQL Server does not exist or access denied
>
I've tried to run it from the client from the application, from the
command prompt and it fails.
I went into enterprise on the client and tried to run the DTS from
there. The run failed already on the 1st step which is a call to a
stored procedure, also giving me the same message. This really stuck me
as wierd because in enterprise I'm accessing the server successfully so
why the above messgae. It identifies the server and I am accessing it.
>
Because it failed on the 1st step which is a call to a stored procedure
I tried running the sp from within query analyzer and it succeeded.
>
Has anyone got any idea what the problem is and ghow to solve it.

You can't accuse me to know too much about DTS, but I see that a
DTS package has connection properties. I would assume that you can
have a package on server A, and run it against server B.

So I would check the connection properties of the package (or the step,
as different task surely must be able to connect to different servers).

The error message simply means that you are trying to connect to a
server that is not available. (Not running, misspelled, a firewall
in the way etc.)

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

error when connect to sqlserver from another machine

hi ..

i install sqlserver and make app with vb6 using ADO to connect to the database and successfully

i put that application on another pc on the network
when i open it it says "can't login computername\guest" ?!!

any help

thanks in advance.any answers|||Are both of your pcs on a domain or a workgroup? If it's not domain, you need to create a same account/password pair on both machines and use that account to login.|||thanks

Xinwei Hong for reply

the two machines on a workgroup so .. could you explain pcs under domain in few lines ?
now i will create two users on the two machines and tell you later

thanks in advance.
|||By "pcs under domain", I mean whether your PC is under a domain which is usually used in median/large company. In this case, domain controller will help you do a lot of things.|||thanks for reply

you says i can do a lot of things if i'm under domain like what ?and what is the domain controler ? could you explain ?

and if you have short time i can talk to you in messanger it will be kind from you

thanks|||i make 2 users with same name but ..
the same problem occurs ?|||It's hard to describe "domain controller" and related stuff in short words. I recommend you find some documents related to Windows Networks to read.

Are you sure your client is running under the user account you created and you used that account to login to the server? It means you may need to login the client Windows system and run your client app under that account. If you user Administrator or even logon the computer without a user/password, it won't work.|||is this means that i need a password for administrator user to login to the database server ?|||Not necessary. SQL server runs as a service under various account(e.g. network service, local system, administrator account, etc.).

Error using RDO query object with SQL Server 7.0

While using RDO(msrdo20.dll) query object to create a temporary table in SQL
Server 7.0(with SP4), I am gettng the error:
Code '40002': Error: S0001: :[Microsoft][ODBC SQL Server Driver][
;SQL Server]
There is already an object name '#<name of temporary table>' in the database
.
Please help me to resolve this.
Thanks.Temporary objects persist until they go out of scope or are explicitly
dropped. If you are in the midst of development, you probably have a
pre-existing creation of the object on your current connection that you have
yet reseted nor have you explicitly dropped the table.
Sincerely,
Anthony Thomas
"ak3010" <ak3010@.discussions.microsoft.com> wrote in message
news:FD8956BA-5547-402C-88E5-2981F0A1860B@.microsoft.com...
While using RDO(msrdo20.dll) query object to create a temporary table in SQL
Server 7.0(with SP4), I am gettng the error:
Code '40002': Error: S0001: :[Microsoft][ODBC SQL Server Driver][
;SQL Server]
There is already an object name '#<name of temporary table>' in the
database.
Please help me to resolve this.
Thanks.|||While using RDO(msrdo20.dll) query object to create a temporary table in SQL
Server 7.0(with SP4), I am gettng the error:
Error: 40002: :[Microsoft][ODBC SQL Server Driver][SQL Server]
The cursor was not declared
From http://www.google.co.in/search?q=40...elopmentnow.com

Error using RDO query object with SQL Server 7.0

While using RDO(msrdo20.dll) query object to create a temporary table in SQL
Server 7.0(with SP4), I am gettng the error:
Code '40002': Error: S0001: :[Microsoft][ODBC SQL Server Driver][SQL Server]
There is already an object name '#<name of temporary table>' in the database.
Please help me to resolve this.
Thanks.
Temporary objects persist until they go out of scope or are explicitly
dropped. If you are in the midst of development, you probably have a
pre-existing creation of the object on your current connection that you have
yet reseted nor have you explicitly dropped the table.
Sincerely,
Anthony Thomas

"ak3010" <ak3010@.discussions.microsoft.com> wrote in message
news:FD8956BA-5547-402C-88E5-2981F0A1860B@.microsoft.com...
While using RDO(msrdo20.dll) query object to create a temporary table in SQL
Server 7.0(with SP4), I am gettng the error:
Code '40002': Error: S0001: :[Microsoft][ODBC SQL Server Driver][SQL Server]
There is already an object name '#<name of temporary table>' in the
database.
Please help me to resolve this.
Thanks.
|||While using RDO(msrdo20.dll) query object to create a temporary table in SQL
Server 7.0(with SP4), I am gettng the error:
Error: 40002: :[Microsoft][ODBC SQL Server Driver][SQL Server]
The cursor was not declared
From http://www.google.co.in/search?q=40002+++msrdo20.dll&hl=en&start=10&sa=N
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com

Error using Microsoft.SqlServer.ManagedDTS.dll

Hi,

I picked the Microsoft.SQLServer.ManagedDTS.dll from following folder:

C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SqlServer.ManagedDTS\9.0.242.0__89845dcd8080cc91>

Similarly picked Microsoft.SqlServer.DTSRuntimeWrap.dll also.

I added it as reference in my .NET application.

When I execute the program I get below error:

Retrieving the COM class factory for component with CLSID {E44847F1-FD8C-4251-B5DA-B04BB22E236E} failed due to the following error: 80040154.

Any Clue?

Application executes from a machine where SQL Server 2005 is not installed.

How to get the RunningPackages information back to a client PC?

HV

Hiral wrote:

Application executes from a machine where SQL Server 2005 is not installed.

How to get the RunningPackages information back to a client PC?

This seems like the most likely problem. You can only work with the SSIS runtime on machines where SSIS (a server component of SQL Server 2005) is installed. There is no redistributable package for SSIS like there was for DTS.

|||

Thank you Matthew.

But then what's the point giving Intergration Services Programming object model?

It's given by microsoft to program around packages.

Please refer the below links:

http://blogs.msdn.com/michen/default.aspx

http://msdn2.microsoft.com/zh-tw/library/ms136025.aspx

My point of concern is how do we get the dll "Microsoft.SqlServer.ManagedDTS.dll" ?

HV

|||

Hiral wrote:

Thank you Matthew.

But then what's the point giving Intergration Services Programming object model?

It's given by microsoft to program around packages.

Please refer the below links:

http://blogs.msdn.com/michen/default.aspx

http://msdn2.microsoft.com/zh-tw/library/ms136025.aspx

My point of concern is how do we get the dll "Microsoft.SqlServer.ManagedDTS.dll" ?

HV

You install SQL Server Integration Services. That is how you get Microsoft.SqlServer.ManagedDTS.dll. Both of the links you provided discuss using the SSIS object model, but neither (that I can see) says anything about installing this DLL on a non-SQL Server computer.

|||Here's another link that seems relevant: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1647966&SiteID=1&mode=1|||

Thank you Matthew.

I agree with you that the link I provided does not mention anything about having the ManagedDTS.dll without sql server installation.

That's the reason I have posted it so that I get some help on how to get that dll.

Another thing is though the links say that ManagedDTS.dll is shipped with SQL Server 2005, I searched for it on our database server and it was not found.

My point is how do I get this dll? Which installation will help me out for it? What is the process I should follow to get it?

HV

|||

Hiral wrote:

Thank you Matthew.

I agree with you that the link I provided does not mention anything about having the ManagedDTS.dll without sql server installation.

That's the reason I have posted it so that I get some help on how to get that dll.

Another thing is though the links say that ManagedDTS.dll is shipped with SQL Server 2005, I searched for it on our database server and it was not found.

My point is how do I get this dll? Which installation will help me out for it? What is the process I should follow to get it?

HV

You need to install SSIS explicitly. SSIS comes with Standard, Developer, and Enterprise versions of SQL Server 2005.

You get the dll by installing SSIS.|||

Thank you Phil.

The thing is SSIS is installed on our database server still we do not have Microsoft.SQLServer.ManagedDTS.dll on that machine.

Any clue on this?

Error starting SQLserver on windows 2000

When starting the SQLserver service on a Windows 2000 server, we get
following error:
17050 :
initerrlog: Could not open error log file
's:\MSSQL8\MSSQL\log\ERRORLOG'. Operating system error = 3(error not
found).
We're running SQL 2000 std ed.. This is no cluster, access rights on
file are correct, the file is not locked by another process.
I've compared registry settings with a working server (same config) and
there identical.
registry setting:
& #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSSQLServer\MSSQLServer\Parameter
s]
"SQLArg0"="-ds:\\MSSQL8\\MSSQL\\data\\master.mdf"
"SQLArg1"="-es:\\MSSQL8\\MSSQL\\log\\ERRORLOG"
"SQLArg2"="-ls:\\MSSQL8\\MSSQL\\data\\mastlog.ldf".
There's a local d, e and l-drive (No SAN)
Anyone has an idea what's going wrongHi Olivier
The parameters are expecting a S drive, where are the files supposed to be?
You could start sqlservr.exe from the command prompt and specify the correct
file names, see the topic "sqlservr Application" in Books Online and change
the values through Enterprise Manager, if you don't want to change the
registry directly.
John
"sqlservr Application"
"olivier.lammens@.gmail.com" wrote:

> When starting the SQLserver service on a Windows 2000 server, we get
> following error:
> 17050 :
> initerrlog: Could not open error log file
> 's:\MSSQL8\MSSQL\log\ERRORLOG'. Operating system error = 3(error not
> found).
> We're running SQL 2000 std ed.. This is no cluster, access rights on
> file are correct, the file is not locked by another process.
> I've compared registry settings with a working server (same config) and
> there identical.
> registry setting:
> & #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSSQLServer\MSSQLServer\Paramet
ers]
> "SQLArg0"="-ds:\\MSSQL8\\MSSQL\\data\\master.mdf"
> "SQLArg1"="-es:\\MSSQL8\\MSSQL\\log\\ERRORLOG"
> "SQLArg2"="-ls:\\MSSQL8\\MSSQL\\data\\mastlog.ldf".
> There's a local d, e and l-drive (No SAN)
> Anyone has an idea what's going wrong
>|||Hi Olivier
The parameters are expecting a S drive, where are the files supposed to be?
You could start sqlservr.exe from the command prompt and specify the correct
file names, see the topic "sqlservr Application" in Books Online and change
the values through Enterprise Manager, if you don't want to change the
registry directly.
John
"sqlservr Application"
"olivier.lammens@.gmail.com" wrote:

> When starting the SQLserver service on a Windows 2000 server, we get
> following error:
> 17050 :
> initerrlog: Could not open error log file
> 's:\MSSQL8\MSSQL\log\ERRORLOG'. Operating system error = 3(error not
> found).
> We're running SQL 2000 std ed.. This is no cluster, access rights on
> file are correct, the file is not locked by another process.
> I've compared registry settings with a working server (same config) and
> there identical.
> registry setting:
> & #91;HKEY_LOCAL_MACHINE\SOFTWARE\Microsof
t\MSSQLServer\MSSQLServer\Paramet
ers]
> "SQLArg0"="-ds:\\MSSQL8\\MSSQL\\data\\master.mdf"
> "SQLArg1"="-es:\\MSSQL8\\MSSQL\\log\\ERRORLOG"
> "SQLArg2"="-ls:\\MSSQL8\\MSSQL\\data\\mastlog.ldf".
> There's a local d, e and l-drive (No SAN)
> Anyone has an idea what's going wrong
>

Error starting SQLserver on windows 2000

When starting the SQLserver service on a windows 2000 server, we get
following error:
17050 :
initerrlog: Could not open error log file
's:\MSSQL8\MSSQL\log\ERRORLOG'. Operating system error = 3(error not
found).
We're running SQL 2000 std ed.. This is no cluster, access rights on
file are correct, the file is not locked by another process.
I've compared registry settings with a working server (same config) and
there identical.
registry setting:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters]
"SQLArg0"="-ds:\\MSSQL8\\MSSQL\\data\\master.mdf"
"SQLArg1"="-es:\\MSSQL8\\MSSQL\\log\\ERRORLOG"
"SQLArg2"="-ls:\\MSSQL8\\MSSQL\\data\\mastlog.ldf".
There's a local d, e and l-drive (No SAN)
Anyone has an idea what's going wrongHi Olivier
The parameters are expecting a S drive, where are the files supposed to be?
You could start sqlservr.exe from the command prompt and specify the correct
file names, see the topic "sqlservr Application" in Books Online and change
the values through Enterprise Manager, if you don't want to change the
registry directly.
John
"sqlservr Application"
"olivier.lammens@.gmail.com" wrote:
> When starting the SQLserver service on a windows 2000 server, we get
> following error:
> 17050 :
> initerrlog: Could not open error log file
> 's:\MSSQL8\MSSQL\log\ERRORLOG'. Operating system error = 3(error not
> found).
> We're running SQL 2000 std ed.. This is no cluster, access rights on
> file are correct, the file is not locked by another process.
> I've compared registry settings with a working server (same config) and
> there identical.
> registry setting:
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters]
> "SQLArg0"="-ds:\\MSSQL8\\MSSQL\\data\\master.mdf"
> "SQLArg1"="-es:\\MSSQL8\\MSSQL\\log\\ERRORLOG"
> "SQLArg2"="-ls:\\MSSQL8\\MSSQL\\data\\mastlog.ldf".
> There's a local d, e and l-drive (No SAN)
> Anyone has an idea what's going wrong
>

Error running SqlServer Reporting Services Report

Hi EveryoneIm running SQLSefrver Reporting Services 2000 SP 1 on Windows Server 2003 and getting the error below. Can anyone point me in the right direction as to what this could mean and how I could fix the problem.This is the error that is being logged in the reportserver error log:w3wp!runningjobs!364!8/02/2007-18:37:17:: w WARN: Previous request for Memory stats updatestill executing, skipping...w3wp!runningjobs!364!8/02/2007-18:38:17:: w WARN: Previous request for Memory stats updatestill executing, skipping...w3wp!runningjobs!364!8/02/2007-18:39:17:: w WARN: Previous request for Memory stats updatestill executing, skipping...w3wp!runningjobs!364!8/02/2007-18:40:17:: w WARN: Previous request for Memory stats updatestill executing, skipping...w3wp!library!3114!02/08/2007-18:40:18:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., ; Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. --> System.Threading.ThreadAbortException: Thread was being aborted. at Microsoft.ReportingServices.Diagnostics.ResourceUtilities.get_PrivateMBytes() at Microsoft.ReportingServices.Diagnostics.ResourceUtilities.get_TooMuchMemory() at Microsoft.ReportingServices.WebServer.Global.Application_AuthenticateRequest(Object sender, EventArgs e) -- End of inner exception stack trace --w3wp!library!18ec!02/08/2007-18:41:03:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., ; Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. --> System.Threading.ThreadAbortException: Thread was being aborted. at Microsoft.ReportingServices.Diagnostics.ResourceUtilities.get_PrivateMBytes() at Microsoft.ReportingServices.Diagnostics.ResourceUtilities.get_TooMuchMemory() at Microsoft.ReportingServices.WebServer.Global.Application_AuthenticateRequest(Object sender, EventArgs e) -- End of inner exception stack trace --

I noticed the formatting was messed up so I have reposted below.

Hi Everyone

Im running SQLSefrver Reporting Services 2000 SP 1 on Windows Server 2003 and getting the error below.

Can anyone point me in the right direction as to what this could mean and how I could fix the problem.

This is the error that is being logged in the reportserver error log:

w3wp!runningjobs!364!8/02/2007-18:37:17:: w WARN: Previous request for Memory stats updatestill executing, skipping...

w3wp!runningjobs!364!8/02/2007-18:38:17:: w WARN: Previous request for Memory stats updatestill executing, skipping...

w3wp!runningjobs!364!8/02/2007-18:39:17:: w WARN: Previous request for Memory stats updatestill executing, skipping...

w3wp!runningjobs!364!8/02/2007-18:40:17:: w WARN: Previous request for Memory stats updatestill executing, skipping...

w3wp!library!3114!02/08/2007-18:40:18:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., ; Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. --> System.Threading.ThreadAbortException: Thread was being aborted. at Microsoft.ReportingServices.Diagnostics.ResourceUtilities.get_PrivateMBytes() at Microsoft.ReportingServices.Diagnostics.ResourceUtilities.get_TooMuchMemory() at Microsoft.ReportingServices.WebServer.Global.Application_AuthenticateRequest(Object sender, EventArgs e)

-- End of inner exception stack trace --

w3wp!library!18ec!02/08/2007-18:41:03:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details., ; Info: Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. --> System.Threading.ThreadAbortException: Thread was being aborted. at Microsoft.ReportingServices.Diagnostics.ResourceUtilities.get_PrivateMBytes() at Microsoft.ReportingServices.Diagnostics.ResourceUtilities.get_TooMuchMemory() at Microsoft.ReportingServices.WebServer.Global.Application_AuthenticateRequest(Object sender, EventArgs e)

-- End of inner exception stack trace --

|||

OK, placing the report and reportserver virtual directories into their own app. pools seems to have "fixed" the problem. Dont know why but at the moment Im happy its just fixed!!