SCOM doesn't require any "weird" access to SQL Server. Any access denied is traceable via Profiler. Dunno about LCS.
If you manually try to start the rtcsrv, do you get an error code back? Cheers Ken From: Steven Peck [mailto:[email protected]] Sent: Sunday, 19 February 2012 12:42 PM To: NT System Admin Issues Subject: Re: So...we broke SMS and Lice Communcations Server 2005 I'd call Microsoft. However if the SQL server was updated, then make sure things like compatibility mode are on and such (and beat the SQL guys for not having people check app compatilibity first). In general, it LCS either works or is just broken. LCS (and SCOM) seriously rely on weird access to SQL so they need rights most SQL DBA's like to take away and never give back. It may be the Upgrade broke something with permissions. On Sat, Feb 18, 2012 at 7:56 PM, David Lum <[email protected]<mailto:[email protected]>> wrote: LCS service (rtcsrv) does not start. Event Type: Error Event Source: Live Communications Server Snap-in Event Category: (1004) Event ID: 30710 Date: 2/18/2012 Time: 4:24:55 PM User: N/A Computer: LCS Description: Live Communications Server Snap-in failed to start service: Service Name = RtcSrv Machine Name = lcs.americas.nwea.pvt HRESULT = 8007042a Error Description = The service has returned a service-specific error code. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
