The SBSMonitoring database is nearing maximum size on SBS 2008

Have you received this error? The SBSMonitoring database is nearing maximum size on SBS 2008. I was getting this on a SBS 2008 server running the SBS BPA. From the error message, it’s pretty clear that the SBSMonitoring database is too large to work normally. There is a fix for this and it turns out the same SQL script that is used for an SBS problem where the Console displays too slowly is part of the solution. To shrink the database, Please follow these steps: Step 1: Download the following file to the server you are going to be working on: 1. 2. I recommend you save the file to an easy to access path, such as c:windowstemp. Step 2: Complete a backup of the SBSMonitoring Databases 1.Open Services from Administrative Tools , Services 2.Accept the UAC prompt 3.Find and stop the SQL Server ( SBSMONITORING ) service. 4.Make a copy of the files in the following folder: 1.C:Program Files (x86)Microsoft SQL ServerMSSQL.1MSSQLData 5.Once the file backup is completed, start the SQL Server (SBSMONITORING) service. Step 3: Proceed to run the following set of commands to implement the improvements 1. Open an Administrative Command Prompt (Run As Admin) 2.Type the following command, substitute the path to the updateSBSMonitoring.sql file as needed (We recommend that you do NOT copy & paste this command directly from the blog post): 1. Sqlcmd -S %computername%SBSMonitoring -E

Eaton LanSafe software may not find the controller

Today I was working on a Eaton 9125 UPS and setting up the software to cleanly shut down the server in case of a power outage. After installing the software, I noticed the Powerware LanSafe could not detect the controller. Nothing found: Taking a deeper dive to see what was going on, I cracked out my trusty NirSoft CurrPorts software to see the ports. I found out that LanSafe Power Monitor uses ports 3068 and port 3069. Upon looking at the ports, I noticed Microsoft DNS was using port 3068. This would cause LanSafe Power Monitor not able to bind with that port since it was in use. What was tricky was it still showed the service as running which I would have expected it to fail since it could not bind. Here is how I fixed it. Since DNS randomly selects the ports it wishes to use, I stopped the Microsoft DNS service. I then restarted the LanSafe Power Monitor services and checked to ensure it was bound to port 3068 and 3069. I then restarted the DNS service, and ensured it didn’t bind to port 3068 as it was before. Now launching LanSafe, I am able to see the server and am able to login to manage my UPS device. Share/Save