Error during set partner statement (SP1)

Hi!

I have the following error during setting partner on mirror server
Msg 1431, Level 16, State 4, Line 1
Neither the partner nor the witness server instance for database "masterserver" is available. Reissue the command when at least one of the instances becomes available.

The partner is available through telnet. I've also checked ports vai netstat and have no found errors.

There are two noteworthy erros in the error log at mirror server
Error: 9642, Severity: 16, State: 3.
and
An error occurred in a Service Broker/Database Mirroring transport connection endpoint, Error: 8474, State: 11. (Near endpoint role: Target, far endpoint address: '')

Security settings it seems are set accurately.

Ok, find out the problem.
I leave database yesterday in restoring state and today morning it has recovering state.

When I synchronize logs again mirroring has worked fine. I think during server startup (I restarted server today morning) it tries to recover mirror database. It leads database status changing and impossibility to set up partner.

Error Creating a new cluster on windows 2003 Server EE SP1

Hi,
I'm trying to install cluster service on a Windows 2003 Server Enterprise
Edition SP1.
I've configured Network and Disk.
When I try to create a new a new cluster for the first node, I receive this
error:
Found an existing cluster or node with the name "pippo.mydomain.com". Choose
another name.
A cluster cannot be created with the specified cluster name because that
cluster name is already in use. Specify a different name for the cluster.
I try to change netbios name but it does nothing.(NETBIOS name pippo does
not exsist in mydomain.....i try to use net view \\pippo)
Can You help Me ?
Tank you.
Have you tried to create this cluster before? Chances are that you still
have a DNS entry that needs to be flushed. All Address and Pointer records
for this host/IP address combination need to be flushed before you try and
reinstall.
Sincerely,
Anthony Thomas

"AS" <AS@.discussions.microsoft.com> wrote in message
news:7E9BC8F9-AA47-4D21-B7CF-71E876B9E6F1@.microsoft.com...
Hi,
I'm trying to install cluster service on a Windows 2003 Server Enterprise
Edition SP1.
I've configured Network and Disk.
When I try to create a new a new cluster for the first node, I receive this
error:
Found an existing cluster or node with the name "pippo.mydomain.com". Choose
another name.
A cluster cannot be created with the specified cluster name because that
cluster name is already in use. Specify a different name for the cluster.
I try to change netbios name but it does nothing.(NETBIOS name pippo does
not exsist in mydomain.....i try to use net view \\pippo)
Can You help Me ?
Tank you.

Error connecting to local SQL Server Express with SQL Server management Studio Express

I have SQL Server 2005 Express Edition installed on a Windows Server 2003 SP1 machine. I am trying to connect to the server on the local machine via shared memory with SQL Server Management Studio Express but I get the following error message:

TITLE: Connect to Server

Cannot connect to SERVER\SQLEXPRESS.

ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) (Microsoft SQL Server, Error: 10061)

I have already enabled remote connections, TCP Ports, etc., and disabled the firewall, but since I am connecting from a local machine, that should not matter. I have uninstalled and reinstalled SQL Server Express with same issue occuring. SQLServer service Browser service is running.

Can anyone share some ideas on how to troubleshoot this connection issue? Could this be caused by some scurity settings or services not running in Windows Server 2003? Any help would be greatly appreciated.

Seems to be a strange issue.

Please check whether the Engine Services are running by using the Configuration Manager. Also check whether the account with which the service is running has a valid login in the Server.

Regards,

Rajesh

|||

After a good night sleep, I tried to connect to the database via Management Studio Express with the following Connection: .\SQLEXPRESS. This allowed me to connect to the database. Previously I had always connected with Server\SQLEXPRESS which produced the above error. After connecting to the datagase, the Registered Database window of Management Studio Express showed the database engine as server\sqlexpress, even though I could not connect to it using Server\SQLEXPRESS.

