Windows Server - Fax and monitoring broken

Asked By Guillermo Lovato
20-Nov-09 03:17 PM
SBS 2k3 R2, all updates to day.

all of the sudden srver is failing everywhere, incoming fazes does not work
anymore(does not stores them in public folder, nor in the sbs site, nor i
receive email alerts), monitoring and reporting is broken too, the event
viewer is filled with errors, most of the time event 4104.

i've tried reinstalling the monitoring services to no avail, trying to
configure it returns in an error, i've also reinstalled the R2 technologies
previously due to another error.

any ideas?
SQL Server
(1)
Windows Server 2003
(1)
SmallBusinessServer
(1)
DeleteInternetData
(1)
Supervisión
(1)
Advertencia
(1)
Descripción
(1)
Reinstalar
(1)
  Larry Struckmeyer[SBS-MVP] replied to Guillermo Lovato
20-Nov-09 06:10 PM
Can we have more details on the errors in the event logs, please, and also
any on screen messages when things do not work correctly?

Have you downloaded, updated, and run the best practices analyzer?

www.sbsbpa.com

-
Larry
Please post the resolution to your
issue so others may benefit
-
Get Your SBS Health Check at
www.sbsbpa.com
  Guillermo Lovato replied to Larry Struckmeyer[SBS-MVP]
23-Nov-09 10:30 AM
Larry,
SBS reports no errors, it was already being used for a long time.

Details:
on the reporting section of the server admin i get a blank screen, if i try
to reconfigure it, it fails on all 4 configuration steps.
http://img338.imageshack.us/img338/3620/failreporting.png

the events i get related to monioring:
Tipo de suceso: Error
Origen del suceso: SmallBusinessServer
Categoría del suceso: Supervisión de SBS
Id. suceso: 4104
Fecha:  23/11/2009
Hora:  09:02:48 a.m.
Usuario:  No disponible
Equipo: SERVER
Descripción:
No se puede conectar a la base de datos de supervisión. Esto puede ocurrir
cuando hay conexiones múltiples a la base de datos. Espere un breve momento
e intente de nuevo. Si el error continúa, ejecute el Asistente para
configuración de supervisiones y seleccione Reinstalar las características
de supervisión.

Para obtener más información, vea el Centro de ayuda y soporte técnico en
http://go.microsoft.com/fwlink/events.asp.
Datos:
0000: 05 40 00 80               .@.€

Tipo de suceso: Advertencia
Origen del suceso: SQLAgent$SBSMONITORING
Categoría del suceso: Job Engine
Id. suceso: 208
Fecha:  23/11/2009
Hora:  03:00:01 a.m.
Usuario:  No disponible
Equipo: SERVER
Descripción:
SQL Server Scheduled Job 'SBS_Database_Cleanup'
(0x2F59D2123D99E24DB55D992676B171C4) - Status: Error - Invoked on:
2009-11-23 03:00:00 - Message: El trabajó falló.  El trabajo fue invocado
por Programar 1 (SBS Monitoring Database Cleanup Schedule). El último paso
ejecutado fue 16 (DeleteInternetData).

Para obtener más información, vea el Centro de ayuda y soporte técnico en
http://go.microsoft.com/fwlink/events.asp.

the service is up.

the fax thing, i'll leave it for later, best to focus on one thing at the
time
  v-robme replied to Guillermo Lovato
24-Nov-09 03:45 AM
Hello Lovato,

Thanks for your post and Larry's input.

Based on the current situation, I'd like suggest you perform the following steps to reinstall SBS monitoring components:

a. Control Panel -> Add Remove Program -> Windows Small Business Server 2003. Set Server Tools to Maintenance. Set Monitoring to Uninstall
b. Control Panel -> Add Remove Program -> SBSMONITORING -> Remove
c. Delete C:\program files\Microsoft SQL Server\MSSQL$SBSMONITORING Folder
d. Reboot
e. Control Panel -> Add Remove Program -> Windows Small Business Server 2003. Set Server Tools to Maintenance. Set Monitoring to Install
f. Reboot
g. Start MSSQL$SBSMONITORING and SQLAgent$SBSMONITORING services
h. In Server Management Console -> Monitoring and Reporting: run the Set Up Monitoring Reports and Alerts wizard.

Does it work now?

If the issue persists however, you may try to reinstall Windows Server 2003 SP2 to see if it changes.

Hope this helps. Also, if you have any questions or concerns, please do not hesitate to let me know.



Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support

==================================================================
Please post your SBS 2008 related questions to the SBS newsgroup on Connect website:
https://connect.microsoft.com/sbs08/community/discussion/richui/default.aspx

Please post your EBS related questions to the EBS newsgroup on Connect website:
https://connect.microsoft.com/ebs08/community/discussion/richui/default.aspx

If you want to use a newsreader other than a web forum to access these newsgroups,
please refer to the following blog to apply NNTP password and configure a newsreader:
http://msmvps.com/blogs/bradley/archive/2008/11/02/signing-up-for-the-sbs-2008-newsgroups.aspx
==================================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
==================================================================
Create New Account
help
Remove a Windows 2003 SBS Server from domain Windows Server OK, I didn???t see a Small Business Server forum so I am just posting this here in hopes I can get some help. What I currently have is a Windows domain environment with the following servers Server A: Windows 2003 SBS Std. Runs Active Directory and DNS Server B: Windows 2003 Std
GPO's Not Replicating Windows Server I am having a great deal of trouble getting GPs to pull over the domain to port 389 on the DC but I can telnet to 23 (after enabling telnet server). It shows that it is listening on 389 in netstat. SYSVOL properties are as they GP fine. it is everything outside of those 2 that does not. The PDC / DNS server is using its own IP for DNS. GPResult reads: Group Policy Infrastructure failed due to View this thread: http: / / forums.techarena.in / active-directory / 1288776.htm http: / / forums.techarena.in Windows Server Active Directory Discussions Windows Server 2008 R2 (1) Windows Server 2008 (1) Active Directory (1) NetBIOS (1) ProcessingTimeInMilliseconds (1) EventRecordID
SBS Migration to Server 2003 STANDARD Windows Server HELP ME PLEASE!! I have a huge problem. I have a SBS 2003 PDC which held all the FSMO roles, obviously, but was also a SQL Server. I added a second Server, which is Server 2003 R2, with SQL server also installed, which was promoted to a
Why does exiting "server management" exit my Terminal Server session? Windows Server Hi All, I have never seen this weird behavior before. I have a customer with a SBS2003 Terminal Server. In start up, it has an icon for Management). Okay, no problem. I have seen this before. But, on this particular server, when you exit "server management", you also exit your Terminal Services' session (same as Logout). What a pain in the neck! So, I erased "server management" from Start Up and now no log out problems with any other program. But
Made a big mistake - VPN and RPC over HTTP (SBS 2003 Prem.) Windows Server Been many months since I last posted. I am the 'poster boy' for how NOT 31 Dec '09, I no longer work for the nonprofit I have been with since 2003; short story - the economy. They kept me on as a contractor to handle IT. I replies convinced me to go with RWW. Theh recommended placing a PC locked in the server room that I could remopte into and then do my work. Couldn't make that that I'd turn on just when I needed it. Hoo-boy. I got into Server Management > Internet and clicked on the icon to create a remote connection (do not remember no good. The Montitoring MSDE quit on me next, then I started seeing errors about SQL. (I rebooted a bunch.) Tried to fix SQL 2000 - no good. Tried to fix SQL Server 2005 Express - no good. Then I thought