ITS Service name not specified error --- Urgent solution required..

[Former Member]

Hi,

We have downloaded SRM 3.0 Business Package and imported in the SAP EP 6.0 SP11 on WAS 6.40.

We have created a system SRM and an alias SRM1 in the EP and have given ITS path and host name in the system properties.

The first page of the SRM iview for example "Shop" in EP gets displayed properly. But later, when we click on any link in the iview, we are getting the following error:

<b>No Service Name Specified</b>

Your request did not contain a service name. Please provide a service name as part of the URL.

Example URL:

<b>http://.../scripts/wgate/CreateSO/!</b>

Could anyone please help us out in solving this problem.

Thanks much in advance,

Sunitha.S

[Former Member]

Try to move the mouse over the link.

The url corresponding must be "http://<its_server>/scripts/wgate/<service_name>/!".

Is it true?

Regards,

Gianluca

[former_member316351]

Hello,

Sounds like a problem with the template that is creating the URL. Are you using BBPSTART and the Integrated ITS 6.40? The URL you should be using should NOT have "/scripts/wgate" in it. Check note 851940 if this is the case.

Regards,

Edgar Chuang

[Former Member]

I'm getting the same error when i create a transactional iView , How did you solve it?..

[Former Member]

hi,

For SRM 3.0,you will have to use External ITS on EP.There the URL would be in the format " http://hostname/scripts/wgate/bbpstart/! ".

Also make sure all the ITS settings are done on SRM 3.0(trasncn SE80) and all the services have been published on the ITS port.

HTH.

BR,

Disha.

Pls reward points for useful answers.

[Former Member]

The error "No Service Name Specified" means that the URL to the ITS (hostname, port, script path) is working otherwise the ITS wouldn't be able to answer with an error message.

But the URL is either lacking the bang ( '!' ) or the question mark ( '?' ) before the parameters start:

/scripts/wgate/webgui/?~transaction=SU01&...

/scripts/wgate/webgui/!~transaction=SU01&...

Another reason could be that the ~session cookie got lost somewhere and then the user doesn't find back to his previous session and therefore it is unknown which service the user was running.

But check for ! and ? first.

best regards

Gerd