Showing results for 
Search instead for 
Do you mean 
Community Home Request Access Read Blogs Share Your Ideas Search Community View My Settings
New Member
Posts: 16
Registered: ‎02-18-2011

WC 03b, can't update leads from the list view

When we try to update the owner of multiple leads from the list view we are receiving the below error.  Also, getting this in multiple environments.  Everything else seems to be working after 100s hrs of testing.


GUI:"there was an unknown error in response to an HTTP request."


Event Type:    Error
Event Source:    Saleslogix Job Service
Event Category:    None
Event ID:    0
Date:        11/4/2014
Time:        9:39:09 AM
User:        N/A
Computer:    SLXINT1UAT
2014-11-04 09:39:09,694 [QuartzScheduler_Worker-3] ERROR Quartz.Core.JobRunShell - Job SlxJobService.Sage.SalesLogix.BusinessRules.Jobs.UpdateEntityJob threw an unhandled Exception:
NHibernate.Exceptions.GenericADOException: could not load an entity: [Sage.SalesLogix.Entities.Lead#Q6UJ9A2D2N1Y][SQL: SELECT lead0_.LEADID as LEADID120_0_, lead0_.CREATEUSER as CREATEUSER120_0_, lead0_.CREATEDATE as CREATEDATE120_0_, lead0_.MODIFYUSER as MODIFYUSER120_0_, lead0_.MODIFYDATE as MODIFYDATE120_0_, lead0_.ASSIGNDATE as ASSIGNDATE120_0_, lead0_.BUSINESSDESCRIPTION as BUSINESS7_120_0_, lead0_.COMPANY as COMPANY120_0_, lead0_.COMPANY_UC as COMPANY9_120_0_, lead0_.CREDITRATING as CREDITR10_120_0_, lead0_.DATAQUALITY as DATAQUA11_120_0_, lead0_.DESCRIPTION as DESCRIP12_120_0_, lead0_.DIVISION as DIVISION120_0_, lead0_.DONOTSOLICIT as DONOTSO14_120_0_, lead0_.EMAIL as EMAIL120_0_, lead0_.EMPLOYEES as EMPLOYEES120_0_, lead0_.FAX as FAX120_0_, lead0_.FIRSTNAME as FIRSTNAME120_0_, lead0_.HOMEPHONE as HOMEPHONE120_0_, lead0_.IMPORTID as IMPORTID120_0_, lead0_.IMPORTSOURCE as IMPORTS21_120_0_, lead0_.INDUSTRY as INDUSTRY120_0_, lead0_.INTERESTS as INTERESTS120_0_, lead0_.ISPRIMARY as ISPRIMARY120_0_, lead0_.LASTCALLDATE as LASTCAL25_120_0_, lead0_.LASTNAME as LASTNAME120_0_, lead0_.LASTNAME_UC as LASTNAME27_120_0_, lead0_.MIDDLENAME as MIDDLENAME120_0_, lead0_.MOBILE as MOBILE120_0_, lead0_.NEXTCALLDATE as NEXTCAL30_120_0_, lead0_.NOTES as NOTES120_0_, lead0_.PREFERRED_CONTACT as PREFERRED32_120_0_, lead0_.PREFIX as PREFIX120_0_, lead0_.PRIORITY as PRIORITY120_0_, lead0_.REVENUE as REVENUE120_0_, lead0_.SICCODE as SICCODE120_0_, lead0_.STATUS as STATUS120_0_, lead0_.SUFFIX as SUFFIX120_0_, lead0_.TICKER as TICKER120_0_, lead0_.TITLE as TITLE120_0_, lead0_.TOLLFREE as TOLLFREE120_0_, lead0_.TYPE as TYPE120_0_, lead0_.USERFIELD1 as USERFIELD43_120_0_, lead0_.USERFIELD2 as USERFIELD44_120_0_, lead0_.USERFIELD3 as USERFIELD45_120_0_, lead0_.USERFIELD4 as USERFIELD46_120_0_, lead0_.USERFIELD5 as USERFIELD47_120_0_, lead0_.USERFIELD6 as USERFIELD48_120_0_, lead0_.USERFIELD7 as USERFIELD49_120_0_, lead0_.USERFIELD8 as USERFIELD50_120_0_, lead0_.USERFIELD9 as USERFIELD51_120_0_, lead0_.USERFIELD10 as USERFIELD52_120_0_, lead0_.WEBADDRESS as WEBADDRESS120_0_, lead0_.WORKPHONE as WORKPHONE120_0_, lead0_.DONOTEMAIL as DONOTEMAIL120_0_, lead0_.DONOTFAX as DONOTFAX120_0_, lead0_.DONOTMAIL as DONOTMAIL120_0_, lead0_.DONOTPHONE as DONOTPHONE120_0_, lead0_.LeadNamePFL as LeadNam59_120_0_, lead0_.LeadFullName as LeadFul60_120_0_, lead0_.LeadNameFL as LeadNameFL120_0_, lead0_.LeadNameLF as LeadNameLF120_0_, lead0_.CREATESOURCE as CREATES63_120_0_, lead0_.GLOBALSYNCID as GLOBALS64_120_0_, lead0_.APPID as APPID120_0_, lead0_.TICK as TICK120_0_, lead0_.C_SEGMENT_TYPE as C67_120_0_, lead0_.C_TERRITORY as C68_120_0_, lead0_.C_DUNS_NUMBER as C69_120_0_, lead0_.C_TRADESTYLE as C70_120_0_, lead0_.C_ILEC_CLLI11 as C71_120_0_, lead0_.C_PARENT_HQ_NAME as C72_120_0_, lead0_.C_HQ_DUNS_NUMBER as C73_120_0_, lead0_.C_DOMESTIC_ULTIMATE_NAME as C74_120_0_, lead0_.C_MAIL_STREET_ADDRESS1 as C75_120_0_, lead0_.C_MAIL_CITY as C76_120_0_, lead0_.C_MAIL_ZIP as C77_120_0_, lead0_.C_MAIL_STATE as C78_120_0_, lead0_.C_EMP_HERE as C79_120_0_, lead0_.C_EMP_TOTAL as C80_120_0_, lead0_.C_YEAR_STARTED as C81_120_0_, lead0_.C_PRIMARY_SIC_2_DIGIT_CODE as C82_120_0_, lead0_.C_EST_LINES as C83_120_0_, lead0_.C_EST_SPEND as C84_120_0_, lead0_.C_LATITUDE as C85_120_0_, lead0_.C_DOMESTIC_ULTIMATE_DUNS_NUM as C86_120_0_, lead0_.C_LONGITUDE as C87_120_0_, lead0_.C_ACCOUNT_MANAGERID as C88_120_0_, lead0_.C_ACCOUNT_OWNERID as C89_120_0_, lead0_.C_DATE_IMPORTED as C90_120_0_, lead0_.C_MAIL_STREET_ADDRESS2 as C91_120_0_, lead0_.C_CURRENT_PROVIDER as C92_120_0_, lead0_.C_NO_PHONES as C93_120_0_, lead0_.C_TERM_EXP_DATE as C94_120_0_, lead0_.C_TERM_LENGTH as C95_120_0_, lead0_.C_TERM_RENEWAL_DATE as C96_120_0_, lead0_.STB_DATE as STB97_120_0_, lead0_.MAINPHONE_EXT as MAINPHONE98_120_0_, lead0_.INSIDE_SALESREP_ID as INSIDE99_120_0_, lead0_.LGT_ID as LGT100_120_0_, lead0_.LEAD_USER_TYPE as LEAD101_120_0_, lead0_.IMPL_TIME as IMPL102_120_0_, lead0_.INTERESTED_PROD as INTERESTED103_120_0_, lead0_.PMT_PROCESSOR as PMT104_120_0_, lead0_.MPLS as MPLS120_0_, lead0_.IP_ADD as IP106_120_0_, lead0_.NUM_LOCATIONS as NUM107_120_0_, lead0_.REFERRAL_METHOD as REFERRAL108_120_0_, lead0_.ACCT_CLASSIFICATION as ACCT109_120_0_, lead0_.REFERRAL_NAME as REFERRAL110_120_0_, lead0_.REFERRAL_EMAIL as REFERRAL111_120_0_, lead0_.REFERRAL_CALLCTR as REFERRAL112_120_0_, lead0_.SPAM_FIELD as SPAM113_120_0_, lead0_.OMS_NUM as OMS114_120_0_, lead0_.PAGE_VERSION as PAGE115_120_0_, lead0_.IS_QUALIFIED_APPT as IS116_120_0_, lead0_.IS_XFERRED_AE as IS117_120_0_, lead0_.INT_PRODS as INT118_120_0_, lead0_.INT_PROGRAMS as INT119_120_0_, lead0_.UFPC_FRANCHISE as UFPC120_120_0_, lead0_.SF_PHONE2 as SF121_120_0_, lead0_.SF_PHONE2_EXT as SF122_120_0_, lead0_.SF_CONTACT2_NAME as SF123_120_0_, lead0_.SF_CONTACT2_TITLE as SF124_120_0_, lead0_.SF_CONTACT2_EMAIL as SF125_120_0_, lead0_.LEADPROMOCODE as LEADPR126_120_0_, lead0_.POSTPROCESSINGINSTRUCTIONS as POSTPR127_120_0_, lead0_.ACCOUNTMANAGERID as ACCOUN128_120_0_, lead0_.LEAD_ADDRESSID as LEAD129_120_0_, lead0_.LEADSOURCEID as LEADSO130_120_0_, lead0_.SECCODEID as SECCODEID120_0_, lead0_.QUALIFICATION_CATEGORYID as QUALIF132_120_0_ FROM LEAD lead0_ WHERE lead0_.LEADID=?] ---> System.Data.OleDb.OleDbException: Unable to initialize data dictionary.
   at System.Data.OleDb.OleDbConnectionInternal..ctor(OleDbConnectionString constr, OleDbConnection connection)
   at System.Data.OleDb.OleDbConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.OleDb.OleDbConnection.Open()
   at Sage.Platform.Data.DataServiceConnectionProvider.GetConnection()
   at NHibernate.AdoNet.ConnectionManager.GetConnection()
   at NHibernate.AdoNet.AbstractBatcher.Prepare(IDbCommand cmd)
   at NHibernate.AdoNet.AbstractBatcher.ExecuteReader(IDbCommand cmd)
   at NHibernate.Loader.Loader.GetResultSet(IDbCommand st, Boolean autoDiscoverTypes, Boolean callable, RowSelection selection, ISessionImplementor session)
   at NHibernate.Loader.Loader.DoQuery(ISessionImplementor session, QueryParameters queryParameters, Boolean returnProxies)
   at NHibernate.Loader.Loader.DoQueryAndInitializeNonLazyCollections(ISessionImplementor session, QueryParameters queryParameters, Boolean returnProxies)
   at NHibernate.Loader.Loader.LoadEntity(ISessionImplementor session, Object id, IType identifierType, Object optionalObject, String optionalEntityName, Object optionalIdentifier, IEntityPersister persister)
   --- End of inner exception stack trace ---

Server stack trace:
   at Sage.Scheduling.Core.RemotingHelpers.SubstituteCustomExceptions(Action action)
   at Sage.Scheduling.Core.RemoteJob.Execute(IJobExecutionContext context)
   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.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

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 Quartz.IJob.Execute(IJobExecutionContext context)
   at Sage.Scheduling.Server.LocalJob.<>c__DisplayClass3.<Execute>b__1()
   at Sage.Scheduling.Core.RemotingHelpers.RestoreExceptionStackTraces(Action action)
   at Sage.Scheduling.Server.LocalJob.Execute(IJobExecutionContext context)
   at Quartz.Core.JobRunShell.Run()

For more information, see Help and Support Center at



Gold Super Contributor
Posts: 3,087
Registered: ‎03-19-2009

Re: WC 03b, can't update leads from the list view

Did you try re-building XMLSCHEMA?

RJ Ledger - +1 603.369.3047 x101
".. Innovators in Mobility - Experts in Workflow Automation..." - blog:
New Member
Posts: 16
Registered: ‎02-18-2011

Re: WC 03b, can't update leads from the list view

I rebuilt the XML schema via a couple of the methods i found via web search.

Unfortunatly, I think this is an Oracle 03b bug.  So tired of this....

Posts: 629
Registered: ‎04-24-2009

Re: WC 03b, can't update leads from the list view

It looks like the underlying error is "Unable to initialize data dictionary". You should take a look at the following possible solutions:





New Member
Posts: 16
Registered: ‎02-18-2011

Re: WC 03b, can't update leads from the list view



Thanks, but it looks like all these are environment related.  I've reproduced this on three systems/environmnts/databases, it only gets thrown when attempting to update leads, and it started with core03b. 


I'm fairly convinced this is an Oracle 03b bug.  What I'd really like to do is find a workaround.  Set up a server for a small group of marketing users to reassign leads and nothing else.  I'm sure if i start mixing/matching dlls other stuff will break, but in this case I would not worry about that.  And, I know a core02 web instance does not play well with a core03b database.


Any thoughts?