Alert Inbox Problems

[Former Member]

Hi all, I have 2 problems with the alert inbox.

1. I can see the long-text information of a error infomation, but meanwhile, if my colleague use the same login account as mine to check the same error message, the short text is ok, but the long text is disappear.

2. In follow-on activities, there's a "Message Monitor" which links to http://sapxidev.companyname.com:8000/sap(bD1lbiZjPTEwMCZkPW1pbg==)/bc/bsp/sap/alertinbox/&messageid=...

After opened it, I got following error info:

Business Server Page (BSP) error

"

What happened?

Calling the BSP page was terminated due to an error.

SAP Note

The following error text was processed in the system:

Error type:

Your SAP Business Server Pages Team

"

Hope you can help me.

Thanks

[prabhu_s2]

also check with the reply from bary neaves:

[Former Member]

HI,

See below answer..

<i>The SICF service is used to check if the ALERTINBOX is activated. Before doing this , I would suggest you code to T code - SE38.

In the program , type RSALERTTEST and then click on EXECUTE button ( F8 ). In the next window, it will ask you for your ALERTCATEGORY. Just give the name of your ALERT CATEGORY and click EXECUTE.

If you have configured your alerts correctly, you will receive a message that tells ALERT IS GENERATED and will give the ALERT ID.

Now, go to your Run TIme workbench and then select ALERT INBOX and see if you have got the ALERT message in your ALERT INBOX.

If yes, then your ALERT INBOX service has been activated</i>

see below thread

/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--step-by-step - Alert Configuration

/people/michal.krawczyk2/blog/2005/09/09/xi-alerts--troubleshooting-guide - Trouble shoot alert config

https://www.sdn.sap.com/irj/sdn/advancedsearch?query=alerts&cat=sdn_weblog

http://help.sap.com/saphelp_nw2004s/helpdata/en/2b/d925bf4b8a11d1894c0000e8323c4f/content.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/9c/34193cb4f5131de10000000a11405a/content.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/8a/3e2d4105f8d92be10000000a1550b0/content.htm

check this thread, it talks about couple of OSS notes. this may be of help to you

Regards

Chilla..

<i>Points rewarded if it is usefull</i>

[prabhu_s2]

If u had checked Dynamic Text option: It is used when you want to trigger Alerts from a BPM. For Alerts without BPM do not select the Dynamic Text optin. Create the Container Elements and use them with & & in your Alert Long and Short Text.

and for the second issue check with notes 768456 and 750287 , may u ned to check:

[Former Member]

Hi Prabhu,

The Dynmamic Text option has not been checked, and I already use the && in container element.

When I log in the alert inbox in my computer, everything is okay, don't know why it happens whith other's.

About the 2nd problem, the alert inbox bsp has already been activated, it links direct to http://sapxidev.companyname.com:8000/sap/bD1lbiZjPTEwMCZkPW1pbg==)/bc/bsp/sap/alertinbox/, I've tested it.

The the link in "follow-on activities" links to In follow-on activities, there's a "Message Monitor" which links to http://sapxidev.companyname.com:8000/sap(bD1lbiZjPTEwMCZkPW1pbg==)/bc/bsp/sap/alertinbox/&messageid=..., that's why the problem happens.

Hope you can help me

[prabhu_s2]

check with the login langauge and does toher have the same profile setting as ur id?

[Former Member]

Bingo, solved my 1st problem, thank you:)

[bhavesh_kantilal]

Have faced the second issue as well once.

It was due to some network and firewall issues. When we tried to access the Message Monitor link we were unable to access, but the same worked from a Client Location.

If the server is located in a different geography, maybe askingsomebody there to access the link should help.

Regrads

Bhavesh

[Former Member]

I'm at the client location. So I don't think it is the answer:(

[Former Member]

Another problem I found is that after I used the SXMS_TO_ADAPTER_ERRTXT container element in long text, the information is truncated and only the 1st row appeared. I've applied the note 941489, but it still doesn't work.