prairieFyre - CCM Reporting pending

[plee61]

Hi,
We were able to extract report but not today. The Report status has been in pending status forever.
There are few errors showing in the log files under c:\program files\prairieFyre Software Inc\CCM\Logs
The log fie: WFMService shows the error below:

Error     15/11/2011 9:09:40 PM    prairieFyre.EnterpriseServices.Client.Authenticat ion   Login error!  Reached the following endpoints:and received this exception: System.Exception: System.ServiceModel.EndpointNotFoundExceptionCoul d not connect to net.tcp://172.28.164.137:7003/SecurityService. The connection attempt lasted for a time span of 00:00:01.0156250. TCP error code 10061: No connection could be made because the target machine actively refused it 172.28.164.137:7003.
Server stack trace:
   at System.ServiceModel.Channels.SocketConnectionInit iator.Connect(Uri uri, TimeSpan timeout)
   at System.ServiceModel.Channels.BufferedConnectionIn itiator.Connect(Uri uri, TimeSpan timeout)
   at System.ServiceModel.Channels.ConnectionPoolHelper .EstablishConnection(TimeSpan timeout)
   at System.ServiceModel.Channels.ClientFramingDuplexS essionChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject. Open(TimeSpan timeout)
   at System.ServiceModel.Channels.LayeredChannel`1.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject. Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.OnOpe n(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject. Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.CallO penOnce.System.ServiceModel.Channels.ServiceChann el.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.CallO nceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
   at System.ServiceModel.Channels.ServiceChannel.Ensur eOpened(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs)
   at System.ServiceModel.Channels.ServiceChannelProxy. InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy. Invoke(IMessage message)

Exception rethrown at

• :

   at System.Runtime.Remoting.Proxies.RealProxy.HandleR eturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.Private Invoke(MessageData& msgData, Int32 type)
   at prairieFyre.EnterpriseServices.Management.ISecuri tyService.Login(LoginRequest request)
   at prairieFyre.EnterpriseServices.Client.Management. SecurityService.<>c__DisplayClass2.<Login>b__0()
   at prairieFyre.EnterpriseServices.Client.ServiceProx yBase`1.CallInnerChannelWithRetry[K](Func`1 aInnerChannelCall)
   at prairieFyre.EnterpriseServices.Client.Management. SecurityService.Login(LoginRequest request) ---> System.Exception: System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 172.28.164.137:7003
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
   at System.ServiceModel.Channels.SocketConnectionInit iator.Connect(Uri uri, TimeSpan timeout)
   --- End of inner exception stack trace ---
   at prairieFyre.EnterpriseServices.Client.Authenticat ion.Login(LoginRequest aLoginRequest, String aServerAddress, Boolean aRegisterRemoteMessages)

Error     15/11/2011 9:09:40 PM    Error encountered in IsLicensedForWFM: Could not connect to the CCM Enterprise Service.   

Please help!
Cheers

[bluewhite4]

Check the PrairieFyre Reporting service found in Windows service.msc. It look like that service might be stopped. In which case you'll have to re-start it again.

If it fails to start or starts and then stops right away, look at the windows user account that's used to run the service. If its a domain level account, the password on that account may have expired or changed, so you'll have to update that.