Hi Robbin
I could handle with mmc problem.
After running sbsbpa one of the suggestion was to turned on DEP Always on.
Instead of that I changed boot.ini option on that /noexecute=OptIn.
Now Isa Console and other mmc snapin's works OK.
Anyway after removing monitoring, deleting msde base and removing registry
key from sql registry nothing has changed with monitoring problem.
I checked problem and during startup in logs I have errors:
ID 7026
" the following boot-start drivers failed to load ' i8042prt'"
and
Event ID 1000 # 50070: Unable to connect to the database STS_Config_xxxxx
on <server_name>\Sharepoint. Check the database connection information and
make sure that the database is running.
I'm still waiting for some proposition.
I hope you can help me.
Regards
""Robbin Meng [MSFT]"" wrote:
>
>
> Hi,
>
> Thank you for writing back to us.
>
> First, I would like to explain that the previous steps we re-registered the WMI dll files and mofcomp should not cause MMC issues directly. Have you rebooted the server and
> double check it again?
>
> Now, please try to open a new MMC window(run MMC in the "Run¡Â*" box) and manually add the ISA 2004 snap-in. Can we open ISA console in this way? Moreover, please
> check if the issue occurs when load other snap-ins besides ISA so that we can determine whether it is a general MMC issue or ISA server issue.
>
> If the issue only occur when open ISA console, to work around this ISA server issue, use one of the following methods.
> Method 1: Reinstall ISA Server 2004 SP3
> 1. Download ISA Server 2004 SP3.
>
> For more information about how to download ISA 2004 SP3, visit the following Microsoft Web site:
> http://technet.microsoft.com/en-us/f.../bb734854.aspx
> 2. Exit all ISA Server utilities, and then close all ISA Server user interface components. For example, close the ISA Server Management Microsoft Management
> Console (MMC) snap-in.
> 3. Exit all other RDP sessions on the server. To do this, follow these steps:
> a. Open Task Manager , and then click the User tab.
> b. Right-click a user account that does not represent your current connection, and then click Log Off .
> c. When you are prompted to verify the action, click Yes .
> d. Repeat steps 3b through 3c for each RDP connection.
>
> 4. At a command prompt, type the following command to reinstall ISA Server 2004 SP3, and then press ENTER:
> msiexec /p Full_Path_To_SP3_Package REINSTALL=all REINSTALLMODE=omus /l*v c:\sp3.log
> Note We recommend that you reinstall ISA Server 2004 SP3 in repair mode.
>
> After reinstalling SP3, please use the SPCheck Tool to confirm the Service Pack lever of ISA server 2004. Then connect SBS server to the Microsoft Update website and
> apply all necessary updates released after SP3.
>
> How to Use the SPCheck Tool to Determine the Service Pack Level of ISA Server Files
> http://support.microsoft.com/kb/312552/EN-US/
>
> Method 2: Reregister the ISA Server administration component
> 1. Click Start , click Run , type cmd , and then press ENTER.
> 2. At the command prompt, type the following commands. Press ENTER after each command.
> cd /d "%programfiles%\microsoft isa server"
> regsvr32 wspadmin.dll
> 3. When you receive the "DllRegisterServer in wspadmin.dll succeeded" message, click OK .
> 4. At the command prompt, type the following commands. Press ENTER after each command.
> md VPN\Netsh
> net start fwsrv
>
>
> More ISA issue related information here:
>
>
> The Microsoft Firewall service does not start after an ISA Server 2004 SP3 installation fails
> http://support.microsoft.com/kb/937028
>
> You receive a false positive Firewall service error message on your ISA Server 2004 computer
> http://support.microsoft.com/kb/840180
>
> Error message when you open a Microsoft Management Console (MMC) snap-in after you install Windows Server 2003 Service Pack 2 or Windows Small Business Server
> 2003 R2 Technologies: "MMC has detected an error in a snap-in"
> http://support.microsoft.com/kb/947532
>
> Microsoft Internet Security and Acceleration (ISA) Server Best Practices Analyzer (BPA) Tool
> http://www.microsoft.com/downloads/d...displaylang=en
>
>
> Just for your reference, if the original incomplete reporting issue still occurs, you may consider reinstall the Monitoring and Report feature of SBS. Following are detailed
> steps to reinstall it:
>
> 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
>
>
> 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/...i/default.aspx
>
> Please post your EBS related questions to the EBS newsgroup on Connect website:
> https://connect.microsoft.com/ebs08/...i/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/arch...ewsgroups.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.
> ================================================== ================
>
>
>
> .
>