Error:--Can anyone help me...........

Hi All,

I am getting following error while installing following .sar filesof e-Gate:- MFS,SunJavaSystemeWay,SybaseeWay,MQSerieseWay and eIndex

Error is:--

Install Directory File Name is: C:\JavaCAPS51\repository\upload\C49D9F4CBEF0B0AE5E697633F3680975\gsr76487\insta ll.xml

Installation Started, Please wait ...

***********************************************

Refer to this upload session's Logs at:

C:\JavaCAPS51\repository\server\logs\eManagerInstaller-1157359911268.log

1 :

2 : install:

3 : [InstallRepAPI] API class name: com.stc.mfs.repository.impl.MfsManagerImpl

4 : [InstallRepAPI] Connecting to Repository: http://axa-foe649:12000/Hexrepo

5 : [InstallRepAPI] API SYSTEM ID: MfsManager/SBYN0001

6 : [InstallRepAPI] Adding JAR files for API: [C:\JavaCAPS51\repository\upload\C49D9F4CBEF0B0AE5E697633F3680975\gsr76487\lib\ mfsrepository.jar, C:\JavaCAPS51\repository\upload\C49D9F4CBEF0B0AE5E697633F3680975\gsr76487\lib\m fsbpi.jar]

7 :

8 : BUILD FAILED

9 : file:C:/JavaCAPS51/repository/upload/C49D9F4CBEF0B0AE5E697633F3680975/gsr76487/ install.xml:20: com.stc.repository.RepositoryException:

10 : Could not get information for an object with OID Hexrepo of type {01000000-23A61B690D0100-0A012E8C-01}

11 :

12 : No server error detail

13 :

14 : Total time: 40 seconds

***********************************************

Reported execute exit value: 1

Buildfile: C:\JavaCAPS51\repository\upload\C49D9F4CBEF0B0AE5E697633F3680975\gsr76487\insta ll.xml

Executing installation script failed.

Failed to execute ant:

Executing installation script failed.

Adding product MFS to the Failed List.

Executing installation script failed.

[1818 byte] By [sudeepjm] at [2007-11-26 9:54:44]
# 1
What type of server does your repository reside? I had the same problem on our AIX installation and found that the server lacked tmp space. When we cleaned and added space to tmp all worked well.
bgrant88 at 2007-7-7 1:14:15 > top of Java-index,Java Enterprise System,Java Composite Application Platform Suite -- General Discussion...
# 2

Try examining the temp directory on your box. I haven't done an Win install for CAPS but have done a few Solaris installs and have come across an eway or 2 that doesn't get cleaned out of the tmp directory after another user's install. So when I go to upload the same component for a different instance of CAPS it then chokes (though I don't recall seeing the specific exception you detail). Directory I had to remove on Solaris (or Unix) is /var/tmp/XSDManager (find Win equivalant). I found that by removing the XSDManager directory that my problem was resolved and could continue the component upload (though the XSDManager would again need to be removed afterwards or the next person doing install of same component for different CAPS instance would run into same snag). The problem may not be the XSDManager in your case but still may be a leftover directory in your tmp directory that didn't get cleaned up by a previous install of those components. If this is the first and only instance of CAPS that you are installing on that box then this info is of little help.

hizey1 at 2007-7-7 1:14:15 > top of Java-index,Java Enterprise System,Java Composite Application Platform Suite -- General Discussion...