Question

2
Replies
212
Views
Close popover
Mark Olive (MARKO929)
Cahaba Gba

Cahaba Gba
US
MARKO929 Member since 2011 11 posts
Cahaba Gba
Posted: October 19, 2016
Last activity: November 29, 2016
Closed

InvalidReferenceException .pyRuleName

I am getting an error in our PEGA logs that reads:

 (Commons_Data_Interface_.Action) INFO  gbautilwas1.corp.bcbsal.org|XX.XX.XX.XX|SOAP|CGBACTI|Event|AgentCallNotification|AB6A8EA7934A1AF91FCAF24383BA5B810 - LogServiceInOutTime*Application:CC*ID:151641000006927*InTime:20160307T213925.282 GMT*OutTime:20160307T213925.300GMT*TimeDifference:18.0*Msg:ScreenPop2016-03-07 15:39:33,168 [   WebContainer : 12] (  rd.resolve.SqlReportResolver) ERROR gbautilwas1|gba10004548.corp.bcbsal.org - An error occured during resolving the report definition - InvalidReferenceException    .pyRuleName     Cannot use an unexposed property as there is no BLOB column for the class: Data-Rule-Locking com.pega.pegarules.data.internal.rd.reference.InvalidReferenceException: InvalidReferenceException      .pyRuleName     Cannot use an unexposed property as there is no BLOB column for the class: Data-Rule-Locking

 

I was looking up this error and found the PDN article 'https://pdn.pega.com/support-articles/invalidreferenceexception-post-cpm-713-upgrade'. We are on CPM 7.1.3 and PEGA 7.1.6. This article references an error message simliar, but no exactly like our error message. My question is, will the fix listed in the article also apply to our log file error message?

***Updated by Moderator: Marissa to remove proprietary information from post; moved from Product Support Community to Pega Customer Service***

***Updated by moderator: Maryrita to add Group Tag***

 

Moderation Team has archived post