Re: Remedy Test Plan

[Carl Wilson]

Hi Jason,

I think you have hit the nail on the head, if we supply our IP we have no value 
anymore.  The other thing to note is that these take time to produce so why 
would someone just give them away, that is professional suicide.  Many of the 
partner companies make a living out of having teams for testing with their own 
test cases (large teams), again these take time to develop and tweak to get 
correct so why would they give these away for free where there is a business 
for them?

 

AMIGO was the BMC Professional Services upgrade program, so why would they give 
away their IP for free?

 

The older 7.1 Guides actually had unit tests in them that could form the basis 
of testing, however it is not difficult to formulate a plan as the tests are 
very generic in nature.

 

  _  

 

Kind Regards,

 

Carl Wilson

 

 

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Jason Miller
Sent: 25 November 2014 20:29
To: arslist@ARSLIST.ORG
Subject: Re: Remedy Test Plan

 

** 

I agree consultants have them.  But I think the rub there is the consultants 
use those to make a living.  There have been a number of times I have talked to 
people/partners/BMC Professional Services that have the docs/process/whatever I 
am looking for and say we can have them for the low, low price of tens of 
thousands of dollars by using their services.

 

Jason

 

On Tue, Nov 25, 2014 at 12:19 PM, Scott Hallenger  wrote:

I find it hard to belive that not a consultant out there has ever gone through 
an upgrade/deployment and had to have the user population test the newley stood 
up system. Does not have to be an official BMC doc. Just any company that has 
UATd 7.1 ot 7.6. However, my google searches did yield anything either.



On Tue, 11/25/14, Jason Miller  wrote:

 Subject: Re: Remedy Test Plan
 To: arslist@ARSLIST.ORG
 Date: Tuesday, November 25, 2014, 2:49 PM

 **
 I ready it the same way you did.  I wish you
 luck on finding such a document from BMC (and not paying
 Professional Services for it).
 Jason
 On Tue, Nov 25, 2014 at
 10:45 AM, JD Hood 
 wrote:
 **
 OK -- I completely misread the original post
 by Scott Hallenger. I
 thought he was looking for a UAT test plan... He was just
 looking for the upgrade plan. My bad.
 But if anyone
 knows if a BMC "blessed" UAT plan exists, strictly
 for OOB functionality, that would be awesome
 too!
 -JDHood
 On Tue, Nov 25, 2014 at
 1:39 PM, JD Hood 
 wrote:
 Yep - I've looked at the files attached
 to KA404409 (and the
 other related AMIGO pages) and there is nothing that looks
 like a post-upgrade test-plan that could be used to UAT the
 out-of-the-box ITSM -- a test plan that exercises
 the out-of-the-box
 modules to validate out-of-the-box
 functionality.
 Perhaps BMC took
 it down for some reason...
 -JDHood
 On Tue, Nov 25, 2014 at
 12:48 PM, Carin Grobler 
 wrote:
 **
 Look at KA404409 there is templates
 attached 
 On Tue, Nov 25, 2014 at
 11:38 AM, Carin Grobler 
 wrote:
 Are you doing a parallel upgrade or in
 place 
 On Tue, Nov 25, 2014 at
 10:59 AM, JD Hood 
 wrote:
 **
 Paged through every Remedy/Atrium/ITSM
 "Amigo" related page I could find and the only
 spreadsheet I saw was for sizing recommendations.

 Like always with BMC docs,
 this spreadsheet is going to be as easy to find as
 Bigfoot...
 -JDHood

 On Tue, Nov 25, 2014
 at 11:00 AM, Carin Grobler 
 wrote:
 **
 https://communities.bmc.com/docs/DOC-28417


 On Tue, Nov 25, 2014 at
 9:57 AM, Rob Dudley 
 wrote:
 **
 Claire/Scott -

 Can you post a link to this AMIGO program
 you're referring to?  I can't seem to find it
 within the Documentation section on BMC's site.

 Thanks,

 Rob D.

 On Tue, Nov 25, 2014 at
 9:03 AM, LJ LongWing 
 wrote:
 **
 Scott,Docs don't even require a
 login anymore, let alone a support
 contract...
 On Tue, Nov 25, 2014 at
 6:44 AM, Scott Hallenger 
 wrote:
 **
 Cant get in
 there, my clients support expired and they will not
 renew...

  On Monday, November 24, 2014
 2:31 PM, "Sanford, Claire" 
 wrote:


  Look at the AMIGO program in the DOCS
 section on BMC.  There is a great spreadsheet there that is
 basically your plan. 

 -Original Message-
 From: Action Request System discussion
 list(ARSList) [mailto:arslist@ARSLIST.ORG]
 On Behalf Of Scott Hallenger
 Sent: Monday,
 November 24, 2014 10:54 AM
 To: arslist@ARSLIST.ORG
 Subject: Remedy Test Plan

 Would anyone be willing to share a remedy post
 migration/upgrade plan that they may have laying around. Any
 version from 7.1 on would be ok. Any info is better than no
 info. Thanks in advance my fellow listers..

 ___
 UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
 "Where the Answers Are, and have been for
 20 years"

 ___
 UNSUBSCRIBE or access ARSlist 

Re: Creating a jira issue on click of a button on remedy form

[Jason Miller]

Exactly why AR System should not run as root :)

On Wed, Nov 26, 2014 at 10:56 AM, Jarl Grøneng 
wrote:

