on ‎2007 Jun 08 8:07 AM
Hello Everybody
I am new to XI administration. I am working on XI 3.0 system with WAS 6.40, windows 2003 server and Orcale DB 9.2.1.4.
I upgraded XI with latest kernel patch level 155, SAP Basis patch 19, SAP ABA Patch level 19. I checked in SPAM and noted the successful application of patches. I checked the kernel patch level in status.
As a next step when I was applying J2EE patches SP 19, using SAPINST.EXE file I got an error in a Wizard in the 17th step. At that time based on some advice I have restarted the ABAP engine that was up earlier (keeping SAPINST wizard open). Now to my dismay the ABAP engine also went down (disp+work.exe status displayed as stopped). I found that this error was due to lack of connectivity to the database. I resolved this by retaining a connection between the database and ABAP engine. Thereafter the Java engine was also up and I upgraded the J2EE engine patch level SP20. So I think everything is fine till this point.
Then I logged on to the XI system and I executed the transaction code SXMB_IFR. Initially I got 404 not found error. Then I referred the docment 'how to handle caches' and 'post installation activities'. I found that some services were not visible in the visual adminstrator. On the path cluster--> Server --> Services --> Deploy the following are the services that were not visible.
all the services beginning with
sap.com/com.sap.aii*
sap.com/com.sap.xi*
I downloaded all the services from service.sap.com and deployed using SDM tool.
Now I was able to see those services in the visual adminstrator. Now after restarting the server again evrything till this point seems to be working fine. After this I logged on to the XI system successfully.
<b>Now here is the problem...</b>
When I executed the transaction SXMB_IFR I was getting an error again. This time it is dfferent from the above.
<b>"500 Internal Server Error</b>
SAP J2EE Engine/6.40
Application error occurred during request processing.
Details: com.sap.aii.utilxi.prop.api.PropertiesException: Unable to read configuration data (ExchangeProfile/aii.properties)
Exception id: [0008C7E662A0003F00000068000013C00004325EECBAC6F8]"
Exception
An internal error occurred. Contact you XI administrator
Unable to read configuration data (ExchangeProfile/aii.properties)"
Please guide/ help me on this.
Thanks in anticipation, Regards
Suresh
Request clarification before answering.
Check these steps from the OSS notes
<i>Solution
I. If you have configured ICM to forward requests to the J2EE dispatcher and you are running SP12 or earlier, you need to apply the attached patch. The fix for the problem will enter SP13 as a standard release.
1. Make sure you are running SP11 or SP12 of the Engine
2. Download the attached httpSP11.zip or httpSP12.zip
3. Unzip the archive to a temporary directory
4. Deploy the http.sda from the temporary directory as per Note 656711. Make sure you select the option "Update deployed SDAs/SCAs that have any version" from teh Deployment configuration after selecting the sda in the SDM filechooser dialog.
5. The engine will be restarted as part of the deployment
6. If you are still having the problem, then implement section II.
II. The request bytes are reaching the Engine too slowly
1. Start the configtool in <J2EE>/configtool directory
2. Browse the tree in the left pane
cluster-data -> Global server configuration -> services -> http
3. Press the ServletInputStreamTimeout key in the keylist on the right
4. Change the value of the "Value" field at the bottom of the right paneto the preferred one (in milliseconds).
-1 means there is no timeout - that is unless the full request comes into a single chunk, an error will be thrown
30000 means the Engine would wait for 30 seconds for any byte to be entered in the stream.
1728000000 means the Engine would wait for 20 days for any byte to be entered in the stream
5. Press the "Set" button in the top-right corner
6. Select from the menu File -> Apply and confirm all popups.
7. Restart the Engine for changes to take effect
</i>
regards
krishna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Krishnamoorthy
Thanks for your reply.
I changed the said value to '-1' . I restarted the J2EE engine. Again while I logged on into XI system. On executing transaction SXMB_IFR I get the following error.
503 Service Unavailable
SAP J2EE Engine/6.40
Cannot process a request for dynamic resources.
Details: Web Container service is currently unavailable.
Regards
Suresh
Here you go
😎 Error: The error message 503 Service unavailable Application stopped! is displayed.
Description:The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay MAY be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
<b>Possible Tips: Because of J2EE application com.sap.aii.af.ms.app not active
Try to (re)start the application using the Visual Administrator Choose Server --> Services --> Deploy --> View on Application or restart the J2EE engine
The problem is that not all J2EE services can be started by the J2EE. i.e Start the Visual Administrator and select Server->Services->Deploy in the tree on the left. On the right-hand side, choose the Runtime tab page. You see a tree in the right window with all applications if you select the APPLICATION radio button. Check if they are running, otherwise choose Start. Usually the J2EE engine starts all services automatically.
Refer SAP Note 803145,807000,791655
regards
krishna</b>
| User | Count |
|---|---|
| 15 | |
| 9 | |
| 6 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.