9.5.2 Error: Prolog procedure line (9): Unable to register s

Post Reply
rfielden
Posts: 122
Joined: Wed Aug 06, 2008 2:50 pm
OLAP Product: TM1
Version: 9.5.2
Excel Version: 2007
Location: Tega Cay, SC

9.5.2 Error: Prolog procedure line (9): Unable to register s

Post by rfielden »

We have had a TI process running the past four yrs with no issues and yesterday started receiving the err msg:

Error: Prolog procedure line (9): Unable to register subset

The Prolog is:

If(SubsetExists('Accounts', 'Store PL Detail Zero Suppressed New') = 1);
SubsetDestroy('Accounts', 'Store PL Detail Zero Suppressed New');
EndIf;

SubsetCreate('Accounts', 'Store PL Detail Zero Suppressed New');
#SubsetDeleteAllElements('Accounts', 'Store PL Detail Zero Suppressed New');
SubsetExpandAboveSet('Accounts', 'Store PL Detail Zero Suppressed New', 1);

We are currently bouncing the server and if that doesn't work look to refresh data from backup.

Does anybody have any other advise they are willing to provide on this issue?

Thanks, Rick.
User avatar
jim wood
Site Admin
Posts: 3958
Joined: Wed May 14, 2008 1:51 pm
OLAP Product: TM1
Version: PA 2.0.7
Excel Version: Office 365
Location: 37 East 18th Street New York
Contact:

Re: 9.5.2 Error: Prolog procedure line (9): Unable to regist

Post by jim wood »

The only time I have seen an error when creating a subset is when the delete has failed because the subset is part of a view. I would check your views just in case. I do feel however that you are taking the right approach bouncing the server. We have some funnies with TM1 retaining values in memory even when things have been deleted. Hopefully you just have a memory blip,

Jim.
Struggling through the quagmire of life to reach the other side of who knows where.
Shop at Amazon
Jimbo PC Builds on YouTube
OS: Mac OS 11 PA Version: 2.0.7
rfielden
Posts: 122
Joined: Wed Aug 06, 2008 2:50 pm
OLAP Product: TM1
Version: 9.5.2
Excel Version: 2007
Location: Tega Cay, SC

Re: 9.5.2 Error: Prolog procedure line (9): Unable to regist

Post by rfielden »

Bouncing the server resolved the issue. Really strange after 4 yrs!
Post Reply