> **
>
> echo ';rm -rf;'
>
>
> --
> J
>
> 2014-11-26 16:33 GMT+01:00 John Sundberg :
>
>> **
>> Gotta love that REST api.
>>
>> also YAY UNIX!!!
>>
>> BTW - can be pretty dangerous to put all that on the command line.
>>
>> You may want to write your data to a file. … Then post the data from the
>> file.
>>
>> As — somebody could put in an RFE which would kick off your JIRA…
>> Hopefully they don’t do something like
>>
>> Fix bug where people can do `echo “something bad here"`
>>
>>
>>
>> -John
>>
>>
>> On Wed, Nov 26, 2014 at 7:21 AM, MalviyaSaurabh <
>> malviya.saurab...@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> This solved/
>>>
>>> $PROCESS$ /opt/bcs/bin/curl -D- -k -u svc-remedy:password -X POST --data
>>> “$Data1$” -H “Content-Type: application/json”
>>> https://jiradev.company.com/rest/api/2/issue/
>>>
>>> where DATA1 = as follows:
>>> {"fields":
>>>   {"project":
>>>   { "id": "18168"  },
>>>"summary":"Post-Mortem for Remedy *S3 - Major * Outage",
>>>"description":"You have been identified as the post-mortem owner for
>>> Remedy Ticket * 1714111 *. Please update this JIRA within 48
>>> hours
>>> with the following information:  1. Outage Summary - *scout
>>> collector
>>> heartbeat failure! scout collector may have stopped processing monitor
>>> executions*  2. Order of Events  3. Root Cause and Resolution
>>>  4. Improvements Implemented  5. Trends and Risks  6.
>>> Follow-Ups.  The NOC Debrief, within the Remedy ticket, is a
>>> resource
>>> you may use to populate some of this information. Additionally, you will
>>> be
>>> invited to participate in a post-mortem meeting. When you receive the
>>> meeting invite, feel free to forward to others who were involved or
>>> should
>>> also attend. You will be requested to speak in detail to the areas listed
>>> above.",
>>>   "reporter":
>>>   {"name": "repoterlogin"},
>>>   "assignee":
>>>   {"name": "assigneelogin"},
>>>   "issuetype":
>>>   { "id": "11000" }
>>>   }
>>> }
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://ars-action-request-system.1.n7.nabble.com/Creating-a-jira-issue-on-click-of-a-button-on-remedy-form-tp119290p119950.html
>>> Sent from the ARS (Action Request System) mailing list archive at
>>> Nabble.com.
>>>
>>>
>>> ___
>>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>>> "Where the Answers Are, and have been for 20 years"
>>>
>>
>>
>>
>> --
>>
>> *John Sundberg*
>> Kinetic Data, Inc.
>> "Your Business. Your Process."
>>
>> 651-556-0930 I john.sundb...@kineticdata.com
>> www.kineticdata.com I community.kineticdata.com
>>
>>
>>  _ARSlist: "Where the Answers Are" and have been for 20 years_
>
>
> _ARSlist: "Where the Answers Are" and have been for 20 years_
>

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Creating a jira issue on click of a button on remedy form

[Jarl Grøneng]

echo ';rm -rf;'


--
J

2014-11-26 16:33 GMT+01:00 John Sundberg :

> **
> Gotta love that REST api.
>
> also YAY UNIX!!!
>
> BTW - can be pretty dangerous to put all that on the command line.
>
> You may want to write your data to a file. … Then post the data from the
> file.
>
> As — somebody could put in an RFE which would kick off your JIRA…
> Hopefully they don’t do something like
>
> Fix bug where people can do `echo “something bad here"`
>
>
>
> -John
>
>
> On Wed, Nov 26, 2014 at 7:21 AM, MalviyaSaurabh <
> malviya.saurab...@gmail.com> wrote:
>
>> Hi All,
>>
>> This solved/
>>
>> $PROCESS$ /opt/bcs/bin/curl -D- -k -u svc-remedy:password -X POST --data
>> “$Data1$” -H “Content-Type: application/json”
>> https://jiradev.company.com/rest/api/2/issue/
>>
>> where DATA1 = as follows:
>> {"fields":
>>   {"project":
>>   { "id": "18168"  },
>>"summary":"Post-Mortem for Remedy *S3 - Major * Outage",
>>"description":"You have been identified as the post-mortem owner for
>> Remedy Ticket * 1714111 *. Please update this JIRA within 48 hours
>> with the following information:  1. Outage Summary - *scout collector
>> heartbeat failure! scout collector may have stopped processing monitor
>> executions*  2. Order of Events  3. Root Cause and Resolution
>>  4. Improvements Implemented  5. Trends and Risks  6.
>> Follow-Ups.  The NOC Debrief, within the Remedy ticket, is a resource
>> you may use to populate some of this information. Additionally, you will
>> be
>> invited to participate in a post-mortem meeting. When you receive the
>> meeting invite, feel free to forward to others who were involved or should
>> also attend. You will be requested to speak in detail to the areas listed
>> above.",
>>   "reporter":
>>   {"name": "repoterlogin"},
>>   "assignee":
>>   {"name": "assigneelogin"},
>>   "issuetype":
>>   { "id": "11000" }
>>   }
>> }
>>
>>
>>
>> --
>> View this message in context:
>> http://ars-action-request-system.1.n7.nabble.com/Creating-a-jira-issue-on-click-of-a-button-on-remedy-form-tp119290p119950.html
>> Sent from the ARS (Action Request System) mailing list archive at
>> Nabble.com.
>>
>>
>> ___
>> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
>> "Where the Answers Are, and have been for 20 years"
>>
>
>
>
> --
>
> *John Sundberg*
> Kinetic Data, Inc.
> "Your Business. Your Process."
>
> 651-556-0930 I john.sundb...@kineticdata.com
> www.kineticdata.com I community.kineticdata.com
>
>
>  _ARSlist: "Where the Answers Are" and have been for 20 years_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Remedy 8.1 Email Engine - ERROR (623)

