cancel
Showing results for 
Search instead for 
Did you mean: 

Last query refresh failed due to internal errors; contact your admin?

Former Member
0 Kudos

Hello All,

We are using SRM 7.0

When the user login in to SRM Front end Portal he is getting below error.

Last query refresh failed due to internal errors; contact your admin.

this error is happing for many of the user.

Please sugguest me how to troubleshoot this issue

Accepted Solutions (1)

Accepted Solutions (1)

ivy_li
Active Contributor
0 Kudos

Hi Kiran,

The error indicates that the POWL query is currently locked, for this
you can check SM12 and release/delete any locks existing for the
POWL application area there.

I would suggest you educate the users about quick clicking/navigation
around the POWL especially if you have implemented auto refresh or
refresh on query switch (parameter REFRESHQ=X or REFRESHA=X).

It is advisable to make sure that the selection criteria in the initial
queries are kept as simple as possible to ensure quicker response time
on initial POWL access, i.e. if the initial query in the ESS status
query was All Shopping Carts, I would suggest to restrict the selection
to perhaps 1 day or 1 week as a default to ensure the query is quickly
executed. Once the query is read and opened then the criteria can be
changed and the results updated in the POWL list.

Finally, there is the option to enable shadowing in the POWL which would
allow access to the same query by multiple users thus negating the error
you have experienced, however this shadowing also has its drawbacks
since the use of shadowing removes the ability to personalize and define
new queries by users once it is enabled.

Best regards,

Ivy

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello Kiran,

This is a generalised error when working in any POWL objects in SRM.

If you are using multiple logins of the same user when each one are accessing you

will be getting this error.

Use working o n POWL objects after some time it will work

Regards

G.Ganesh Kumar

Former Member
0 Kudos

Hello All

Thanks for the solution

Regards

Kiran.S

Former Member
0 Kudos

Hi Kiran,

Check transaction ST22 for the dump with the respective user ID.

Clear the Cache through report POWL_D01 for the user id from which you are trying to search POWL.

Best Regards,

Anil

Former Member
0 Kudos

This worked for me.thank you Anil