Monitoring and reporting not working

Hi all,

Customer server, SBS2003 standard with SQL2005 installed. The problems
started after they had an external comapany in to install their software
onto the server to make use of the SQL which I had installed the week
before.

In server management when you click on monitoring and reporting you get
a host not found error. The daily performance reports that are mailed to
the owner now just contain the error "Bad Request (Invalid Hostname)" as
well.

Server logs are showing a few critical errors for around the time they
were in there installing,

error 4104
"Could not connect to the monitoring database. This can occur when there
are multiple connections to the database. Wait a short period of time,
and then try again. If this error persists, run the Monitoring
Configuration Wizard, and select Reinstall monitoring features.
"
I will go and ask the software company if they have any ideas, however
they probably aren't SBS aware.
Thanks,
Simon

OUCH...

You could fix this but then it may break their work done... They must be
consulted first. Ask them to write to you what they did and paste it here.

However this sounds like an expensive route!... SBS standard and then
purchased SQL2005, its 10 times cheaper to upgrade to SBS Premium?


"Simon" <news@bools-remove-this.org> wrote in message
news:%234Pc62oYIHA.4808@TK2MSFTNGP05.phx.gbl...
> Hi all,
>
> Customer server, SBS2003 standard with SQL2005 installed. The problems
> started after they had an external comapany in to install their software
> onto the server to make use of the SQL which I had installed the week
> before.
>
> In server management when you click on monitoring and reporting you get a
> host not found error. The daily performance reports that are mailed to the
> owner now just contain the error "Bad Request (Invalid Hostname)" as well.
>
> Server logs are showing a few critical errors for around the time they
> were in there installing,
>
> error 4104
> "Could not connect to the monitoring database. This can occur when there
> are multiple connections to the database. Wait a short period of time, and
> then try again. If this error persists, run the Monitoring Configuration
> Wizard, and select Reinstall monitoring features.
> "
> I will go and ask the software company if they have any ideas, however
> they probably aren't SBS aware.
> Thanks,
> Simon

Thanks for the reply,

I have emailed the support people at the company so they reply in
writing, I'll update this when they do.
The customer, although excellent are prone to going off and doing things
and then I found out after the event. The cost of the sql was no where
near what they had installed. I can see a new member server being
recommended by me pretty soon.
simon
Teneo wrote:
> OUCH...
>
> You could fix this but then it may break their work done... They must be
> consulted first. Ask them to write to you what they did and paste it here.
>
> However this sounds like an expensive route!... SBS standard and then
> purchased SQL2005, its 10 times cheaper to upgrade to SBS Premium?
>
>
> "Simon" <news@bools-remove-this.org> wrote in message
> news:%234Pc62oYIHA.4808@TK2MSFTNGP05.phx.gbl...
>> Hi all,
>>
>> Customer server, SBS2003 standard with SQL2005 installed. The problems
>> started after they had an external comapany in to install their software
>> onto the server to make use of the SQL which I had installed the week
>> before.
>>
>> In server management when you click on monitoring and reporting you get a
>> host not found error. The daily performance reports that are mailed to the
>> owner now just contain the error "Bad Request (Invalid Hostname)" as well.
>>
>> Server logs are showing a few critical errors for around the time they
>> were in there installing,
>>
>> error 4104
>> "Could not connect to the monitoring database. This can occur when there
>> are multiple connections to the database. Wait a short period of time, and
>> then try again. If this error persists, run the Monitoring Configuration
>> Wizard, and select Reinstall monitoring features.
>> "
>> I will go and ask the software company if they have any ideas, however
>> they probably aren't SBS aware.
>> Thanks,
>> Simon
>
>

Hi Simon,

Thank you for posting here and also Teneo's input.

From your posts, I understand that after installing some third party SQL related software, the Monitoring and Reporting
component doesn't work. Event Error 4104 was also encountered:

"Could not connect to the monitoring database. This can occur when there are multiple connections to the database. Wait a
short period of time, and then try again. If this error persists, run the Monitoring Configuration Wizard, and select Reinstall
monitoring features."