[LJ LongWing]

yea, resetting it in the server config only changes the server password,
doesn't update any of the clients to tell them what the password is :).

On Wed, Nov 26, 2014 at 10:21 AM, Sanford, Claire <
claire.sanf...@memorialhermann.org> wrote:

> **
>
> Thanks LJ!!
>
>
>
> That is what I did.  I hard set it in the emaildaemon.properties file and
> it worked!  I had reset it several times in the server config area.  I
> think for some reason it was not talking to or updating the
> emaildaemon.properties file.
>
>
>
> Sometimes all you have to do is ask the world the question and you figure
> it out!
>
>
>
> Claire
>
>
>
>
>
> *From:* Action Request System discussion list(ARSList) [mailto:
> arslist@ARSLIST.ORG] *On Behalf Of *LJ LongWing
> *Sent:* Wednesday, November 26, 2014 11:12 AM
> *To:* arslist@ARSLIST.ORG
> *Subject:* Re: Remedy 8.1 Email Engine - ERROR (623)
>
>
>
> **
>
> Claire,
>
> The authentication failed message is simply that the password it's trying
> is not correct (obviously), so, you could try re-setting the password in
> the server config to what you think it should be, and if that doesn't work,
> you can reset the password in the emaildaemon.properties file
>
>
>
> https://docs.bmc.com/docs/display/public/ars81/EmailDaemon.properties+file
>
>
>
> Follow the directions in that link, utilizing the -p parameter to reset
> the password the daemon is trying to utilize.
>
>
>
> On Wed, Nov 26, 2014 at 10:01 AM, Sanford, Claire <
> claire.sanf...@memorialhermann.org> wrote:
>
> **
>
> I have 8.1 installed on my new test/prod server and the email engine
> starts, but it does not authenticate.
>
>
>
> I have checked the user name and password in the service and it still
> won’t authenticate.
>
>
>
> I have looked in the “normal” areas.
>
>
>
> Config.properties
>
> Ar.cfg
>
> Armonitor.cfg
>
> emaildaemon.properties
>
>
>
> And found nothing out of the ordinary.  I made sure everything matched
> what is in my current (working) emaildaemon.properties file matched in the
> non-working one.
>
>
>
> This is the content of my mail logs:
>
> STOUT.log
>
>
>
> Checking connection to server: REMEDYAPP1.mh.org ...
>
> ERROR (623): Authentication failed;
>
>
>
> Cannot connect.
>
> Checking connection to server: REMEDYAPP1.mh.org ...
>
>
>
> Cannot connect.
>
>
>
>
>
>
>
> STDERR.log
>
> ERROR (623): Authentication failed;
>
> at
> com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown Source)
>
> at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source)
>
> at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown
> Source)
>
> at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source)
>
> at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source)
>
> at
> com.bmc.arsys.emaildaemon.EmailUtil.createARServerUser(EmailUtil.java:1299)
>
> at
> com.bmc.arsys.emaildaemon.LoggingModule.setUserInfo(LoggingModule.java:767)
>
> at
> com.bmc.arsys.emaildaemon.EmailDaemon.startLoggingModule(EmailDaemon.java:125)
>
> at
> com.bmc.arsys.emaildaemon.EmailDaemon.(EmailDaemon.java:96)
>
> at
> com.bmc.arsys.emaildaemon.EmailDaemon.newInstance(EmailDaemon.java:161)
>
> at
> com.bmc.arsys.emaildaemon.EmailDaemon.startMonitor(EmailDaemon.java:903)
>
> at
> com.bmc.arsys.emaildaemon.EmailDaemon.executeComandLine(EmailDaemon.java:609)
>
> at com.bmc.arsys.emaildaemon.EmailDaemon.main(EmailDaemon.java:324)
>
> ERROR (623): Authentication failed;
>
> at
> com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown Source)
>
> at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source)
>
> at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown
> Source)
>
> at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source)
>
> at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source)
>
> at com.bmc.arsys.api.ARServerUser.login(Unknown Source)
>
> at
> com.bmc.arsys.emaildaemon.MonitorModule.checkServer(MonitorModule.java:307)
>
> at
> com.bmc.arsys.emaildaemon.MonitorModule.doWork(MonitorModule.java:99)
>
> at com.bmc.arsys.emaildaemon.ThreadBase.run(ThreadBase.java:302)
>
> at
> com.bmc.arsys.emaildaemon.MonitorModule.run(MonitorModule.java:26)
>
> at java.lang.Thread.run(Unknown Source)
>
> ERROR (623): Authentication failed;
>
> at
> com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown Source)
>
> at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source)
>
> at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown
> Source)
>
> at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source)
>
> at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source)
>
> at
> com.bmc.arsys.emaildaemon.EmailUtil.createARServerUser(EmailUtil.java:1299)
>
> at
> com.bmc.arsys.emaildaemon.EmailDaemon.setUserInfo(EmailDaemon.java:947)
>
> 

Re: Remedy 8.1 Email Engine - ERROR (623)

[Sanford, Claire]

Thanks LJ!!

That is what I did.  I hard set it in the emaildaemon.properties file and it 
worked!  I had reset it several times in the server config area.  I think for 
some reason it was not talking to or updating the emaildaemon.properties file.

Sometimes all you have to do is ask the world the question and you figure it 
out!

Claire


