XI error

[Former Member]

import configuration scenarios in ID.

error SM58, no service for system XXX in ID.

I can't figure out what wrong it is.

But when I delete the scenario, and do it again, the scenario works.

Is it normal or any wrong?

Thanks.

[Former Member]

because of failed to refrech cache.

[Former Member]

Hi,

Check the Last Reply from the Posters in these threads

Regards

Seshagiri

[Former Member]

Hi Peng,

I faced same problem when i work on one of my scenario.

you have to check your cache and refresh your cache.

Thanks

Vikranth

[vijay_b4]

Hi Shen,

The cache refreshing is a task in XI to get the latest copy of the objects created or changed into the cache of the XI server. usually it is done automatically.But some times manually we have to refresh the cache.May be in your requirement cache is the problem.

sxi_cache - this tcode is used to manually refresh the cache and also to view the status of the objeccts in the cache. (/people/sravya.talanki2/blog/2005/12/02/sxicache--ripped-off)

There are 2 types of caches.....

CPA cache - is your Collaboration profile agreement cache, ie to mean it will contains the cache copy of all objects created during configuration time (ID).CPA (Collaboration profile agreement )Cache-mainly for J2EE engine/Adapter engine.

About Cache Monitoring-

http://help.sap.com/saphelp_nw2004s/helpdata/en/92/2fd93f130f9115e10000000a155106/content.htm

Runtime cache - it will contain cache copies of all the objects in XI (IR/ID)

and active version of all your objects during runtime.

Check this.......

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1a69ea11-0d01-0010-fa80-b47...

Reward points if this helps

Regards

Pragathi.

[Former Member]

HI,

This kind of thing normally happen if the Cache is filled with other execution instances. After deleteing ..and creating again may had refresh the instance.

Normally refreshing the cache could solve this kind of problem

Thanks

Swarup

[Former Member]

Check the cache of your system.

I feel cache is not getting refreshed properly.

Gaurav Jain