I felt happier I could connect, but I still couldn't understand why I can't connect using SERVER\SQLEXPRESS but have to use .\SQLEXPRESS. My real purpose of using SQL Server Express is to upgrade the back-end of an existing networked MS Access database application. When I went to SQL Server Configuration Manager to set up remote connections so I could connect from a client using a form of .\SQLEXPRESS or maybe IP ADDRESS/SQLEXPRESS, I noticed under SQL Native Client Configuration => Aliases, there was an alias configured for "SERVER\SQLEXPRESS". I don't know why this was there since I removed (via add/remove programs deleting the remaining Program Files => SQL SERVER directories) and reinstalled the application. I deleted this alias. After doing this I was able to connect to the Sever from Server Management Studio Express using SERVER\SQLEXPRESS. Finally I am able to progress to the task at hand of connecting to the database via Access Client, which leads to other problem I hope someone can help me with below.

In upsizing our Access application, we have decided only to upgrade the back-end but keep the front-end using Access and Jet connection to SQL Server via ODBC. We are currently using the "SQL Sever" ODBC driver that comes standard on Windows XP machine, configured at Administrative Tools => Data Sources (ODBC). I know this is not the best, but budget dictates (minimal to no changes in front-end Access) and it is a small application (~100MB size with one year of data). I am able to connect to the SQLEXPRESS database from ACCESS front-end at the client workstations, so I know the SQL SERVER Firewall settings are O.K. The problem I am having is that the connection drops out after 15 -30 minutes. I then can not reconnect to the database for some time. However, after additional amount of time, I am able to connect without changing anything in the configuration. We are using Windows Server 2003 R2 SP1 with Windows XP Pro clients. I don't think it is a network cabling problem because at the times when I can not connect to SQL SERVER, file and print sharing still work.

Does anybody have any hints on the easiest way to troubleshoot and fix this intermittant issue? Should I try to use the "SQL Native Client" ODBC Driver? Any suggestions are greatly appreciated.

|||Check any error or warning from SQL error logs & event viewer logs for the intermittent disconnection, also you can run a netmon trace to find where it is having problem. I guess as the clients can connect to SQL server now after your setup, its only on the network you should chekc.

error code 17058

Hi everyone. I installed SP1 and it required a reboot. When I attempted to
start the
service from the Management Studio it fails and indicates an instance
failure (system.data). When I attempt to start from the administrative
services control
it fails and indicates a 17058 error, but the search results indicate this
is associated
with sql2000. The directory indicates the system files are there. I have
current
backups of system and data files. Anything I can do short of a complete
reload?
Thanks to everyone for being there to help.
SQL2005 and almost SP1
EdHi!

> Hi everyone. I installed SP1 and it required a reboot. When I attempted to
> start the
> service from the Management Studio it fails and indicates an instance
> failure (system.data). When I attempt to start from the administrative
> services control
> it fails and indicates a 17058 error, but the search results indicate this
> is associated
> with sql2000. The directory indicates the system files are there. I have
> current
> backups of system and data files. Anything I can do short of a complete
> reload?
> Thanks to everyone for being there to help.
> SQL2005 and almost SP1
This can be SQL 2005 error as well - check, for example
c33f0483c5587bdf." target="_blank">http://groups.google.si/group/micro...3f0483c5587bdf.
If this is what you get, you should not use Network Service account for the
SQL Server service.
Dejan Sarka, SQL Server MVP
Mentor, www.SolidQualityLearning.com
Anything written in this message represents solely the point of view of the
sender.
This message does not imply endorsement from Solid Quality Learning, and it
does not represent the point of view of Solid Quality Learning or any other
person, company or institution mentioned in this message

error code 17058