From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing
Sent: Wednesday, November 26, 2014 11:12 AM
To: arslist@ARSLIST.ORG
Subject: Re: Remedy 8.1 Email Engine - ERROR (623)

**
Claire,
The authentication failed message is simply that the password it's trying is 
not correct (obviously), so, you could try re-setting the password in the 
server config to what you think it should be, and if that doesn't work, you can 
reset the password in the emaildaemon.properties file

https://docs.bmc.com/docs/display/public/ars81/EmailDaemon.properties+file

Follow the directions in that link, utilizing the -p parameter to reset the 
password the daemon is trying to utilize.

On Wed, Nov 26, 2014 at 10:01 AM, Sanford, Claire 
mailto:claire.sanf...@memorialhermann.org>> 
wrote:
**
I have 8.1 installed on my new test/prod server and the email engine starts, 
but it does not authenticate.

I have checked the user name and password in the service and it still won’t 
authenticate.

I have looked in the “normal” areas.

Config.properties
Ar.cfg
Armonitor.cfg
emaildaemon.properties

And found nothing out of the ordinary.  I made sure everything matched what is 
in my current (working) emaildaemon.properties file matched in the non-working 
one.

This is the content of my mail logs:
STOUT.log

Checking connection to server: REMEDYAPP1.mh.org ...
ERROR (623): Authentication failed;

Cannot connect.
Checking connection to server: REMEDYAPP1.mh.org ...

Cannot connect.



STDERR.log
ERROR (623): Authentication failed;
at com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown 
Source)
at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source)
at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown Source)
at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source)
at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source)
at 
com.bmc.arsys.emaildaemon.EmailUtil.createARServerUser(EmailUtil.java:1299)
at 
com.bmc.arsys.emaildaemon.LoggingModule.setUserInfo(LoggingModule.java:767)
at 
com.bmc.arsys.emaildaemon.EmailDaemon.startLoggingModule(EmailDaemon.java:125)
at com.bmc.arsys.emaildaemon.EmailDaemon.(EmailDaemon.java:96)
at 
com.bmc.arsys.emaildaemon.EmailDaemon.newInstance(EmailDaemon.java:161)
at 
com.bmc.arsys.emaildaemon.EmailDaemon.startMonitor(EmailDaemon.java:903)
at 
com.bmc.arsys.emaildaemon.EmailDaemon.executeComandLine(EmailDaemon.java:609)
at com.bmc.arsys.emaildaemon.EmailDaemon.main(EmailDaemon.java:324)
ERROR (623): Authentication failed;
at com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown 
Source)
at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source)
at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown Source)
at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source)
at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source)
at com.bmc.arsys.api.ARServerUser.login(Unknown Source)
at 
com.bmc.arsys.emaildaemon.MonitorModule.checkServer(MonitorModule.java:307)
at com.bmc.arsys.emaildaemon.MonitorModule.doWork(MonitorModule.java:99)
at com.bmc.arsys.emaildaemon.ThreadBase.run(ThreadBase.java:302)
at com.bmc.arsys.emaildaemon.MonitorModule.run(MonitorModule.java:26)
at java.lang.Thread.run(Unknown Source)
ERROR (623): Authentication failed;
at com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown 
Source)
at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source)
at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown Source)
at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source)
at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source)
at 
com.bmc.arsys.emaildaemon.EmailUtil.createARServerUser(EmailUtil.java:1299)
at 
com.bmc.arsys.emaildaemon.EmailDaemon.setUserInfo(EmailDaemon.java:947)
at 
com.bmc.arsys.emaildaemon.EmailDaemon.executeComandLine(EmailDaemon.java:619)
at com.bmc.arsys.emaildaemon.EmailDaemon.main(EmailDaemon.java:324)
Nov 26, 2014 10:24:06 AM com.bmc.arsys.emaildaemon.LoggingModule doWork
SEVERE: Authentication failed

_ARSlist: "Where the Answers Are" and have been for 20 years_

_ARSlist: "Where the Answers Are" and have been for 20 years_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and hav

Re: Remedy 8.1 Email Engine - ERROR (623)

[LJ LongWing]

Claire,
The authentication failed message is simply that the password it's trying
is not correct (obviously), so, you could try re-setting the password in
the server config to what you think it should be, and if that doesn't work,
you can reset the password in the emaildaemon.properties file

https://docs.bmc.com/docs/display/public/ars81/EmailDaemon.properties+file

Follow the directions in that link, utilizing the -p parameter to reset the
password the daemon is trying to utilize.

On Wed, Nov 26, 2014 at 10:01 AM, Sanford, Claire <
claire.sanf...@memorialhermann.org> wrote:

