I just want to share my experince on SCOM SLD which I configured on a machine in test env. I specfically used test environment as I was not sure whether it would work or not on a single server.
Before this test I've already installed these products/applications on different servers and it just work .. no issues...
So, my env has a Server running Windows 2003 + SP2 + SQL 2005 and SQL SP2, SCOM 2007 R2 + CU5 everything on one machine.
SCOM SLD/WSS on a same server and some consideration if you are testing
-Everything was working fine (from SCOM perspective) before instaling WSS and SLD configuration. SCOM was running fine.. reports were accessible
-Then i installed WSS 3.0 + SP2/SLD 2.0 on the same server and configured as required using SLD doc. Though i was little apprehensive but then thought of just giv a try setting up on same server
-So after installation I checked WSS and could configure SLD in sharepoint
-Now, when i went to scom monitoring section and tried to open report directly for the alert generated then it failed ... oh!... then i relaized the mistake i did. I came back to reporting section and tried opening reports frm there as well.. no luck... it just failed with the long error message.
Steps taken for identifying the issue
-----------------------------------
-Report url did not run
-Default web site and report sites were stop in IIS which was after WSS installation
Solution
--------
Changed Default web site port
Checked setting under Reporting Service Configuration .. which was ok
Most important change report url port in SCOM console under admin tab
restart the server --- tested again and worked
Hope this helps anyone who is using the same kind of scenario as used by me here
Varun
