microsoft.public.sqlserver.notificationsvcs
[Top] [All Lists]

SQL 2k5 notification service won't start after SP1

Subject: SQL 2k5 notification service won't start after SP1
From: "InvalidLastName"
Date: Sun, 13 Aug 2006 14:43:16 -0400
Newsgroups: microsoft.public.sqlserver.notificationsvcs
We have a SQL 2k5 notification service application, which is running on Windows 2003 server, couldn't start after we applied the SQL 2k5 sp1. Opened the even viewer, there wasn't any entry found in the logs related to service failure. The server is located in our internal network, which is not public accessible, and has no internet access. We tried to rollback the sp1 by reinstalling the sql 2k5, and service started working again. Then we tried the same installation on a different box, which has internet connection, and service started without any problem.
 
It looks like the notification services has same issue SSIS described in several posts
however, I didn't find anyone has posted similar issue regarding to notification service. Just out of curiosity, I ran the netstat on the server, which SQLNS service won't start, and saw an entry to crl.microsoft.com (see below)
TCP    OurServer:4639           crl.microsoft.com:http  SYN_SENT
 
This tells me the registry hack [1] for SSIS may also work for SQLNS. The problem is the SQLNS service runs as out domain user instead of network service, and I don't really know which is the domain user we use. So I applied to the registry changes to ALL the entries found under HKEY_USERS, and the SQLNS service STARTS WORKING AGAIN.
 
I am glad that Microsoft assumes every SERVER should have internet connection. How says Administrators won't surf the internet or play World of Warcraft on the production server. With internet connection on every server, it makes a richer, but LESS secured production environment. After all, not everyone cares security.
 
However, for those who weights security than surfing internet, some advises for how to resolve this problem will be appreciated. Fist of all, I don't know what is that registry used for, and what does 23e00 mean, so I don't see registry is the right way to go. Second, even the registry works without any side-effect, there would very hard to find the specific domain user and change the registry on each server. Does 918222 cumulative fixes, http://support.microsoft.com/kb/918222/, will resolve this problem?
 
[1] registry hack for SSIS
[HKEY_USERS\S-1-5-20\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing]
"State"=dword:00023e00
 
 
Thanks
 
 
 
 
 
<Prev in Thread] Current Thread [Next in Thread>