Hi everyone. I installed SP1 and it required a reboot. When I attempted to
start the
service from the Management Studio it fails and indicates an instance
failure (system.data). When I attempt to start from the administrative
services control
it fails and indicates a 17058 error, but the search results indicate this
is associated
with sql2000. The directory indicates the system files are there. I have
current
backups of system and data files. Anything I can do short of a complete
reload?
Thanks to everyone for being there to help.
SQL2005 and almost SP1
EdHi!
> Hi everyone. I installed SP1 and it required a reboot. When I attempted to
> start the
> service from the Management Studio it fails and indicates an instance
> failure (system.data). When I attempt to start from the administrative
> services control
> it fails and indicates a 17058 error, but the search results indicate this
> is associated
> with sql2000. The directory indicates the system files are there. I have
> current
> backups of system and data files. Anything I can do short of a complete
> reload?
> Thanks to everyone for being there to help.
> SQL2005 and almost SP1
This can be SQL 2005 error as well - check, for example
http://groups.google.si/group/microsoft.public.sqlserver.server/browse_thread/thread/fd5cb2a8c242612a/c33f0483c5587bdf?lnk=st&q=17058+sql+server+error&rnum=1&hl=sl#c33f0483c5587bdf.
If this is what you get, you should not use Network Service account for the
SQL Server service.
--
Dejan Sarka, SQL Server MVP
Mentor, www.SolidQualityLearning.com
Anything written in this message represents solely the point of view of the
sender.
This message does not imply endorsement from Solid Quality Learning, and it
does not represent the point of view of Solid Quality Learning or any other
person, company or institution mentioned in this message

error code 17058

Hi everyone. I installed SP1 and it required a reboot. When I attempted to
start the
service from the Management Studio it fails and indicates an instance
failure (system.data). When I attempt to start from the administrative
services control
it fails and indicates a 17058 error, but the search results indicate this
is associated
with sql2000. The directory indicates the system files are there. I have
current
backups of system and data files. Anything I can do short of a complete
reload?
Thanks to everyone for being there to help.
SQL2005 and almost SP1
Ed
Hi!

> Hi everyone. I installed SP1 and it required a reboot. When I attempted to
> start the
> service from the Management Studio it fails and indicates an instance
> failure (system.data). When I attempt to start from the administrative
> services control
> it fails and indicates a 17058 error, but the search results indicate this
> is associated
> with sql2000. The directory indicates the system files are there. I have
> current
> backups of system and data files. Anything I can do short of a complete
> reload?
> Thanks to everyone for being there to help.
> SQL2005 and almost SP1
This can be SQL 2005 error as well - check, for example
http://groups.google.si/group/micros...f0483c5587bdf.
If this is what you get, you should not use Network Service account for the
SQL Server service.
Dejan Sarka, SQL Server MVP
Mentor, www.SolidQualityLearning.com
Anything written in this message represents solely the point of view of the
sender.
This message does not imply endorsement from Solid Quality Learning, and it
does not represent the point of view of Solid Quality Learning or any other
person, company or institution mentioned in this message

Error After SQL Server 2005 SP1

SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server SP1
When I start the SQL Server service I get:
[298] SQL Server Error: 2812, Could not find stored procedure
'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
Any ideas?
Thanks,
Bryansp1 build is 2047. you must have installed the post sp1 hotfix rollup.
please follow http://support.microsoft.com/Default.aspx?id=918222 to ensure
you have properly install the hotfix in the specified order.
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server
> SP1
>
> When I start the SQL Server service I get:
> [298] SQL Server Error: 2812, Could not find stored procedure
> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>
> Any ideas?
> Thanks,
> Bryan
>|||sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
please follow http://support.microsoft.com/Default.aspx?id=918222 to ensure
you have properly install the hotfix in the specified order.
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server
> SP1
>
> When I start the SQL Server service I get:
> [298] SQL Server Error: 2812, Could not find stored procedure
> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>
> Any ideas?
> Thanks,
> Bryan
>|||Hi, Thank you for your post.
We were aware and followed KB918222 prior to bringing the build to 2153. It
does not appear to be related.
"oj" <nospam_ojngo@.home.com> wrote in message
news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
> please follow http://support.microsoft.com/Default.aspx?id=918222 to
> ensure you have properly install the hotfix in the specified order.
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...|||Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
execution line should be:
EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
@.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
@.@.trancount, @.wmi_namespace, @.wmi_query
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...
> Hi, Thank you for your post.
> We were aware and followed KB918222 prior to bringing the build to 2153.
> It does not appear to be related.
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
>|||Hi, Thank you for your post.
We were aware and followed KB918222 prior to bringing the build to 2153. It
does not appear to be related.
"oj" <nospam_ojngo@.home.com> wrote in message
news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...[vbcol=seagreen]
> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
> please follow http://support.microsoft.com/Default.aspx?id=918222 to
> ensure you have properly install the hotfix in the specified order.
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...|||Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
execution line should be:
EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
@.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
@.@.trancount, @.wmi_namespace, @.wmi_query
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...
> Hi, Thank you for your post.
> We were aware and followed KB918222 prior to bringing the build to 2153.
> It does not appear to be related.
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
>|||Hi, Thanks for following up! On inspection of msdb.dbo.sp_sqlagent_notify
source the calling semantics of master.dbo.xp_sqlagent_notify are the same
as what you specified.
"oj" <nospam_ojngo@.home.com> wrote in message
news:uJB6qmWkGHA.3588@.TK2MSFTNGP02.phx.gbl...[vbcol=seagreen]
> Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
> execution line should be:
> EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
> @.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
> @.@.trancount, @.wmi_namespace, @.wmi_query
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...|||Hi, Thanks for following up! On inspection of msdb.dbo.sp_sqlagent_notify
source the calling semantics of master.dbo.xp_sqlagent_notify are the same
as what you specified.
"oj" <nospam_ojngo@.home.com> wrote in message
news:uJB6qmWkGHA.3588@.TK2MSFTNGP02.phx.gbl...[vbcol=seagreen]
> Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
> execution line should be:
> EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
> @.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
> @.@.trancount, @.wmi_namespace, @.wmi_query
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...|||there must be a process/procedure that calls 'msdb.dbo.xp_sqlagent_notify'.
run this to see if anything returns.
exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from
?.sys.sql_modules where definition like '%msdb.dbo.xp_sqlagent_notify%'"
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:uFvh$UXkGHA.2200@.TK2MSFTNGP05.phx.gbl...
> Hi, Thanks for following up! On inspection of
> msdb.dbo.sp_sqlagent_notify source the calling semantics of
> master.dbo.xp_sqlagent_notify are the same as what you specified.
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:uJB6qmWkGHA.3588@.TK2MSFTNGP02.phx.gbl...
>

Error After SQL Server 2005 SP1

SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server SP1
When I start the SQL Server service I get:
[298] SQL Server Error: 2812, Could not find stored procedure
'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
Any ideas?
Thanks,
Bryansp1 build is 2047. you must have installed the post sp1 hotfix rollup.
please follow http://support.microsoft.com/Default.aspx?id=918222 to ensure
you have properly install the hotfix in the specified order.
--
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server
> SP1
>
> When I start the SQL Server service I get:
> [298] SQL Server Error: 2812, Could not find stored procedure
> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>
> Any ideas?
> Thanks,
> Bryan
>|||Hi, Thank you for your post.
We were aware and followed KB918222 prior to bringing the build to 2153. It
does not appear to be related.
"oj" <nospam_ojngo@.home.com> wrote in message
news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
> please follow http://support.microsoft.com/Default.aspx?id=918222 to
> ensure you have properly install the hotfix in the specified order.
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
>> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server
>> SP1
>> When I start the SQL Server service I get:
>> [298] SQL Server Error: 2812, Could not find stored procedure
>> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>>
>> Any ideas?
>> Thanks,
>> Bryan|||Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
execution line should be:
EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
@.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
@.@.trancount, @.wmi_namespace, @.wmi_query
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...
> Hi, Thank you for your post.
> We were aware and followed KB918222 prior to bringing the build to 2153.
> It does not appear to be related.
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
>> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
>> please follow http://support.microsoft.com/Default.aspx?id=918222 to
>> ensure you have properly install the hotfix in the specified order.
>> --
>> -oj
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
>> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server
>> SP1
>> When I start the SQL Server service I get:
>> [298] SQL Server Error: 2812, Could not find stored procedure
>> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>>
>> Any ideas?
>> Thanks,
>> Bryan
>|||Hi, Thanks for following up! On inspection of msdb.dbo.sp_sqlagent_notify
source the calling semantics of master.dbo.xp_sqlagent_notify are the same
as what you specified.
"oj" <nospam_ojngo@.home.com> wrote in message
news:uJB6qmWkGHA.3588@.TK2MSFTNGP02.phx.gbl...
> Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
> execution line should be:
> EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
> @.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
> @.@.trancount, @.wmi_namespace, @.wmi_query
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...
>> Hi, Thank you for your post.
>> We were aware and followed KB918222 prior to bringing the build to 2153.
>> It does not appear to be related.
>> "oj" <nospam_ojngo@.home.com> wrote in message
>> news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
>> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
>> please follow http://support.microsoft.com/Default.aspx?id=918222 to
>> ensure you have properly install the hotfix in the specified order.
>> --
>> -oj
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
>> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003 Server
>> SP1
>> When I start the SQL Server service I get:
>> [298] SQL Server Error: 2812, Could not find stored procedure
>> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>>
>> Any ideas?
>> Thanks,
>> Bryan|||there must be a process/procedure that calls 'msdb.dbo.xp_sqlagent_notify'.
run this to see if anything returns.
exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n from
?.sys.sql_modules where definition like '%msdb.dbo.xp_sqlagent_notify%'"
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:uFvh$UXkGHA.2200@.TK2MSFTNGP05.phx.gbl...
> Hi, Thanks for following up! On inspection of
> msdb.dbo.sp_sqlagent_notify source the calling semantics of
> master.dbo.xp_sqlagent_notify are the same as what you specified.
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:uJB6qmWkGHA.3588@.TK2MSFTNGP02.phx.gbl...
>> Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
>> execution line should be:
>> EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
>> @.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
>> @.@.trancount, @.wmi_namespace, @.wmi_query
>> --
>> -oj
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...
>> Hi, Thank you for your post.
>> We were aware and followed KB918222 prior to bringing the build to 2153.
>> It does not appear to be related.
>> "oj" <nospam_ojngo@.home.com> wrote in message
>> news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
>> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
>> please follow http://support.microsoft.com/Default.aspx?id=918222 to
>> ensure you have properly install the hotfix in the specified order.
>> --
>> -oj
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
>> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003
>> Server SP1
>> When I start the SQL Server service I get:
>> [298] SQL Server Error: 2812, Could not find stored procedure
>> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>>
>> Any ideas?
>> Thanks,
>> Bryan
>|||Okay, I ran this and I found no references. I think what might be happening
is that xp_sqlagent_notify is called in the wrong database context. So the
intention is that it is called in master but is instead called in msdb.
However, when I search for just xp_sqlagent_notify, it is only called from
msdb..sp_delete_job
and msdb..sp_sqlagent_notify. BTW, clever code!
"oj" <nospam_ojngo@.home.com> wrote in message
news:OiAGECekGHA.4044@.TK2MSFTNGP03.phx.gbl...
> there must be a process/procedure that calls
> 'msdb.dbo.xp_sqlagent_notify'.
> run this to see if anything returns.
> exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n
> from ?.sys.sql_modules where definition like
> '%msdb.dbo.xp_sqlagent_notify%'"
> --
> -oj
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:uFvh$UXkGHA.2200@.TK2MSFTNGP05.phx.gbl...
>> Hi, Thanks for following up! On inspection of
>> msdb.dbo.sp_sqlagent_notify source the calling semantics of
>> master.dbo.xp_sqlagent_notify are the same as what you specified.
>> "oj" <nospam_ojngo@.home.com> wrote in message
>> news:uJB6qmWkGHA.3588@.TK2MSFTNGP02.phx.gbl...
>> Take a closer look at msdb..sp_sqlagent_notify stored procedure. The
>> execution line should be:
>> EXECUTE @.retval = master.dbo.xp_sqlagent_notify @.op_type, @.job_id,
>> @.schedule_id, @.alert_id, @.action_type, @.nt_user_name, @.error_flag,
>> @.@.trancount, @.wmi_namespace, @.wmi_query
>> --
>> -oj
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:%23sVMFlVkGHA.5108@.TK2MSFTNGP02.phx.gbl...
>> Hi, Thank you for your post.
>> We were aware and followed KB918222 prior to bringing the build to
>> 2153. It does not appear to be related.
>> "oj" <nospam_ojngo@.home.com> wrote in message
>> news:%233htVgRkGHA.4304@.TK2MSFTNGP03.phx.gbl...
>> sp1 build is 2047. you must have installed the post sp1 hotfix rollup.
>> please follow http://support.microsoft.com/Default.aspx?id=918222 to
>> ensure you have properly install the hotfix in the specified order.
>> --
>> -oj
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:%23xzEM2IkGHA.3780@.TK2MSFTNGP03.phx.gbl...
>> SQL Server 2005 SP1 Build 2153 Developer Edition on Windows 2003
>> Server SP1
>> When I start the SQL Server service I get:
>> [298] SQL Server Error: 2812, Could not find stored procedure
>> 'msdb.dbo.xp_sqlagent_notify'. [SQLSTATE 42000] (DisableAgentXPs)
>>
>> Any ideas?
>> Thanks,
>> Bryan
>>
>|||hmm...something must be calling this. there is definitely a bug here (if
it's not user code, then it's probably ms) because it references the wrong
database.
-oj
"BDB" <bdb@.reply.to.group.com> wrote in message
news:uDaA$76kGHA.3304@.TK2MSFTNGP03.phx.gbl...
> Okay, I ran this and I found no references. I think what might be
> happening is that xp_sqlagent_notify is called in the wrong database
> context. So the intention is that it is called in master but is instead
> called in msdb. However, when I search for just xp_sqlagent_notify, it is
> only called from msdb..sp_delete_job
> and msdb..sp_sqlagent_notify. BTW, clever code!
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:OiAGECekGHA.4044@.TK2MSFTNGP03.phx.gbl...
>> there must be a process/procedure that calls
>> 'msdb.dbo.xp_sqlagent_notify'.
>> run this to see if anything returns.
>> exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n
>> from ?.sys.sql_modules where definition like
>> '%msdb.dbo.xp_sqlagent_notify%'"
>> --
>> -oj|||look like it's ms bug.
"Ciprian Gerea [MSFT]" <Ciprian.Gerea@.online.microsoft.com> wrote in message
news:%23kozju%23kGHA.1244@.TK2MSFTNGP05.phx.gbl...
> Hi Adrian,
> The error about the call to xp_sqlagent_notify is a benign startup error,
> and we're looking at fixing it for the next service pack. Without more
> information I can't tell why agent is failing, but I believe that the job
> history error that you're mentioning might give us a clue.
-oj
"oj" <nospam_ojngo@.home.com> wrote in message
news:%23eUC$ODlGHA.4200@.TK2MSFTNGP05.phx.gbl...
> hmm...something must be calling this. there is definitely a bug here (if
> it's not user code, then it's probably ms) because it references the wrong
> database.
>
> --
> -oj
>
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:uDaA$76kGHA.3304@.TK2MSFTNGP03.phx.gbl...
>> Okay, I ran this and I found no references. I think what might be
>> happening is that xp_sqlagent_notify is called in the wrong database
>> context. So the intention is that it is called in master but is instead
>> called in msdb. However, when I search for just xp_sqlagent_notify, it is
>> only called from msdb..sp_delete_job
>> and msdb..sp_sqlagent_notify. BTW, clever code!
>> "oj" <nospam_ojngo@.home.com> wrote in message
>> news:OiAGECekGHA.4044@.TK2MSFTNGP03.phx.gbl...
>> there must be a process/procedure that calls
>> 'msdb.dbo.xp_sqlagent_notify'.
>> run this to see if anything returns.
>> exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n
>> from ?.sys.sql_modules where definition like
>> '%msdb.dbo.xp_sqlagent_notify%'"
>> --
>> -oj
>|||Thanks so much for your help!
"oj" <nospam_ojngo@.home.com> wrote in message
news:%23as6ORDlGHA.1320@.TK2MSFTNGP04.phx.gbl...
> look like it's ms bug.
> "Ciprian Gerea [MSFT]" <Ciprian.Gerea@.online.microsoft.com> wrote in
> message news:%23kozju%23kGHA.1244@.TK2MSFTNGP05.phx.gbl...
>> Hi Adrian,
>> The error about the call to xp_sqlagent_notify is a benign startup error,
>> and we're looking at fixing it for the next service pack. Without more
>> information I can't tell why agent is failing, but I believe that the job
>> history error that you're mentioning might give us a clue.
>
> --
> -oj
>
> "oj" <nospam_ojngo@.home.com> wrote in message
> news:%23eUC$ODlGHA.4200@.TK2MSFTNGP05.phx.gbl...
>> hmm...something must be calling this. there is definitely a bug here (if
>> it's not user code, then it's probably ms) because it references the
>> wrong database.
>>
>> --
>> -oj
>>
>> "BDB" <bdb@.reply.to.group.com> wrote in message
>> news:uDaA$76kGHA.3304@.TK2MSFTNGP03.phx.gbl...
>> Okay, I ran this and I found no references. I think what might be
>> happening is that xp_sqlagent_notify is called in the wrong database
>> context. So the intention is that it is called in master but is instead
>> called in msdb. However, when I search for just xp_sqlagent_notify, it
>> is only called from msdb..sp_delete_job
>> and msdb..sp_sqlagent_notify. BTW, clever code!
>> "oj" <nospam_ojngo@.home.com> wrote in message
>> news:OiAGECekGHA.4044@.TK2MSFTNGP03.phx.gbl...
>> there must be a process/procedure that calls
>> 'msdb.dbo.xp_sqlagent_notify'.
>> run this to see if anything returns.
>> exec sp_msforeachdb "select '?';use ?; select object_name(object_id) n
>> from ?.sys.sql_modules where definition like
>> '%msdb.dbo.xp_sqlagent_notify%'"
>> --
>> -oj
>>
>

