cancel
Showing results for 
Search instead for 
Did you mean: 

Error while accessing portal.....

Former Member
0 Kudos

Hi Experts,

We have installed EP 7.0 SP 9. It's working fine, but yesterday we met the problem, we can't able to access portal.

After giving username and password, its opening the portal homepage with the following JavaScript Error on the taskbar.

<b>1. 'disable personalize' is undefined

2. 'EPCM.getSAPTop().gHistoryFrameworkObj' is null or not an object

3. 'ActiveTrackingEntryIndex' is null or not an object</b>

After showing errors above, its showing the portal HomePage. If we click on any roles is loading with busy symbol, we can't able to navigate to any role or any workset after that.

Please tell me some solution for this, it's very urgent.

Points will be awarded.

Regards,

Chinnadurai.R.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Chinna,

If you want go back earlier stage of your portal.

Programs->Accessories-->SystemTools->System Restore

Choose the correct earlier point :SystemRestore Point

This is the one way to do. Once it's worked for me.

Decide yourself and go ahead.

Rgds

SS

Former Member
0 Kudos

did you find a solution to this problem? i have a similar error in my custom framework

Thanks

Former Member
0 Kudos

At portal homepage we have javascript, something like this...

EPCM.subscribeEvent("urn:com.sapportals:navigation", "PersonalizePortalDisable", onPersonalizePortalDisable);


function openNewPortalWindow()
{
	
		var navTarget = EPCM.getSAPTop().gHistoryFrameworkObj.GetActiveTrackingEntryValue().URL;
		EPCM.doNavigate(navTarget, 2);
	
}

Seems, you have a problem with EPCM. Reason may be wronge configuration of the J2EE Engine. But you says it was working properly and problem occured suddenly. Can you please check following,

Follow the WIKI related to EPCM or note 516249.

1. Enter the J2EE Config tool.

2. drill down: alone/services/http

3. on the right hand side, click on NotZippedFile.

4. on the bottom, add at the end: , .js

5. Apply the changes

6. restart the J2EE.

Surely this will solve the problem.

Regards,

Nitin

[Please award points if it is helpful]