> **
>  I have 8.1 installed on my new test/prod server and the email engine
> starts, but it does not authenticate.
>
> I have checked the user name and password in the service and it still
> won’t authenticate.
>
> I have looked in the “normal” areas.
>
> Config.properties
> Ar.cfg
> Armonitor.cfg
> emaildaemon.properties
>
> And found nothing out of the ordinary.  I made sure everything matched
> what is in my current (working) emaildaemon.properties file matched in the
> non-working one.
>
> This is the content of my mail logs:
> STOUT.log
>
> Checking connection to server: REMEDYAPP1.mh.org ...
> ERROR (623): Authentication failed;
>
> Cannot connect.
> Checking connection to server: REMEDYAPP1.mh.org ...
>
> Cannot connect.
>
>
>
> STDERR.log
> ERROR (623): Authentication failed;
> at
> com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown Source)
> at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source)
> at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown
> Source)
> at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source)
> at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source)
> at
> com.bmc.arsys.emaildaemon.EmailUtil.createARServerUser(EmailUtil.java:1299)
> at
> com.bmc.arsys.emaildaemon.LoggingModule.setUserInfo(LoggingModule.java:767)
> at
> com.bmc.arsys.emaildaemon.EmailDaemon.startLoggingModule(EmailDaemon.java:125)
> at
> com.bmc.arsys.emaildaemon.EmailDaemon.(EmailDaemon.java:96)
> at
> com.bmc.arsys.emaildaemon.EmailDaemon.newInstance(EmailDaemon.java:161)
> at
> com.bmc.arsys.emaildaemon.EmailDaemon.startMonitor(EmailDaemon.java:903)
> at
> com.bmc.arsys.emaildaemon.EmailDaemon.executeComandLine(EmailDaemon.java:609)
> at com.bmc.arsys.emaildaemon.EmailDaemon.main(EmailDaemon.java:324)
> ERROR (623): Authentication failed;
> at
> com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown Source)
> at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source)
> at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown
> Source)
> at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source)
> at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source)
> at com.bmc.arsys.api.ARServerUser.login(Unknown Source)
> at
> com.bmc.arsys.emaildaemon.MonitorModule.checkServer(MonitorModule.java:307)
> at
> com.bmc.arsys.emaildaemon.MonitorModule.doWork(MonitorModule.java:99)
> at com.bmc.arsys.emaildaemon.ThreadBase.run(ThreadBase.java:302)
> at
> com.bmc.arsys.emaildaemon.MonitorModule.run(MonitorModule.java:26)
> at java.lang.Thread.run(Unknown Source)
> ERROR (623): Authentication failed;
> at
> com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown Source)
> at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source)
> at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown
> Source)
> at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source)
> at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source)
> at
> com.bmc.arsys.emaildaemon.EmailUtil.createARServerUser(EmailUtil.java:1299)
> at
> com.bmc.arsys.emaildaemon.EmailDaemon.setUserInfo(EmailDaemon.java:947)
> at
> com.bmc.arsys.emaildaemon.EmailDaemon.executeComandLine(EmailDaemon.java:619)
> at com.bmc.arsys.emaildaemon.EmailDaemon.main(EmailDaemon.java:324)
> Nov 26, 2014 10:24:06 AM com.bmc.arsys.emaildaemon.LoggingModule doWork
> SEVERE: Authentication failed
>
>  _ARSlist: "Where the Answers Are" and have been for 20 years_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Remedy 8.1 Email Engine - ERROR (623)

[Sanford, Claire]

I have 8.1 installed on my new test/prod server and the email engine starts, 
but it does not authenticate.

I have checked the user name and password in the service and it still won't 
authenticate.

I have looked in the "normal" areas.

Config.properties
Ar.cfg
Armonitor.cfg
emaildaemon.properties

And found nothing out of the ordinary.  I made sure everything matched what is 
in my current (working) emaildaemon.properties file matched in the non-working 
one.

This is the content of my mail logs:
STOUT.log

Checking connection to server: REMEDYAPP1.mh.org ...
ERROR (623): Authentication failed;

Cannot connect.
Checking connection to server: REMEDYAPP1.mh.org ...

Cannot connect.



STDERR.log
ERROR (623): Authentication failed;
at com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown 
Source)
at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source)
at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown Source)
at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source)
at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source)
at 
com.bmc.arsys.emaildaemon.EmailUtil.createARServerUser(EmailUtil.java:1299)
at 
com.bmc.arsys.emaildaemon.LoggingModule.setUserInfo(LoggingModule.java:767)
at 
com.bmc.arsys.emaildaemon.EmailDaemon.startLoggingModule(EmailDaemon.java:125)
at com.bmc.arsys.emaildaemon.EmailDaemon.(EmailDaemon.java:96)
at 
com.bmc.arsys.emaildaemon.EmailDaemon.newInstance(EmailDaemon.java:161)
at 
com.bmc.arsys.emaildaemon.EmailDaemon.startMonitor(EmailDaemon.java:903)
at 
com.bmc.arsys.emaildaemon.EmailDaemon.executeComandLine(EmailDaemon.java:609)
at com.bmc.arsys.emaildaemon.EmailDaemon.main(EmailDaemon.java:324)
ERROR (623): Authentication failed;
at com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown 
Source)
at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source)
at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown Source)
at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source)
at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source)
at com.bmc.arsys.api.ARServerUser.login(Unknown Source)
at 
com.bmc.arsys.emaildaemon.MonitorModule.checkServer(MonitorModule.java:307)
at com.bmc.arsys.emaildaemon.MonitorModule.doWork(MonitorModule.java:99)
at com.bmc.arsys.emaildaemon.ThreadBase.run(ThreadBase.java:302)
at com.bmc.arsys.emaildaemon.MonitorModule.run(MonitorModule.java:26)
at java.lang.Thread.run(Unknown Source)
ERROR (623): Authentication failed;
at com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown 
Source)
at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source)
at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown Source)
at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source)
at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source)
at 
com.bmc.arsys.emaildaemon.EmailUtil.createARServerUser(EmailUtil.java:1299)
at 
com.bmc.arsys.emaildaemon.EmailDaemon.setUserInfo(EmailDaemon.java:947)
at 
com.bmc.arsys.emaildaemon.EmailDaemon.executeComandLine(EmailDaemon.java:619)
at com.bmc.arsys.emaildaemon.EmailDaemon.main(EmailDaemon.java:324)
Nov 26, 2014 10:24:06 AM com.bmc.arsys.emaildaemon.LoggingModule doWork
SEVERE: Authentication failed


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: BMC Account Class

[Santosh Kumar S]

Hi Victor,