Error after installing sp1

I started getting this after installing sp1 on my workstation and trying to deploy to rtm machines. The components giving this error are the data readers in the data flow.

TITLE: Microsoft Visual Studio

Component with name "<name>" and class ID "{BF01D463-7089-41EE-8F05-0A6DC17CE633}" could not be created because an error was encountered during its upgrade to the current version.
Contact information:
Extracts data from a relational database by using a .NET provider.;Microsoft Corporation;Microsoft SqlServer v9; ? 2004 Microsoft Corporation; All Rights Reserved; http://www.microsoft.com/sql/support;2

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.DataTransformationServices.Design.SR&EvtID=ComponentUpgradeFailed&LinkId=20476

BUTTONS:

OK

See Component Changes - http://wiki.sqlis.com/default.aspx/SQLISWiki/SP1.html|||That's just wonderful considering I installed it on my workstation as a test and now I can't roll out a lot of my packages. Ugh, I didn't think they could make management and deployment any more of a headache but they succeeded. How about they let you write the release notes from now on :)|||As a side note, it appears that even if I edit the xml as you suggest I still cannot deploy it from my workstation or it will readd those properties.|||Maybe you are using the built in deployment utility? I'm working in a file copy style deployment so it works fine as a workaround. Failing that roll out SP1!|||

Yeah I am. I suppose it calls that upgrade method before it uploads it to the server. *sigh*

We'd like to roll out sp1 if the install would quit crashing :)