I also understand that you have emailed the support to confirm what they have done during the installation. Thank you for
your effort on this issue. The information will be very helpful if they have made some changes to the SQL server, or their
software has conflicts with the Monitoring component.


From the SBS standpoint, we can reinstall the Monitoring and Reporting component. However, just as Teneo said, this may
affect the application they installed. To avoid confusion, I recommend temporarily removing the third party application
before perform the following steps to reinstall this component.

1. Remove the Monitoring component:

Control Panel -> Add Remove Program -> Windows Small Business Server 2003. Set Server Tools to Maintenance. Set
Monitoring to Uninstall

2. Remove the Monitoring instance:

Control Panel -> Add Remove Program -> SBSMONITORING (Microsoft SQL Server Desktop Engine) -> Remove

3. Rename or delete C:\program files\Microsoft SQL Server\MSSQL$SBSMONITORING Folder

For example, rename to C:\program files\Microsoft SQL Server\old_MSSQL$SBSMONITORING.

4. Remove the following registry keys:

a. Delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\Monitoring
b. Delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SBSMONITORING

Reboot the SBS Server.

5. Control Panel -> Add Remove Program -> Windows Small Business Server 2003. Set Server Tools to Maintenance. Set
Monitoring to Install.
6. Reboot the SBS Server again.
7. Start the MSSQL$SBSMONITORING and SQLAgent$SBSMONITORING service.
8. In Server Management Console -> Monitoring and Reporting: run the Set Up Monitoring Reports and Alerts wizard again,
how will things go?


If the issue still occurs, you can also help me collect the MPS report for the further research:
---------------
a. Please download the MPSRPT_SETUPPerf.EXE from the following link and then run this tool to gather some information
from the problematic computer:
http://download.microsoft.com/downlo..._SETUPPerf.EXE

b. Double-click on the MPSRPT_SETUPPerf.EXE file. [Note] This process may take some time; however, it will not have a
negative effect on the performance.
c. A CAB file will be generated in the %systemroot%\MPSReports\Setup\Reports\Cab directory called%
COMPUTERNAME%_MPSReports.CAB. The CAB file will contain the reports generated by the MPS Reporting Tool.

You can zip these log files and send them as attachments to my mailbox v-shshao@microsoft.com

I hope the above info helps. Please feel free to let me know if anything is unclear.

Best regards,

Shawn Shao
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues regarding other Microsoft products, you'd better
post in the corresponding newsgroups so that they can be resolved in an efficient and timely manner. You can locate the
newsgroup here: http://www.microsoft.com/communities...s/default.aspx

When opening a new thread via the web interface, we recommend you check the "Notify me of replies" box to receive e-
mail notifications when there are any updates in your thread. When responding to posts via your newsreader, please
"Reply to Group" so that others may learn and benefit from your issue.

Microsoft engineers can only focus on one issue per thread. Although we provide other information for your reference, we
recommend you post different incidents in different threads to keep the thread clean. In doing so, it will ensure your issues
are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please check http://support.microsoft.com for regional
support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Hi Shawn,