Thanks for the response.Yes, AST:ClassAttributes was not having record
BMC_Account class.after creating the same records were getting created in
AST:Attributes form after the recon job.

Thnk you once again.

Regards,
Santosh Kumar S



--
View this message in context: 
http://ars-action-request-system.1.n7.nabble.com/BMC-Account-Class-tp119901p119956.html
Sent from the ARS (Action Request System) mailing list archive at Nabble.com.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Creating a jira issue on click of a button on remedy form

[John Sundberg]

Gotta love that REST api.

also YAY UNIX!!!

BTW - can be pretty dangerous to put all that on the command line.

You may want to write your data to a file. … Then post the data from the
file.

As — somebody could put in an RFE which would kick off your JIRA…
Hopefully they don’t do something like

Fix bug where people can do `echo “something bad here"`



-John


On Wed, Nov 26, 2014 at 7:21 AM, MalviyaSaurabh  wrote:

> Hi All,
>
> This solved/
>
> $PROCESS$ /opt/bcs/bin/curl -D- -k -u svc-remedy:password -X POST --data
> “$Data1$” -H “Content-Type: application/json”
> https://jiradev.company.com/rest/api/2/issue/
>
> where DATA1 = as follows:
> {"fields":
>   {"project":
>   { "id": "18168"  },
>"summary":"Post-Mortem for Remedy *S3 - Major * Outage",
>"description":"You have been identified as the post-mortem owner for
> Remedy Ticket * 1714111 *. Please update this JIRA within 48 hours
> with the following information:  1. Outage Summary - *scout collector
> heartbeat failure! scout collector may have stopped processing monitor
> executions*  2. Order of Events  3. Root Cause and Resolution
>  4. Improvements Implemented  5. Trends and Risks  6.
> Follow-Ups.  The NOC Debrief, within the Remedy ticket, is a resource
> you may use to populate some of this information. Additionally, you will be
> invited to participate in a post-mortem meeting. When you receive the
> meeting invite, feel free to forward to others who were involved or should
> also attend. You will be requested to speak in detail to the areas listed
> above.",
>   "reporter":
>   {"name": "repoterlogin"},
>   "assignee":
>   {"name": "assigneelogin"},
>   "issuetype":
>   { "id": "11000" }
>   }
> }
>
>
>
> --
> View this message in context:
> http://ars-action-request-system.1.n7.nabble.com/Creating-a-jira-issue-on-click-of-a-button-on-remedy-form-tp119290p119950.html
> Sent from the ARS (Action Request System) mailing list archive at
> Nabble.com.
>
>
> ___
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> "Where the Answers Are, and have been for 20 years"
>



-- 

*John Sundberg*
Kinetic Data, Inc.
"Your Business. Your Process."

651-556-0930 I john.sundb...@kineticdata.com
www.kineticdata.com I community.kineticdata.com

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Fwd: Any one had this error with Atrium SSO Midtier Install?

[Hristo Ninov]

Hello,

I have not installed the 9.0 version, but my experience with previous SSO 
installation was always:
- install SSO without setting the mid tier/remedy integration
- run the deployer (version 8) or use the automated option in version 8.1x to 
create the webagent for mid tier.

I think this is not the issu - I have the server.xml file in slightly different 
location than you - I have it in folder Tomcat\Conf.

Regards,
Hristo

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Verify migrated form

[Misi Mladoniczky]

Hi,

I like to compare the exported def files from source and target systems.

To do this I have created a set of tools of which RRR|DefDiff would be the
most important one: https://rrr.se/cgi/tools/main?tool=rrrDefDiff

Comparing two complete defs:
rrrDefDiff.exe source.def target.def -nodef

To compare a single form object:
rrrDefDiff.exe -t form -n "HPD:Help Desk" source.def target.def -nodef

The -nodef option is used to skip the default behavior of creating backup and
delta definition files.

There are also some other tools you may want to check out:
RRR|ExportDef - https://rrr.se/cgi/tools/main?tool=rrrExportDef
RRR|ImportDef - https://rrr.se/cgi/tools/main?tool=rrrImportDef
RRR|DeleteObject - https://rrr.se/cgi/tools/main?tool=rrrDeleteObject

They can be used to do a full export of a source and target system, compare
them, produce delta def files and backup files, and import/delete needed
objects in the target system.

In other words pretty much what Migrator is supposed to do ;-)

Best Regards - Misi, RRR AB, http://www.rrr.se (ARSList MVP 2011)

Ask the Remedy Licensing Experts (Best R.O.I. Award at WWRUG10/11/12/13):
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
Find these products, and many free tools and utilities, at http://rrr.se.

> Hi All,
>
> This is probably going to be a mundane question, but i want to know how can
> we verify whether a custom form has been migrated correctly or not.
> Forms are migrated either by Developer Studio or AR Migrator from Server A
> to Server B.
> I can think of few steps, please let me know if these are correct or not for
> regular/join forms.
> 1. Post-migration : AR Migrator tool will tell the differences if any,
> ideally this report should give no differences (barring timestamp and owner)
> 2. Open the form in user tool and search the empty form : as data is not yet
> migrated (here my understanding is if the form is not migrated correctly
> then we should get sql view related error)
> 3. Query the back-end for existence of T,B and H tables for schemaid
> 4. Query the back-end for existence of db (oracle) view and SH view
>
> Is there any thing else we would have to do in order to make sure whether
> these are migrated correctly.
> Please note - related workflows are not a concern here.
>
> Regards,
> Saurabh
>
>
>
> --
> View this message in context:
> http://ars-action-request-system.1.n7.nabble.com/Verify-migrated-form-tp119949.html
> Sent from the ARS (Action Request System) mailing list archive at Nabble.com.
>
> ___
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> "Where the Answers Are, and have been for 20 years"
>

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Verify migrated form

