Hi LJ
I had to downgrade to version 1.5.0_06 for my Admin Tool 7.1 to initialize
properly. But that version didn't seem to work with Admin 7.0.0 Patch002
though which I have on another machine, so it seems to be completely
variable.
Another error I have had which may or may not be related is as follows:
ERROR: URI not found ns1.xsd
Additional Details:
C:\Program Files\AR System\Admin\ns1.xsd (The system cannot find the file
specified)
com.bmc.arsys.ws.util.ARWSException: URI not found ns1.xsd
at com.bmc.arsys.ws.util.WsdlUtil.newDocument(WsdlUtil.java:213)
at com.bmc.arsys.ws.util.WsdlUtil.newDocument(WsdlUtil.java:232)
at
com.bmc.arsys.ws.wsdl.XMLSchemaParser.extractFormDefaultValues(XMLSchemaPars
er.java:231)
at
com.bmc.arsys.ws.wsdl.XMLSchemaParser.extractFormDefaultValues(XMLSchemaPars
er.java:278)
at
com.bmc.arsys.ws.wsdl.XMLSchemaParser.parseXMLSchema(XMLSchemaParser.java:29
5)
at
com.bmc.arsys.ws.wsdl.XMLSchemaParser.<init>(XMLSchemaParser.java:121)
at
com.bmc.arsys.ws.wsdl.WsdlParser.createMappingDoc(WsdlParser.java:179)
at com.bmc.arsys.ws.wsdl.WsdlParser.parseWsdl(WsdlParser.java:121)
at
com.bmc.arsys.ws.util.WsdlAdminInterface.parseWsdl(WsdlAdminInterface.java:3
99)
at
com.bmc.arsys.ws.util.WsdlAdminInterface.parseWSDLIntoMappingString(WsdlAdmi
nInterface.java:198)
There's no obvious reference to ns1.xsd in the wsdl - does anyone have any
idea what this error referes to?
Regards
David Sanders
Remedy Solution Architect
Enterprise Service Suite @ Work
==========================
ARS List Award Winner 2005
Best 3rd party Remedy Application
See the ESS Concepts Guide
tel +44 1494 468980
mobile +44 7710 377761
email [EMAIL PROTECTED]
web http://www.westoverconsulting.co.uk
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of LJ Longwing
Sent: Friday, February 29, 2008 5:30 PM
To: [email protected]
Subject: Re: 7017
I did lookup the post, I do appreciate your time replying. I'll see what I
can figure out on this side and reply back to the list with a definitive
answer when I get a chance
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Rabi Tripathi
Sent: Friday, February 29, 2008 10:21 AM
To: [email protected]
Subject: Re: 7017
LJ:
Ok, you want to check what's immediately below the key I mentioned. The
numbers there will give you JRE versions you have. It seems you have JRE
1.6.0.
My best guess is Remedy Admin doesn't like your version of JRE. Try other
versions, such as 1.4.2_16 or 1.5.0_06.
Multiple versions can coexist ok.
I don't know if you took the trouble to lookup the post I mentioned before
or not.
In that post I say that my Remedy Admin 7.1 did NOT work with JRE 1.4.2_13.
Then I had them install JRE
1.4.2_16 and 1.5.0_06. That did the trick. I'm not sure which of the two
made it work.
The trouble is that in the past when the matrix states JRE version x or
higher is required, I have seen that some higher versions don't work, so
it's worth trying the minimum they mention or some of the higher ones to see
which one works.
For Remedy Admin 7.1, I can't even find out the minimum required version.
Compatibility matrix doesn't state anything. Try 1.5.0_06. If that doesn't
work, try 1.4.2_16.
--- LJ Longwing <[EMAIL PROTECTED]> wrote:
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
