Detached Change Logs are generating an error message on client screen

Modified on Wed, 28 Dec 2011 09:56 by CAREWare Help Desk — Categorized as: FAQ

Detached Change Logs are generating an error message on client screen when the client has no records in the currently attached change logs. The error being generated is:

Source:  - An error occured while requesting change log information. You will not be able to perform searches at this time.
If the problem persists, please contact technical support.
The given client for the requested data is not present in the database.
   at jProgBusiness.jBusiness.jSearchList.GetClientInfo(String ClientPK, String DomainPK)
   at jProgBusiness.jBusiness.jBusinessAdministration.SearchChangesLog(String GUIDToken, jChangesFilter ChangesFilter, 
Int32 logFileNumber)
   at jProgBusiness.jBusiness.jBusinessRemote.ADM_Search_Changes_Log(String SessionToken, jChangesFilter ChangesFilter, 
Int32 logFileNumber)
 
Server stack trace:
   at jProgBusiness.jBusiness.jBusinessRemote.ADM_Search_Changes_Log(String SessionToken, jChangesFilter ChangesFilter, 
Int32 logFileNumber)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, 
Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, 
Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
 
Exception rethrown at [0]:
   at jProgBusiness.jBusiness.jClientSideRemote.ADM_Search_Changes_Log(String SessionToken, jChangesFilter ChangesFilter, 
Int32 logFileNumber)
   at Client.ChangeLog.get_ChangedRecordsList()
   at Client.ChangeLog.LoadChangesList()
An error occured while requesting change log information. You will not be able to perform searches at this time.

This bug was found in build580
This bug was fixed in build#
TTP #1905

Back to Bugs

Back to Frequently Asked Questions