[Arner, Todd]

If you're using AR Migrator, you can also look at the completion results.  Any 
errors will be listed there.

Todd Arner

-Original Message-
From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of MalviyaSaurabh
Sent: Wednesday, November 26, 2014 7:19 AM
To: arslist@ARSLIST.ORG
Subject: Verify migrated form

Hi All,
 
This is probably going to be a mundane question, but i want to know how can we 
verify whether a custom form has been migrated correctly or not.
Forms are migrated either by Developer Studio or AR Migrator from Server A to 
Server B.
I can think of few steps, please let me know if these are correct or not for 
regular/join forms.
1. Post-migration : AR Migrator tool will tell the differences if any, ideally 
this report should give no differences (barring timestamp and owner) 2. Open 
the form in user tool and search the empty form : as data is not yet migrated 
(here my understanding is if the form is not migrated correctly then we should 
get sql view related error) 3. Query the back-end for existence of T,B and H 
tables for schemaid 4. Query the back-end for existence of db (oracle) view and 
SH view
 
Is there any thing else we would have to do in order to make sure whether these 
are migrated correctly.
Please note - related workflows are not a concern here.
 
Regards,
Saurabh



--
View this message in context: 
http://ars-action-request-system.1.n7.nabble.com/Verify-migrated-form-tp119949.html
Sent from the ARS (Action Request System) mailing list archive at Nabble.com.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers 
Are, and have been for 20 years"

--
The information contained in this communication may be confidential, is 
intended only for the use of the recipient(s) named above, and may be protected 
under state or federal law. If the reader of this message is not the intended 
recipient, you are hereby notified that any dissemination, distribution, or 
copying of this communication, or any of its contents, is strictly prohibited. 
If you have received this communication in error, please forward the 
communication to no...@glhec.org immediately and destroy or delete the original 
message and any copy of it from your computer system. If you have any questions 
concerning this message, please contact the sender.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: ITSM 7 Defs Running on ARS 7.6

[Scott Hallenger]

Well in my scenario, the client would pay for the new ARS 7.6 licesnse, but 
would maintain their existing ITSM 7.1. I am still not clear on if 7.1 ITSM 
would run on ARS 7.6. From a def stainpoint it seem completely possible. Just 
looking for someone to chime in here who has done this or similar. BTW does a 
new install still come wit the 3 demo licenses... ? That could be useful for 
testing.


On Tue, 11/25/14, LJ LongWing  wrote:

 Subject: Re: ITSM 7 Defs Running on ARS 7.6
 To: arslist@ARSLIST.ORG
 Date: Tuesday, November 25, 2014, 5:59 PM
 
 **
 I would say yes...they are entitled to it and
 received it during their support window
 On Tue, Nov 25, 2014 at
 3:54 PM, Jason Miller 
 wrote:
 **
 You and LJ are likely correct.  I have heard
 similar things.  It is just odd to me and seems against how
 a typical license agreement is written.  I am so use to
 "you can use this as long as you pay us" (for
 server software, not Office, etc.)  I just figured BMC
 wasn't enforcing it or going after the organization it
 knew about.
 So in the
 scenario above, what if the organization downloaded 7.6 or
 even 8.x before they dropped support.  They can upgrade
 since they downloaded it during their entitled period?
 
 Jason
 On Tue, Nov 25, 2014 at
 2:30 PM, Rick Westbrock 
 wrote:
 **
 
 
 
 
 
 
 
 
 I would check on ARS/ITSM
 compatibilities, I have heard of a customer who was on ARS
 7.1 and ITSM 7.0.03 and could not upgrade ARS to 7.5 because
 their current
  version of ITSM would not work with that version of ARS. I
 heard about this years after the fact so I don’t know if
 any testing was done or if they were just going on what BMC
 reported to them.
  
  
 As far as support my understanding
 (whether it’s correct or not is up for debate) is that you
 should be able to run forever without a support contract but
 you
  lose all abilities to initiate a case with BMC Support, no
 access to patches or any other software and so forth.  I
 haven’t read the fine print of a contract though so I
 could be wrong. I was at a customer once who ran without
 support for nearly a year without
  a support contract because they were planning to migrate
 from Remedy to a different platform. As I recall BMC
 didn’t have a problem with the system running without a
 support contract, they just wouldn’t sell additional
 licenses without renewal of the overall
  support contract. 
  
 If you were to buy software and a
 specific number of licenses wouldn’t you expect to be able
 to run that software with that user count in perpetuity
 regardless
  of whether you had a support contract? I think in Scott’s
 case the customer needs to upgrade ARS for compliance
 reasons so they are going to have to accept the costs
 associated with that (i.e. purchase a support contract) or
 migrate to another platform (IMHO).
  
  
 -Rick
  
 From: Action Request System discussion
 list(ARSList) [mailto:arslist@ARSLIST.ORG]
 On Behalf Of Jason Miller
 
 Sent: Tuesday, November 25, 2014 2:12 PM
 
 To: arslist@ARSLIST.ORG
 
 Subject: Re: ITSM 7 Defs Running on ARS
 7.6
  
 ** 
 
 Thanks for the info.  Viable,
 yes.  Potentially with some challenges.
 
  
 
 
 We are still on Help Desk 6 on 8.1
 ARS.  I stop short of calling it ITSM because all we are
 using is Help Desk and this was before Assignment Engine,
 EIE/AIE and various other newer processes external to AR
 that
  now make up the whole ITSM suite tick.
 
  
 
 
 At this point I call it ours
 because it is so customized and so far out of support that
 we'll never upgrade over it.  In fact we recently
 converted all of the Help Desk, CMDB and SLA objects to
 Custom (I plan on
  deleting the CMDB and SLA stuff, we don't use them and
 are already broken binary-wise).
 
 
  
 
 
 With that said we still pay for
 support (granted we were heading down the ITSM 8.x path
 until recently).  Servers get old and need to be replaced,
 that old version of ARS will will only go so far with newer
 OSes. 
  We will need new license keys for the new servers (without
 playing illegal games).  We do a ton of development and we
 want to continue to incorporate new (UI) features. 
 Starting at 7.5 the new and updated web UI controls have
 been highly valuable.  We too
  use Remedy every day and it is considered one of higher
 priority apps DR wise (much of the info we need to recover
 is stored in Remedy).
 
 
  
 
 
 My aim is not to call out your
 customer however we are dancing around some legalities... 
 How can an organization upgrade ARS without a support
 contract?  The reasons your customer is not able to access
 parts of
  the BMC site, including software, is because that
 entitlement ran out with support.  I have heard stories of
 long-running systems that have been off of support for years
 so I know they are out there but I don't think legally
 an organization can continue to
  run Remedy without support?.?.?  I haven't read the
 license agreement that c

