Nova SS
Guest
|
 Posted:
Tue Sep 20, 2005 8:52 pm Post subject:
WSS Alerts not working |
|
|
I installed Windows SharePoint Services (WSS) on a Windows 2003 server. The
server is fully patched. When I go to Windows Update, it does not recommend
any updates.
Alerts initially worked just fine. Then a few weeks later, on Sept. 2, 2005,
alerts stopped working for all WSS users.
WSS uses the IIS SMTP service on the same machine. That machine’s last SMTP
log file is from Sept. 2, suggesting that WSS hasn’t even attempted to send
an email since then. The only user of IIS on that machine is WSS. Just now, I
ran a test script to send me an email through that server’s SMTP service. It
worked fine. (This gave me a new SMTP log file with a time stamp of just a
few minutes ago.)
WSS uses an SQL Server on a different Windows 2000 Server box. WSS access
the DB using a SQL Server account (as opposed to computer or domain account)
that is set up as a System Administrator. Since this Win2K server hosts SQL
Server databases for several applications, and since all these applications
and WSS are working fine (except for the email issue), I do not think SQL
Server is the problem. The full, correct connection string is accessible at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server
Extensions\Secure\ConfigDb.
WSS is not generating any unusual server events in the Application, System,
or Security event logs.
WSS is running under the TeamTestSite Application Pool, and that pool is
running under the context of Network Service.
The SharePoint Timer Service (SPTimer), which runs "C:\Program Files\Common
Files\Microsoft Shared\Web Server Extensions\60\BIN\OWSTIMER.EXE", is running
under the NT AUTHORITY\NETWORK SERVICE account. It is running, and I cannot
find any events attributable to it.
I do not have an owstimer.log. I am aware that if owstimer.exe was running
under the context of an actual account, I could look in %accountDir%/Local
Settings/Temp/owstimer.log. However, I am not aware of any such directory for
Network Service.
I have done an iisreset a few times, I have restarted SPTimer a few times, I
have rebooted the whole server a few times. Nothing helps.
Since WSS is not even attempting to send an email, this may not be relevant,
but I checked my McAfee VirusScan 8.0 anyway. This is the version that has
the port 25 blocking. Its Access Protection log does not record any email
blockings since Sept. 2. Even then, I have added owstimer.exe w3wp.exe to the
port 25 blocking exception list. I also tried turning off port 25 blocking,
and that didn’t fix anything, either.
I have reviewed
http://www.asaris-matrix.com/mvp-walsh/Lists/WSS%20FAQ/DispForm.aspx?ID=189.
I do not think that applies since I am authenticating to the database with an
SQL Server account, not a local computer or domain account.
Any assistance will be greatly appreciated!
Aren Cambre |
|
Nova SS
Guest
|
| Posted:
Thu Sep 22, 2005 4:51 pm Post subject:
RE: WSS Alerts not working |
|
|
I posted message into the wrong group. I am reposting at
microsoft.public.sharepoint.windowsservices.
Aren
"Nova SS" wrote:
| Quote: | I installed Windows SharePoint Services (WSS) on a Windows 2003 server. The
server is fully patched. When I go to Windows Update, it does not recommend
any updates.
Alerts initially worked just fine. Then a few weeks later, on Sept. 2, 2005,
alerts stopped working for all WSS users.
WSS uses the IIS SMTP service on the same machine. That machine’s last SMTP
log file is from Sept. 2, suggesting that WSS hasn’t even attempted to send
an email since then. The only user of IIS on that machine is WSS. Just now, I
ran a test script to send me an email through that server’s SMTP service. It
worked fine. (This gave me a new SMTP log file with a time stamp of just a
few minutes ago.)
WSS uses an SQL Server on a different Windows 2000 Server box. WSS access
the DB using a SQL Server account (as opposed to computer or domain account)
that is set up as a System Administrator. Since this Win2K server hosts SQL
Server databases for several applications, and since all these applications
and WSS are working fine (except for the email issue), I do not think SQL
Server is the problem. The full, correct connection string is accessible at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server
Extensions\Secure\ConfigDb.
WSS is not generating any unusual server events in the Application, System,
or Security event logs.
WSS is running under the TeamTestSite Application Pool, and that pool is
running under the context of Network Service.
The SharePoint Timer Service (SPTimer), which runs "C:\Program Files\Common
Files\Microsoft Shared\Web Server Extensions\60\BIN\OWSTIMER.EXE", is running
under the NT AUTHORITY\NETWORK SERVICE account. It is running, and I cannot
find any events attributable to it.
I do not have an owstimer.log. I am aware that if owstimer.exe was running
under the context of an actual account, I could look in %accountDir%/Local
Settings/Temp/owstimer.log. However, I am not aware of any such directory for
Network Service.
I have done an iisreset a few times, I have restarted SPTimer a few times, I
have rebooted the whole server a few times. Nothing helps.
Since WSS is not even attempting to send an email, this may not be relevant,
but I checked my McAfee VirusScan 8.0 anyway. This is the version that has
the port 25 blocking. Its Access Protection log does not record any email
blockings since Sept. 2. Even then, I have added owstimer.exe w3wp.exe to the
port 25 blocking exception list. I also tried turning off port 25 blocking,
and that didn’t fix anything, either.
I have reviewed
http://www.asaris-matrix.com/mvp-walsh/Lists/WSS%20FAQ/DispForm.aspx?ID=189.
I do not think that applies since I am authenticating to the database with an
SQL Server account, not a local computer or domain account.
Any assistance will be greatly appreciated!
Aren Cambre |
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in