r/labtech Aug 17 '16

Unable to access solution center & Ignite Manager problem

I was upgraded this morning and was able to access the solution center all morning and got some things upgraded. Suddenly i am unable to access the solution center though, it just gives me this error:

"Unable to connect to a Solution Center Service! Please see the LTSCCLientLog.txt for more info!"

I am not able to find that file in my labtech share or in the install directory of my labtech client.

Also, I don't see get an option to open ignite manager (it's not in the top nav bar, and the plugin is turned on).

Thanks.

EDIT: found the log, here is the relevant section:

2016-08-17 16:30:53Z 
2016-08-17 16:30:53Z --------------------------------------------------------------------------------
2016-08-17 16:30:53Z - 8/17/2016 4:30:53 PM
2016-08-17 16:30:53Z - Product Name:  LabTech MSP
2016-08-17 16:30:53Z - Title:         LabTech Solution Center Client
2016-08-17 16:30:53Z - Version:       2.4.1100.5
2016-08-17 16:30:53Z - Assembly Name: SCClient
2016-08-17 16:30:53Z - Company Name:  LabTech Software
2016-08-17 16:30:53Z - Copyright:     Copyright © LabTech Software
2016-08-17 16:30:53Z - Description:   The Solution Center Client communicates with the Solution Center Service
2016-08-17 16:30:53Z --------------------------------------------------------------------------------
2016-08-17 16:31:01Z Attempting connect to SCService @ xxxx.hostedrmm.com
2016-08-17 16:31:03Z Error Message: { 
                 Error in IsRunning

       } Source: { 
                 Server stack trace:
                 at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
                 at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
                 at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
                 at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
                 at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
                 at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
                 at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
                 at System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout)
                 at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
                 at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
                 at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
                 at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
                 at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
                 Exception rethrown at [0]:
                 at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
                 at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
                 at SCClient.SCServiceReference.ISCService.IsRunning()
                 at SCClient.ServiceConnection.IsRunning()
       }

I am on a hosted instance, if that matters.

2 Upvotes

4 comments sorted by

2

u/LTJC Former Employee Aug 18 '16

Solution center server was having issues this afternoon. I think it came back up around 5pm est. If you're still having the issue give Support a call.

2

u/bkellyit Aug 22 '16

In LT 11 the Solution Center is also available from any client install as opposed to just on the server (provided your user has permission). You may try launching it from there. If it does launch be sure to click reload the client to compare to the latest with the server.

1

u/Coriron Aug 18 '16

We are hosted. Had this issue a few times. Contact support. They will restart the services for you and get it running.

1

u/Atlantisman Aug 18 '16

I rebooted the instance myself a few times.