Re: Creating a jira issue on click of a button on remedy form

[MalviyaSaurabh]

Hi All,

This solved/

$PROCESS$ /opt/bcs/bin/curl -D- -k -u svc-remedy:password -X POST --data
“$Data1$” -H “Content-Type: application/json”
https://jiradev.company.com/rest/api/2/issue/

where DATA1 = as follows:
{"fields":
  {"project":
  { "id": "18168"  },
   "summary":"Post-Mortem for Remedy *S3 - Major * Outage",
   "description":"You have been identified as the post-mortem owner for
Remedy Ticket * 1714111 *. Please update this JIRA within 48 hours
with the following information:  1. Outage Summary - *scout collector
heartbeat failure! scout collector may have stopped processing monitor
executions*  2. Order of Events  3. Root Cause and Resolution
 4. Improvements Implemented  5. Trends and Risks  6.
Follow-Ups.  The NOC Debrief, within the Remedy ticket, is a resource
you may use to populate some of this information. Additionally, you will be
invited to participate in a post-mortem meeting. When you receive the
meeting invite, feel free to forward to others who were involved or should
also attend. You will be requested to speak in detail to the areas listed
above.",
  "reporter":
  {"name": "repoterlogin"},
  "assignee":
  {"name": "assigneelogin"},
  "issuetype":
  { "id": "11000" }
  }
}



--
View this message in context: 
http://ars-action-request-system.1.n7.nabble.com/Creating-a-jira-issue-on-click-of-a-button-on-remedy-form-tp119290p119950.html
Sent from the ARS (Action Request System) mailing list archive at Nabble.com.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Verify migrated form

[MalviyaSaurabh]

Hi All,
 
This is probably going to be a mundane question, but i want to know how can
we verify whether a custom form has been migrated correctly or not.
Forms are migrated either by Developer Studio or AR Migrator from Server A
to Server B.
I can think of few steps, please let me know if these are correct or not for
regular/join forms.
1. Post-migration : AR Migrator tool will tell the differences if any,
ideally this report should give no differences (barring timestamp and owner)
2. Open the form in user tool and search the empty form : as data is not yet
migrated (here my understanding is if the form is not migrated correctly
then we should get sql view related error)
3. Query the back-end for existence of T,B and H tables for schemaid
4. Query the back-end for existence of db (oracle) view and SH view
 
Is there any thing else we would have to do in order to make sure whether
these are migrated correctly.
Please note - related workflows are not a concern here.
 
Regards,
Saurabh



--
View this message in context: 
http://ars-action-request-system.1.n7.nabble.com/Verify-migrated-form-tp119949.html
Sent from the ARS (Action Request System) mailing list archive at Nabble.com.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Fwd: Any one had this error with Atrium SSO Midtier Install?

[BradRemedy]

Sorry, further to my mail - when I check the atriumsso_install_log file I
have the following entry

  LOG EVENT {Description=[connector port=8029 scheme=null secure=null
keystoreFile=null sslProtocol=null],Detail=[]}
(Nov 26 2014 01:39:48.405 PM
+0200),WARNING,com.bmc.install.product.atriumsso.integration.ar.installer.validator.AtriumSsoIntegrationMtContainerTypeValidationTask,
  LOG EVENT
{Description=[com.bmc.install.product.atriumsso.integration.ar.installer.validator.AtriumSsoIntegrationMtContainerTypeValidationTask.description],Detail=[Container
server xml is not valid.]}


If I look at the location of the server.xml file it is there with the nomal
information inside and file permissions.

*


Hi

Has anyone had the following error when trying to do the Mid Tier
integration install with Atrium SSO 9 ?

The step before was to "Enter the path to BMC Remedy Mid Tier Web server
home" which I set to "C:\Program Files\Apache Software
Foundation\Tomcat7.0" however then I get

[image: Inline image 1]

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Any one had this error with Atrium SSO Midtier Install?

[BradRemedy]

Hi

Has anyone had the following error when trying to do the Mid Tier
integration install with Atrium SSO 9 ?

The step before was to "Enter the path to BMC Remedy Mid Tier Web server
home" which I set to "C:\Program Files\Apache Software
Foundation\Tomcat7.0" however then I get

[image: Inline image 1]

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"