LCS 2005 message archiving

We currently run LCS 2005 SP1 in our enviroment with an access proxy for external connection and message logging.   the access proxy is on a different server then the LCS 2005 Server.  When have the IM's being archived on a SQL 2005 server.  Currently the logging is not working.  I noticed on the LCS 2005 server the  archiving service isn't running but on the access proxy server it is running.  I am not sure what to check because i  did not set this up and have never used it.
derekjrAsked:
Who is Participating?
 
gaanthonyConnect With a Mentor Commented:
Nope - On nt07 (LCS Server) change the Archiving Queue Path association.  
 
0
 
gaanthonyCommented:
Archiving should be running on the LCS 2005 server.  Archiving on the Access Proxy would be doing nothing. No reason for it to be installed there.
Check the MSMQ on the Front End Server and on the LCS Archiving Server.  MSMQ would queue up IMs for archiving on the LCS Home Server and send them to MSMQ on the LCS Archiving Server.
You can find all the LCS 2005 Guide at this link http://office.microsoft.com/en-us/communicationsserver/FX011526591033.aspx?ofcresset=1
Download "Live Communications Server 2005 deploying archiving" a little of 3/4 of the way down the page and have a look at it as it should help you determine what the issue may be.
0
 
derekjrAuthor Commented:
Ok i have taken some screenshots here.    both servers have the archiving service on them as you can see in the images.
 

NT071.jpg
NT072.jpg
NT073.jpg
VMSVR021.jpg
VMSRV022.jpg
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

 
gaanthonyCommented:
Looks like a permissions issue.  Add the LCS Archiving Service account to the Local Administrators group on the LCS 2005 Server and see if you can start the service.
0
 
derekjrAuthor Commented:
i see a lcadmin and rtcdomainserveradmins already in the local admin groups. i guess it would be the lcadmin account correct?
 
0
 
derekjrAuthor Commented:
oops i found lcsarchivingservice in the domain and added but the service still won't start.
 
0
 
derekjrAuthor Commented:
this is what is in the event log
 

Event Type: Error
Event Source: Live Communications Archiving Service
Event Category: (1014)
Event ID: 30605
Date:  2/20/2009
Time:  9:19:41 PM
User:  N/A
Computer: NT07
Description:
Live Communications Archiving Service failed to start.
Cause: Archiving Service encountered at least one critical error during startup.
Resolution:
Review event log entries.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
 
0
 
derekjrAuthor Commented:

Event Type: Error
Event Source: Live Communications Archiving Service
Event Category: (1014)
Event ID: 30603
Date:  2/20/2009
Time:  9:19:41 PM
User:  N/A
Computer: NT07
Description:
The service failed to connect to database LcsLog
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0
 
gaanthonyCommented:
Check the LCS Archiving Server to confirm whether the SQL services are running.  Also check event logs on it.
0
 
derekjrAuthor Commented:
mssqlrtc$ is running but sqlagentrtc$ is set not to run.
0
 
gaanthonyCommented:
Look in Add/remove programs on both the LCS 2005 server and the SQL server to determine which of them actually has the Archiving Server Role installed.
Then Deactivate the LCS Archiving Role on the server on which it is installed.  
Uninstall it from Add/Remove Programs and then reinstall and reactivate but "DO NOT" choose the option to replace the database if you wish to retain the previous archived data.  Might be a good idea to backup the SQL database just in case.
0
 
derekjrAuthor Commented:
0
 
derekjrAuthor Commented:
it runs on VMSVR02 which is the server that the service was able to run
 
0
 
derekjrAuthor Commented:
reinstalling now
0
 
derekjrAuthor Commented:
ok reinstalled and activated it. i see messages in the ms queue but it is staying there. i ran a query on the sql database  and it isn't in  there.
 
0
 
gaanthonyCommented:
Open the MMC for LIve Communications Server 2005.
Expand Forest, Expand Enterprise or Standard Edition Pool,
Expand the Server,  Right Click the Server FQDN and select properties and on the Archiving Tab check the Association.
0
 
derekjrAuthor Commented:
the server is already in there. if i  you take a look at these screen shots it lists the message queue as two different things.
ScreenHunter-01-Feb.-22-10.56.gif
ScreenHunter-02-Feb.-22-10.57.gif
0
 
gaanthonyCommented:
Looks like a message queue mismatch.
The Archiving Server queue is private\lcslog
The LCS Server (Front end) should be associated with archiving Queue path vmwrv02\private$\lcslog and not lcslogAP.
0
 
derekjrAuthor Commented:
how do i change it? do i have to deactivate and reinstall the archving service on vmsrv02?
0
 
derekjrAuthor Commented:
So this is now right correct?
ScreenHunter-01-Feb.-22-18.36.gif
0
 
derekjrAuthor Commented:
are you sure it should be lcslog. because under the lcslogap queue there is a message from last night after i  reinstalled the service.
0
 
gaanthonyCommented:
Based on what I can tell from the information provided this should be correct.  There may be a message from last night in the LCSLOGAP queue since that's where it's was associated originally.
Also check that
On a Windows Server 2003 domain, each computer running MSMQ must be a member of the Windows Authorization Access group in order to access TokenGroupsGlobalAndUniversal attribute used to authenticate Live Communications Servers that send messages to the Archving service destination queue. Computer accounts for the following servers must be added to this group:
·         The server with the SQL archiving database.
·         The server running the Archiving service
·         If you are archiving one a Standard Edition Server, add the Standard Edition Server computer account.
·         If you are archiving on an Enterprise pool,:
·         All Enterprise Editions Servers in a pool on which archiving is enabled.
·         The server on which the back-end database is run
0
 
derekjrAuthor Commented:
It is now working. Thanks so much for your help
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.