Many thanks for the reply, I've got nothing useful back from the other
comapany yet, and it also appears they have messed up Sage on the server
as well.
I will report back once I find out what they have done today when trying
to fix that problem as no doubt it is related. I'm in the middle here
and the Owners want the new suppliers of the application to fix things,
no doubt I will have to clear up the broken pieces afterwards. No doubt
I will be back.
simon
Shawn Shao [MSFT] wrote:
> Hi Simon,
>
> Thank you for posting here and also Teneo's input.
>
> From your posts, I understand that after installing some third party SQL related software, the Monitoring and Reporting
> component doesn't work. Event Error 4104 was also encountered:
>
> "Could not connect to the monitoring database. This can occur when there are multiple connections to the database. Wait a
> short period of time, and then try again. If this error persists, run the Monitoring Configuration Wizard, and select Reinstall
> monitoring features."
>
> I also understand that you have emailed the support to confirm what they have done during the installation. Thank you for
> your effort on this issue. The information will be very helpful if they have made some changes to the SQL server, or their
> software has conflicts with the Monitoring component.
>
>
> From the SBS standpoint, we can reinstall the Monitoring and Reporting component. However, just as Teneo said, this may
> affect the application they installed. To avoid confusion, I recommend temporarily removing the third party application
> before perform the following steps to reinstall this component.
>
> 1. Remove the Monitoring component:
>
> Control Panel -> Add Remove Program -> Windows Small Business Server 2003. Set Server Tools to Maintenance. Set
> Monitoring to Uninstall
>
> 2. Remove the Monitoring instance:
>
> Control Panel -> Add Remove Program -> SBSMONITORING (Microsoft SQL Server Desktop Engine) -> Remove
>
> 3. Rename or delete C:\program files\Microsoft SQL Server\MSSQL$SBSMONITORING Folder
>
> For example, rename to C:\program files\Microsoft SQL Server\old_MSSQL$SBSMONITORING.
>
> 4. Remove the following registry keys:
>
> a. Delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\Monitoring
> b. Delete HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SBSMONITORING
>
> Reboot the SBS Server.
>
> 5. Control Panel -> Add Remove Program -> Windows Small Business Server 2003. Set Server Tools to Maintenance. Set
> Monitoring to Install.
> 6. Reboot the SBS Server again.
> 7. Start the MSSQL$SBSMONITORING and SQLAgent$SBSMONITORING service.
> 8. In Server Management Console -> Monitoring and Reporting: run the Set Up Monitoring Reports and Alerts wizard again,
> how will things go?
>
>
> If the issue still occurs, you can also help me collect the MPS report for the further research:
> ---------------
> a. Please download the MPSRPT_SETUPPerf.EXE from the following link and then run this tool to gather some information
> from the problematic computer:
> http://download.microsoft.com/downlo..._SETUPPerf.EXE
>
> b. Double-click on the MPSRPT_SETUPPerf.EXE file. [Note] This process may take some time; however, it will not have a
> negative effect on the performance.
> c. A CAB file will be generated in the %systemroot%\MPSReports\Setup\Reports\Cab directory called%
> COMPUTERNAME%_MPSReports.CAB. The CAB file will contain the reports generated by the MPS Reporting Tool.
>
> You can zip these log files and send them as attachments to my mailbox v-shshao@microsoft.com
>
> I hope the above info helps. Please feel free to let me know if anything is unclear.
>
> Best regards,
>
> Shawn Shao
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> This newsgroup only focuses on SBS technical issues. If you have issues regarding other Microsoft products, you'd better
> post in the corresponding newsgroups so that they can be resolved in an efficient and timely manner. You can locate the
> newsgroup here: http://www.microsoft.com/communities...s/default.aspx
>
> When opening a new thread via the web interface, we recommend you check the "Notify me of replies" box to receive e-
> mail notifications when there are any updates in your thread. When responding to posts via your newsreader, please
> "Reply to Group" so that others may learn and benefit from your issue.
>
> Microsoft engineers can only focus on one issue per thread. Although we provide other information for your reference, we
> recommend you post different incidents in different threads to keep the thread clean. In doing so, it will ensure your issues
> are resolved in a timely manner.
>
> For urgent issues, you may want to contact Microsoft CSS directly. Please check http://support.microsoft.com for regional
> support phone numbers.
>
> Any input or comments in this thread are highly appreciated.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>

Hi Simon,

Thank you for your feedback.

It seems the problem is closely related to installation of the software. And you may need to work with their support to
troubleshoot this issue first. If further assistance is needed from the SBS side or if there is any update on this issue, please
feel free to post back.

Have a nice day!

Best regards,

Shawn Shao
Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues regarding other Microsoft products, you'd better
post in the corresponding newsgroups so that they can be resolved in an efficient and timely manner. You can locate the
newsgroup here: http://www.microsoft.com/communities...s/default.aspx

When opening a new thread via the web interface, we recommend you check the "Notify me of replies" box to receive e-
mail notifications when there are any updates in your thread. When responding to posts via your newsreader, please
"Reply to Group" so that others may learn and benefit from your issue.

Microsoft engineers can only focus on one issue per thread. Although we provide other information for your reference, we
recommend you post different incidents in different threads to keep the thread clean. In doing so, it will ensure your issues
are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please check http://support.microsoft.com for regional
support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.