Re: Trouble getting rrrchive to run

[Warren Dew]

Yes thats what we do , we transferred a whole Change Management from one
server to another consolidated Server  last year with two laptops ,
millions of records in the Change Management form and related Data , no
problem .

On 4 May 2018 at 18:31, Kevin M Candelaria  wrote:

> Why don't you just get rrrchive for windows and run it on your desktop and
> not the server.
>
>
>
>
> Sent from my Verizon, Samsung Galaxy smartphone. Excuse any spelling or
> formatting errors.
>
>
>  Original message 
> From: Ben Chernys 
> Date: 5/4/18 11:26 AM (GMT-05:00)
> To: 'ARSList' 
> Subject: RE: Trouble getting rrrchive to run
>
> Like Conny said,
>
>
>
> export  ARAPILOGGING=x where x is 1 or 29 or some other number – in the
> same bash shell where you set the LD_LIBRARY_PATH and where you will run
> rrrchive.
>
>
>
> Log file(s) show up in the current working directory.
>
>
>
> Do a
>
>
>
> set | grep -e LD_LIBRARY -e AR
>
>
>
> and email the results.
>
>
>
> You need to make sure there is no ARTCPPORT set.  This would override
> anything that the program is trying to set.
>
>
>
> Are you in MUC these days?
>
>
>
> Ben
>
>
>
> *From:* ARSList  *On Behalf Of *Thomas
> Miskiewicz
> *Sent:* May-04-18 9:03 AM
> *To:* ARSList 
> *Subject:* Re: Trouble getting rrrchive to run
>
>
>
> Hi Ben,
>
>
>
> I actually did set the LD_LIBRARY_PATH but it makes no difference.
>
>
>
> The only thing I don’t get is how to enable that API Logging on that Linux
> Server.
>
>
>
>
>
>
>
> Thomas
>
>
> On 4. May 2018, at 16:11, Ben Chernys 
> wrote:
>
> Thomas,
>
>
>
> It IS compatible.  I know this without using the tool.  The API is
> compatible across all releases with only a few minor problems related to
> AR_INFO selection values introduced in 9 - which are not affecting you.  It
> is not Misi’s tool.  I can run stuff linked with any version against any
> version of the server,
>
>
>
> Ensure your LD_LIBRARY_PATH is set to where you installed the tool – see
> Conny’s email on how to do this.  Given that you did not know how to set
> environment variable, I suspect that this may be your issue.  The binary
> needs to pick up the right .so and in Linux they are not named differently
> by version.
>
>
>
> export  LD_LIBRARY_PATH=/where-ever-I-installed-rrrchive-bin:$LD_
> LIBRARY_PATH
>
>
>
> Cheers
>
> Ben
>
>
>
> *From:* ARSList  *On Behalf Of *Thomas
> Miskiewicz
> *Sent:* May-04-18 7:42 AM
> *To:* ARSList 
> *Subject:* Re: Trouble getting rrrchive to run
>
>
>
> Hi Misi,
>
>
>
> the only last idea I have is: your version is 9.1.00 and ours is 9.1.04.
> Maybe it’s incompatible. Disappointing experience with this tool
>
>
>
>
>
> Thomas
>
>
>
>
> On May 3, 2018, at 8:37 AM, Misi Mladoniczky  wrote:
>
>
>
> Hi,
>
> You see exactly what the problem is in the log with normal logging turned
> on.
>
> You get ARERR 91 with the additional text "RPC: Unable to receive;
> Asynchronous event occurred".
>
> You should might want to work with BMC support on this.
>
> To debug you might use the driver program to do an RPC call both with the
> 7.6.04 API and the 9.1 API to check if this makes a difference in your case.
>
> You could also set ARAPILOGGING to 1 prior to running RRR|Chive to get the
> exact API-calls and data to feed to driver in order to reproduce this.
>
> If you have the correct server IP and tcp port it should work.
>
> 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
>
>
>
>
> May 2, 2018 3:44 PM, "Thomas Miskiewicz"  <%22thomas%20miskiewicz%22%20%3ctmisk...@gmail.com%3e>> wrote:
>
> Thank you, Misi!
>
> Is there an advanced logging that would help where the problem is?
>
> Thomas
>
>
> On 2. May 2018, at 15:36, Misi Mladoniczky  wrote:
>
> Hi,
>
> No, different server versions work just fine.
>
> 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
>
>
>
>
> May 2, 2018 2:55 PM, "Thomas Miskiewicz"  <%22thomas%20miskiewicz%22%20%3ctmisk...@gmail.com%3e>> wrote:
>
> The thing is we have 7.6.4 on one side and 9.1.4 on the other side.
> Problem?
>
> On May 2, 2018, at 2:48 PM, Kevin M Candelaria  wrote:
>
> It's 

Re: Trouble getting rrrchive to run

[Kevin M Candelaria]

Why don't you just get rrrchive for windows and run it on your desktop and not 
the server.




Sent from my Verizon, Samsung Galaxy smartphone. Excuse any spelling or 
formatting errors.


 Original message 
From: Ben Chernys 
Date: 5/4/18 11:26 AM (GMT-05:00)
To: 'ARSList' 
Subject: RE: Trouble getting rrrchive to run

Like Conny said,

export  ARAPILOGGING=x where x is 1 or 29 or some other number – in the same 
bash shell where you set the LD_LIBRARY_PATH and where you will run rrrchive.

Log file(s) show up in the current working directory.

Do a

set | grep -e LD_LIBRARY -e AR

and email the results.

You need to make sure there is no ARTCPPORT set.  This would override anything 
that the program is trying to set.

Are you in MUC these days?

Ben

From: ARSList  On Behalf Of Thomas Miskiewicz
Sent: May-04-18 9:03 AM
To: ARSList 
Subject: Re: Trouble getting rrrchive to run

Hi Ben,

I actually did set the LD_LIBRARY_PATH but it makes no difference.

The only thing I don’t get is how to enable that API Logging on that Linux 
Server.



Thomas

On 4. May 2018, at 16:11, Ben Chernys 
> 
wrote:
Thomas,

It IS compatible.  I know this without using the tool.  The API is compatible 
across all releases with only a few minor problems related to AR_INFO selection 
values introduced in 9 - which are not affecting you.  It is not Misi’s tool.  
I can run stuff linked with any version against any version of the server,

Ensure your LD_LIBRARY_PATH is set to where you installed the tool – see 
Conny’s email on how to do this.  Given that you did not know how to set 
environment variable, I suspect that this may be your issue.  The binary needs 
to pick up the right .so and in Linux they are not named differently by version.

export  LD_LIBRARY_PATH=/where-ever-I-installed-rrrchive-bin:$LD_LIBRARY_PATH

Cheers
Ben

From: ARSList > 
On Behalf Of Thomas Miskiewicz
Sent: May-04-18 7:42 AM
To: ARSList >
Subject: Re: Trouble getting rrrchive to run

Hi Misi,

the only last idea I have is: your version is 9.1.00 and ours is 9.1.04. Maybe 
it’s incompatible. Disappointing experience with this tool


Thomas



On May 3, 2018, at 8:37 AM, Misi Mladoniczky > 
wrote:

Hi,

You see exactly what the problem is in the log with normal logging turned on.

You get ARERR 91 with the additional text "RPC: Unable to receive; Asynchronous 
event occurred".

You should might want to work with BMC support on this.

To debug you might use the driver program to do an RPC call both with the 
7.6.04 API and the 9.1 API to check if this makes a difference in your case.

You could also set ARAPILOGGING to 1 prior to running RRR|Chive to get the 
exact API-calls and data to feed to driver in order to reproduce this.

If you have the correct server IP and tcp port it should work.

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




May 2, 2018 3:44 PM, "Thomas Miskiewicz" 
>
 wrote:
Thank you, Misi!
Is there an advanced logging that would help where the problem is?
Thomas

On 2. May 2018, at 15:36, Misi Mladoniczky > 
wrote:
Hi,

No, different server versions work just fine.

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




May 2, 2018 2:55 PM, "Thomas Miskiewicz" 
>
 wrote:
The thing is we have 7.6.4 on one side and 9.1.4 on the other side. Problem?
On May 2, 2018, at 2:48 PM, Kevin M Candelaria 
> wrote:
It's definitely compatible with 9.x
I just did a 9.1.00 to 9.1.04 transfer and my config looks like this. Worked 
perfectly fine.
source_server =
source_tcp = 2020
source_user =
source_password =
target_server =
target_tcp = 2020
target_user =
target_password =
target_disabledeletefltr = YES
target_disablemergefltr = YES
target_disableaudit = YES
target_clearallrecords = YES
multipleforms = 

RE: Trouble getting rrrchive to run

[Ben Chernys]

Like Conny said,

 

export  ARAPILOGGING=x where x is 1 or 29 or some other number – in the same 
bash shell where you set the LD_LIBRARY_PATH and where you will run rrrchive.

 

Log file(s) show up in the current working directory.

 

Do a 

 

set | grep -e LD_LIBRARY -e AR

 

and email the results.

 

You need to make sure there is no ARTCPPORT set.  This would override anything 
that the program is trying to set.

 

Are you in MUC these days?

 

Ben

 

From: ARSList  On Behalf Of Thomas Miskiewicz
Sent: May-04-18 9:03 AM
To: ARSList 
Subject: Re: Trouble getting rrrchive to run

 

Hi Ben,

 

I actually did set the LD_LIBRARY_PATH but it makes no difference.

 

The only thing I don’t get is how to enable that API Logging on that Linux 
Server.

 

 

 

Thomas


On 4. May 2018, at 16:11, Ben Chernys  > wrote:

Thomas,

 

It IS compatible.  I know this without using the tool.  The API is compatible 
across all releases with only a few minor problems related to AR_INFO selection 
values introduced in 9 - which are not affecting you.  It is not Misi’s tool.  
I can run stuff linked with any version against any version of the server,

 

Ensure your LD_LIBRARY_PATH is set to where you installed the tool – see 
Conny’s email on how to do this.  Given that you did not know how to set 
environment variable, I suspect that this may be your issue.  The binary needs 
to pick up the right .so and in Linux they are not named differently by 
version.  

 

export  LD_LIBRARY_PATH=/where-ever-I-installed-rrrchive-bin:$LD_LIBRARY_PATH

 

Cheers

Ben

 

From: ARSList  
> On Behalf Of Thomas Miskiewicz
Sent: May-04-18 7:42 AM
To: ARSList  >
Subject: Re: Trouble getting rrrchive to run

 

Hi Misi,

 

the only last idea I have is: your version is 9.1.00 and ours is 9.1.04. Maybe 
it’s incompatible. Disappointing experience with this tool

 

 

Thomas






On May 3, 2018, at 8:37 AM, Misi Mladoniczky  
> wrote:

 

Hi,

You see exactly what the problem is in the log with normal logging turned on.

You get ARERR 91 with the additional text "RPC: Unable to receive; Asynchronous 
event occurred".

You should might want to work with BMC support on this.

To debug you might use the driver program to do an RPC call both with the 
7.6.04 API and the 9.1 API to check if this makes a difference in your case.

You could also set ARAPILOGGING to 1 prior to running RRR|Chive to get the 
exact API-calls and data to feed to driver in order to reproduce this.

If you have the correct server IP and tcp port it should work.

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 
 




May 2, 2018 3:44 PM, "Thomas Miskiewicz"  > wrote:

Thank you, Misi!

Is there an advanced logging that would help where the problem is?

Thomas


On 2. May 2018, at 15:36, Misi Mladoniczky  > 
wrote:

Hi,

No, different server versions work just fine.

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 
 




May 2, 2018 2:55 PM, "Thomas Miskiewicz"  > wrote:

The thing is we have 7.6.4 on one side and 9.1.4 on the other side. Problem?

On May 2, 2018, at 2:48 PM, Kevin M Candelaria  > wrote:

It's definitely compatible with 9.x

I just did a 9.1.00 to 9.1.04 transfer and my config looks like this. Worked 
perfectly fine.

source_server = 
source_tcp = 2020
source_user = 
source_password = 
target_server = 
target_tcp = 2020
target_user = 
target_password = 
target_disabledeletefltr = YES 
target_disablemergefltr = YES
target_disableaudit = YES
target_clearallrecords = YES
multipleforms = HPD:Template, \
HPD:Template Associations, \
HPD:TemplateCustMapping, \
HPD:TemplateSPGAssoc, \
splitsearch = YES
transfertype = SYNCIFNEWER
logfile = AUTO
progressbar = YES


  _  


From: ARSList  
> on 

Re: AW: Trouble getting rrrchive to run

[Thomas Miskiewicz]

Thanks, Conny! Where would that Log show up then?

> On 4. May 2018, at 14:33,  
>  wrote:
> 
> export ARAPILOGGING=1
>  
> If client side api logging is working, you should see files created in your 
> current working directory. This works with every AR-Api Client using the 
> native api libs
>  
> KR Conny
>  
> Von: ARSList [mailto:arslist-boun...@arslist.org] Im Auftrag von Thomas 
> Miskiewicz
> Gesendet: Freitag, 4. Mai 2018 12:10
> An: ARSList 
> Betreff: Re: Trouble getting rrrchive to run
>  
> Misi, you said: You could also set ARAPILOGGING to 1 prior to running 
> RRR|Chive to get the exact API-calls and data to feed to driver in order to 
> reproduce this.
>  
> How do I do that on a Linux box?
>  
>  
> Thomas
> 
> 
> On May 3, 2018, at 8:37 AM, Misi Mladoniczky  wrote:
>  
> Hi,
> 
> You see exactly what the problem is in the log with normal logging turned on.
> 
> You get ARERR 91 with the additional text "RPC: Unable to receive; 
> Asynchronous event occurred".
> 
> You should might want to work with BMC support on this.
> 
> To debug you might use the driver program to do an RPC call both with the 
> 7.6.04 API and the 9.1 API to check if this makes a difference in your case.
> 
> You could also set ARAPILOGGING to 1 prior to running RRR|Chive to get the 
> exact API-calls and data to feed to driver in order to reproduce this.
> 
> If you have the correct server IP and tcp port it should work.
> 
> 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
> 
> 
> 
> 
> May 2, 2018 3:44 PM, "Thomas Miskiewicz"  wrote:
> Thank you, Misi!
> Is there an advanced logging that would help where the problem is?
> Thomas
> 
> On 2. May 2018, at 15:36, Misi Mladoniczky  wrote:
> Hi,
> 
> No, different server versions work just fine.
> 
> 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
> 
> 
> 
> 
> May 2, 2018 2:55 PM, "Thomas Miskiewicz"  wrote:
> The thing is we have 7.6.4 on one side and 9.1.4 on the other side. Problem?
> On May 2, 2018, at 2:48 PM, Kevin M Candelaria  wrote:
> It's definitely compatible with 9.x
> I just did a 9.1.00 to 9.1.04 transfer and my config looks like this. Worked 
> perfectly fine.
> source_server = 
> source_tcp = 2020
> source_user = 
> source_password = 
> target_server = 
> target_tcp = 2020
> target_user = 
> target_password = 
> target_disabledeletefltr = YES 
> target_disablemergefltr = YES
> target_disableaudit = YES
> target_clearallrecords = YES
> multipleforms = HPD:Template, \
> HPD:Template Associations, \
> HPD:TemplateCustMapping, \
> HPD:TemplateSPGAssoc, \
> splitsearch = YES
> transfertype = SYNCIFNEWER
> logfile = AUTO
> progressbar = YES
> From: ARSList  on behalf of Thomas Miskiewicz 
> 
> Sent: Wednesday, May 2, 2018 6:16 AM
> To: arslist@arslist.org
> Subject: Trouble getting rrrchive to run
> Hi Listers,
> I'm trying to use rrrchive tool (https://rrr.se/cgi/index?pg=chive-doc) to 
> migrate data from Remedy 7.6.4 to Remedy 9.1.
> Here's my config file:
> rrrchive.cfg
> source_server = sourceservername
> source_tcp = 1100
> source_user = myusername
> source_password = PROMPT
> source_form = MyTestForm
> target_server = targetservername
> target_tcp = 1400
> target_user = myusername
> target_password = PROMPT
> target_form = MyTestForm
> splitsearch = YES
> transfertype = SYNCTOTARGET
> logfile = AUTO
> loglevel = DEBUG
> progressbar = YES
> and here's my log:
> rrrchive.log
> 1 rrrchive: 2018-05-02 11:51:50, type=APP, level=NOTICE, file=rrrchive.cpp, 
> line=5076
> 2 Program Start: configfile=rrrchive.cfg
> 3 rrrchive: 2018-05-02 11:51:50, type=ARS, level=DEBUG, file=rrrchive.cpp, 
> line=365
> 4 ARSetServerPort(server=sourceservername, tcp=1100, rpc=0)
> 5 rrrchive: 2018-05-02 11:51:50, type=ARS, level=DEBUG, file=rrrchive.cpp, 
> line=365
> 6 ARSetServerPort(server=targetservername, tcp=1400, rpc=0)
> 7 rrrchive: 2018-05-02 11:52:06, type=ARS, level=ERROR, file=rrrchive.cpp, 
> line=389
> 8 ARGetServerInfo(server=targetservername, AR_SERVER_INFO_DELAY_RECACHE_TIME)
> 9 API CALL SEVERITY: AR_RETURN_ERROR, failure, status contains details
> 10 ARStatusList: contains 1 messages
> 11 Number: ARERR 91
> 12 Message: Cannot open 

Re: Trouble getting rrrchive to run

[Thomas Miskiewicz]

Hi Ben,

I actually did set the LD_LIBRARY_PATH but it makes no difference.

The only thing I don’t get is how to enable that API Logging on that Linux 
Server.



Thomas

> On 4. May 2018, at 16:11, Ben Chernys  
> wrote:
> 
> Thomas,
>  
> It IS compatible.  I know this without using the tool.  The API is compatible 
> across all releases with only a few minor problems related to AR_INFO 
> selection values introduced in 9 - which are not affecting you.  It is not 
> Misi’s tool.  I can run stuff linked with any version against any version of 
> the server,
>  
> Ensure your LD_LIBRARY_PATH is set to where you installed the tool – see 
> Conny’s email on how to do this.  Given that you did not know how to set 
> environment variable, I suspect that this may be your issue.  The binary 
> needs to pick up the right .so and in Linux they are not named differently by 
> version. 
>  
> export  LD_LIBRARY_PATH=/where-ever-I-installed-rrrchive-bin:$LD_LIBRARY_PATH
>  
> Cheers
> Ben
>  
> From: ARSList  On Behalf Of Thomas Miskiewicz
> Sent: May-04-18 7:42 AM
> To: ARSList 
> Subject: Re: Trouble getting rrrchive to run
>  
> Hi Misi,
>  
> the only last idea I have is: your version is 9.1.00 and ours is 9.1.04. 
> Maybe it’s incompatible. Disappointing experience with this tool
>  
>  
> Thomas
> 
> 
> On May 3, 2018, at 8:37 AM, Misi Mladoniczky  wrote:
>  
> Hi,
> 
> You see exactly what the problem is in the log with normal logging turned on.
> 
> You get ARERR 91 with the additional text "RPC: Unable to receive; 
> Asynchronous event occurred".
> 
> You should might want to work with BMC support on this.
> 
> To debug you might use the driver program to do an RPC call both with the 
> 7.6.04 API and the 9.1 API to check if this makes a difference in your case.
> 
> You could also set ARAPILOGGING to 1 prior to running RRR|Chive to get the 
> exact API-calls and data to feed to driver in order to reproduce this.
> 
> If you have the correct server IP and tcp port it should work.
> 
> 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
> 
> 
> 
> 
> May 2, 2018 3:44 PM, "Thomas Miskiewicz"  wrote:
> Thank you, Misi!
> Is there an advanced logging that would help where the problem is?
> Thomas
> 
> On 2. May 2018, at 15:36, Misi Mladoniczky  wrote:
> Hi,
> 
> No, different server versions work just fine.
> 
> 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
> 
> 
> 
> 
> May 2, 2018 2:55 PM, "Thomas Miskiewicz"  wrote:
> The thing is we have 7.6.4 on one side and 9.1.4 on the other side. Problem?
> On May 2, 2018, at 2:48 PM, Kevin M Candelaria  wrote:
> It's definitely compatible with 9.x
> I just did a 9.1.00 to 9.1.04 transfer and my config looks like this. Worked 
> perfectly fine.
> source_server = 
> source_tcp = 2020
> source_user = 
> source_password = 
> target_server = 
> target_tcp = 2020
> target_user = 
> target_password = 
> target_disabledeletefltr = YES 
> target_disablemergefltr = YES
> target_disableaudit = YES
> target_clearallrecords = YES
> multipleforms = HPD:Template, \
> HPD:Template Associations, \
> HPD:TemplateCustMapping, \
> HPD:TemplateSPGAssoc, \
> splitsearch = YES
> transfertype = SYNCIFNEWER
> logfile = AUTO
> progressbar = YES
> From: ARSList  on behalf of Thomas Miskiewicz 
> 
> Sent: Wednesday, May 2, 2018 6:16 AM
> To: arslist@arslist.org
> Subject: Trouble getting rrrchive to run
> Hi Listers,
> I'm trying to use rrrchive tool (https://rrr.se/cgi/index?pg=chive-doc) to 
> migrate data from Remedy 7.6.4 to Remedy 9.1.
> Here's my config file:
> rrrchive.cfg
> source_server = sourceservername
> source_tcp = 1100
> source_user = myusername
> source_password = PROMPT
> source_form = MyTestForm
> target_server = targetservername
> target_tcp = 1400
> target_user = myusername
> target_password = PROMPT
> target_form = MyTestForm
> splitsearch = YES
> transfertype = SYNCTOTARGET
> logfile = AUTO
> loglevel = DEBUG
> progressbar = YES
> and here's my log:
> rrrchive.log
> 1 rrrchive: 2018-05-02 11:51:50, type=APP, level=NOTICE, file=rrrchive.cpp, 
> line=5076
> 2 Program Start: configfile=rrrchive.cfg
> 3 rrrchive: 2018-05-02 11:51:50, 

RE: Trouble getting rrrchive to run

[Ben Chernys]

Thomas,

 

It IS compatible.  I know this without using the tool.  The API is compatible 
across all releases with only a few minor problems related to AR_INFO selection 
values introduced in 9 - which are not affecting you.  It is not Misi’s tool.  
I can run stuff linked with any version against any version of the server,

 

Ensure your LD_LIBRARY_PATH is set to where you installed the tool – see 
Conny’s email on how to do this.  Given that you did not know how to set 
environment variable, I suspect that this may be your issue.  The binary needs 
to pick up the right .so and in Linux they are not named differently by 
version.  

 

export  LD_LIBRARY_PATH=/where-ever-I-installed-rrrchive-bin:$LD_LIBRARY_PATH

 

Cheers

Ben

 

From: ARSList  On Behalf Of Thomas Miskiewicz
Sent: May-04-18 7:42 AM
To: ARSList 
Subject: Re: Trouble getting rrrchive to run

 

Hi Misi,

 

the only last idea I have is: your version is 9.1.00 and ours is 9.1.04. Maybe 
it’s incompatible. Disappointing experience with this tool

 

 

Thomas





On May 3, 2018, at 8:37 AM, Misi Mladoniczky  
> wrote:

 

Hi,

You see exactly what the problem is in the log with normal logging turned on.

You get ARERR 91 with the additional text "RPC: Unable to receive; Asynchronous 
event occurred".

You should might want to work with BMC support on this.

To debug you might use the driver program to do an RPC call both with the 
7.6.04 API and the 9.1 API to check if this makes a difference in your case.

You could also set ARAPILOGGING to 1 prior to running RRR|Chive to get the 
exact API-calls and data to feed to driver in order to reproduce this.

If you have the correct server IP and tcp port it should work.

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 
 




May 2, 2018 3:44 PM, "Thomas Miskiewicz"  > wrote:

Thank you, Misi!

Is there an advanced logging that would help where the problem is?

Thomas


On 2. May 2018, at 15:36, Misi Mladoniczky  > 
wrote:

Hi,

No, different server versions work just fine.

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 
 




May 2, 2018 2:55 PM, "Thomas Miskiewicz"  > wrote:

The thing is we have 7.6.4 on one side and 9.1.4 on the other side. Problem?

On May 2, 2018, at 2:48 PM, Kevin M Candelaria  > wrote:

It's definitely compatible with 9.x

I just did a 9.1.00 to 9.1.04 transfer and my config looks like this. Worked 
perfectly fine.

source_server = 
source_tcp = 2020
source_user = 
source_password = 
target_server = 
target_tcp = 2020
target_user = 
target_password = 
target_disabledeletefltr = YES 
target_disablemergefltr = YES
target_disableaudit = YES
target_clearallrecords = YES
multipleforms = HPD:Template, \
HPD:Template Associations, \
HPD:TemplateCustMapping, \
HPD:TemplateSPGAssoc, \
splitsearch = YES
transfertype = SYNCIFNEWER
logfile = AUTO
progressbar = YES


  _  


From: ARSList  
> on behalf of Thomas Miskiewicz  >
Sent: Wednesday, May 2, 2018 6:16 AM
To: arslist@arslist.org  
Subject: Trouble getting rrrchive to run

Hi Listers,

I'm trying to use rrrchive tool (https://rrr.se/cgi/index?pg=chive-doc) to 
migrate data from Remedy 7.6.4 to Remedy 9.1.

Here's my config file:

rrrchive.cfg

source_server = sourceservername

source_tcp = 1100

source_user = myusername

source_password = PROMPT

source_form = MyTestForm

target_server = targetservername

target_tcp = 1400

target_user = myusername

target_password = PROMPT

target_form = MyTestForm

splitsearch = YES

transfertype = SYNCTOTARGET

logfile = AUTO

loglevel = DEBUG

progressbar = YES

and here's my log:

rrrchive.log

1 rrrchive: 2018-05-02 11:51:50, type=APP, level=NOTICE, file=rrrchive.cpp, 
line=5076

2 Program Start: configfile=rrrchive.cfg

3 rrrchive: 2018-05-02 11:51:50, type=ARS, level=DEBUG, file=rrrchive.cpp, 
line=365

4 

RE: Trouble getting rrrchive to run

[Ben Chernys]

Hallo Thomas, Conny, Misi,

 

I always use the value 29.  From the doc:  (These are bits that must be
or'd)

 


0

No logging - Setting ARAPILOGGING to 0 or not setting it at all turns
ARAPILOGGING off.


1

Logging on - ARAPILOGGING is on and minimum output is recorded in the
arapicmd.log and arapires.log files. If other options are included, this
option does not have to be included in the bit mask.


2

Record sleep time in seconds - The sleep time in seconds is recorded in the
command file.


4

Record sleep time in milliseconds - The sleep time in milliseconds is
recorded in the command file. If both the options (seconds and milliseconds,
value = 6) are selected, the sleep time output will be in seconds.


8

Record start, finish, and elapsed time - The start, finish, and elapsed
times are recorded in the result file. The elapsed time includes the time
needed for the API to write information to the log file.


16

Combine the command and result files into the result file - In this case,
client commands and server replies are all recorded in the arapires.log, and
the arapicmd.log is not created. This output is easiest to use because the
client commands and server responses are collated. Do not use this option if
you are building a command file to be played back in driver.


32

Do not record result data output - This option suppresses the output of the
result data, limiting the result output to status information only. This
option is useful when the quantity of result data is very large and the
output can impact performance. This option is also useful to reduce the
amount of logging information when the details of the returned data are not
important.


64

Buffer the file output - Utilizes file system buffering to write log output.
It can be used to reduce the time required to output the logging
information. However, you might lose information if the client you are
collecting logging information for crashes before all information has been
written to the log.



29



 

 

Thomas,  when you say you ran driver, did you actually do something like
retrieve data or issue a query?  Logging in doesn't actually do much.  

 


Cheers,

Ben Chernys
Senior Software Architect
  

Canada / Deutschland
Mobile:+49 171 380 2329   GMT - 7 + [ DST ]

Mobile +1 403  554 0887
Email:   Ben.Chernys_AT_softwaretoolhouse.com
 
Web:   www.softwaretoolhouse.com

We are a BMC Technology Alliance Partner

 

 

Check out Software Tool House's free Diary Editor and our  Freebies Section
for ITSM Forms and Fields spreadsheet.

Meta-Update  ,
our premium ARS Data tool, lets you automate your imports, migrations, in no
time at all, without programming, without staging forms, without merge
workflow. 

 

Meta-Archive 
does ITSM Archiving your way: with your forms and your multi-tenant rules,
treating each root request as a complete tree and checking associatuions.
Archive output to different servers, HTML pages with links to attachments or
archive forms.

 

Meta-Databot 
is an automated, extensible BMC Data Wizard.  It reads a file of data
changes and sports an Undo feature.

 

Pre ITSM 9.1.04?  Clarify?  HP? Roll your own?  No problem!  You can keep
your valuable data!


  http://www.softwaretoolhouse.com/  

 

 

 

Ben

 

From: ARSList  On Behalf Of
conny.mar...@t-systems.com
Sent: May-04-18 6:33 AM
To: arslist@arslist.org
Subject: AW: Trouble getting rrrchive to run

 

export ARAPILOGGING=1

 

If client side api logging is working, you should see files created in your
current working directory. This works with every AR-Api Client using the
native api libs

 

KR Conny

 

Von: ARSList [mailto:arslist-boun...@arslist.org] Im Auftrag von Thomas
Miskiewicz
Gesendet: Freitag, 4. Mai 2018 12:10
An: ARSList  >
Betreff: Re: Trouble getting rrrchive to run

 

Misi, you said: You could also set ARAPILOGGING to 1 prior to running
RRR|Chive to get the exact API-calls and data to feed to driver in order to
reproduce this.

 

How do I do that on a Linux box?

 

 

Thomas

 

On May 3, 2018, at 8:37 AM, Misi Mladoniczky 
> wrote:

 

Hi,

You see exactly what the problem is in the log with normal logging turned
on.

You get ARERR 91 with the additional text "RPC: Unable to receive;
Asynchronous event occurred".

You should might want to work with BMC support on this.

To debug you might use the driver program to do an RPC call both with the
7.6.04 API and the 9.1 API to check if this makes a difference in your case.

You could also set ARAPILOGGING to 1 prior to running RRR|Chive to get 

Re: Trouble getting rrrchive to run

[Thomas Miskiewicz]

Hi Misi,

the only last idea I have is: your version is 9.1.00 and ours is 9.1.04. Maybe 
it’s incompatible. Disappointing experience with this tool


Thomas

> On May 3, 2018, at 8:37 AM, Misi Mladoniczky  wrote:
> 
> Hi,
> 
> You see exactly what the problem is in the log with normal logging turned on.
> 
> You get ARERR 91 with the additional text "RPC: Unable to receive; 
> Asynchronous event occurred".
> 
> You should might want to work with BMC support on this.
> 
> To debug you might use the driver program to do an RPC call both with the 
> 7.6.04 API and the 9.1 API to check if this makes a difference in your case.
> 
> You could also set ARAPILOGGING to 1 prior to running RRR|Chive to get the 
> exact API-calls and data to feed to driver in order to reproduce this.
> 
> If you have the correct server IP and tcp port it should work.
> 
> 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 
> 
> 
> 
> 
> 
> May 2, 2018 3:44 PM, "Thomas Miskiewicz"  >> wrote:
> Thank you, Misi!
> Is there an advanced logging that would help where the problem is?
> Thomas
> 
> On 2. May 2018, at 15:36, Misi Mladoniczky > 
> wrote:
>> Hi,
>> 
>> No, different server versions work just fine.
>> 
>> 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 
>> 
>> 
>> 
>> 
>> 
>> May 2, 2018 2:55 PM, "Thomas Miskiewicz" > >> wrote:
>> The thing is we have 7.6.4 on one side and 9.1.4 on the other side. Problem?
>>> On May 2, 2018, at 2:48 PM, Kevin M Candelaria >> > wrote:
>>> It's definitely compatible with 9.x
>>> I just did a 9.1.00 to 9.1.04 transfer and my config looks like this. 
>>> Worked perfectly fine.
>>> source_server = 
>>> source_tcp = 2020
>>> source_user = 
>>> source_password = 
>>> target_server = 
>>> target_tcp = 2020
>>> target_user = 
>>> target_password = 
>>> target_disabledeletefltr = YES 
>>> target_disablemergefltr = YES
>>> target_disableaudit = YES
>>> target_clearallrecords = YES
>>> multipleforms = HPD:Template, \
>>> HPD:Template Associations, \
>>> HPD:TemplateCustMapping, \
>>> HPD:TemplateSPGAssoc, \
>>> splitsearch = YES
>>> transfertype = SYNCIFNEWER
>>> logfile = AUTO
>>> progressbar = YES
>>> From: ARSList >> > on behalf of Thomas Miskiewicz 
>>> >
>>> Sent: Wednesday, May 2, 2018 6:16 AM
>>> To: arslist@arslist.org 
>>> Subject: Trouble getting rrrchive to run
>>> Hi Listers,
>>> I'm trying to use rrrchive tool (https://rrr.se/cgi/index?pg=chive-doc 
>>> ) to migrate data from Remedy 7.6.4 
>>> to Remedy 9.1.
>>> Here's my config file:
>>> rrrchive.cfg
>>> source_server = sourceservername
>>> source_tcp = 1100
>>> source_user = myusername
>>> source_password = PROMPT
>>> source_form = MyTestForm
>>> target_server = targetservername
>>> target_tcp = 1400
>>> target_user = myusername
>>> target_password = PROMPT
>>> target_form = MyTestForm
>>> splitsearch = YES
>>> transfertype = SYNCTOTARGET
>>> logfile = AUTO
>>> loglevel = DEBUG
>>> progressbar = YES
>>> and here's my log:
>>> rrrchive.log
>>> 1 rrrchive: 2018-05-02 11:51:50, type=APP, level=NOTICE, file=rrrchive.cpp, 
>>> line=5076
>>> 2 Program Start: configfile=rrrchive.cfg
>>> 3 rrrchive: 2018-05-02 11:51:50, type=ARS, level=DEBUG, file=rrrchive.cpp, 
>>> line=365
>>> 4 ARSetServerPort(server=sourceservername, tcp=1100, rpc=0)
>>> 5 rrrchive: 2018-05-02 11:51:50, type=ARS, level=DEBUG, file=rrrchive.cpp, 
>>> line=365
>>> 6 ARSetServerPort(server=targetservername, tcp=1400, rpc=0)
>>> 7 rrrchive: 2018-05-02 11:52:06, type=ARS, level=ERROR, file=rrrchive.cpp, 
>>> line=389
>>> 8 ARGetServerInfo(server=targetservername, 
>>> AR_SERVER_INFO_DELAY_RECACHE_TIME)
>>> 9 API CALL SEVERITY: AR_RETURN_ERROR, failure, status contains details
>>> 10 ARStatusList: contains 1 messages
>>> 11 Number: ARERR 91
>>> 12 Message: Cannot open catalog; Message number = 91
>>> 13 Append: RPC: Unable to receive; Asynchronous event 

Re: Trouble getting rrrchive to run

[Thomas Miskiewicz]

Hi Misi,

we also maxed out ulimit but get the very same error.


Thomas

> On May 3, 2018, at 8:37 AM, Misi Mladoniczky  wrote:
> 
> Hi,
> 
> You see exactly what the problem is in the log with normal logging turned on.
> 
> You get ARERR 91 with the additional text "RPC: Unable to receive; 
> Asynchronous event occurred".
> 
> You should might want to work with BMC support on this.
> 
> To debug you might use the driver program to do an RPC call both with the 
> 7.6.04 API and the 9.1 API to check if this makes a difference in your case.
> 
> You could also set ARAPILOGGING to 1 prior to running RRR|Chive to get the 
> exact API-calls and data to feed to driver in order to reproduce this.
> 
> If you have the correct server IP and tcp port it should work.
> 
> 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 
> 
> 
> 
> 
> 
> May 2, 2018 3:44 PM, "Thomas Miskiewicz"  >> wrote:
> Thank you, Misi!
> Is there an advanced logging that would help where the problem is?
> Thomas
> 
> On 2. May 2018, at 15:36, Misi Mladoniczky > 
> wrote:
>> Hi,
>> 
>> No, different server versions work just fine.
>> 
>> 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 
>> 
>> 
>> 
>> 
>> 
>> May 2, 2018 2:55 PM, "Thomas Miskiewicz" > >> wrote:
>> The thing is we have 7.6.4 on one side and 9.1.4 on the other side. Problem?
>>> On May 2, 2018, at 2:48 PM, Kevin M Candelaria >> > wrote:
>>> It's definitely compatible with 9.x
>>> I just did a 9.1.00 to 9.1.04 transfer and my config looks like this. 
>>> Worked perfectly fine.
>>> source_server = 
>>> source_tcp = 2020
>>> source_user = 
>>> source_password = 
>>> target_server = 
>>> target_tcp = 2020
>>> target_user = 
>>> target_password = 
>>> target_disabledeletefltr = YES 
>>> target_disablemergefltr = YES
>>> target_disableaudit = YES
>>> target_clearallrecords = YES
>>> multipleforms = HPD:Template, \
>>> HPD:Template Associations, \
>>> HPD:TemplateCustMapping, \
>>> HPD:TemplateSPGAssoc, \
>>> splitsearch = YES
>>> transfertype = SYNCIFNEWER
>>> logfile = AUTO
>>> progressbar = YES
>>> From: ARSList >> > on behalf of Thomas Miskiewicz 
>>> >
>>> Sent: Wednesday, May 2, 2018 6:16 AM
>>> To: arslist@arslist.org 
>>> Subject: Trouble getting rrrchive to run
>>> Hi Listers,
>>> I'm trying to use rrrchive tool (https://rrr.se/cgi/index?pg=chive-doc 
>>> ) to migrate data from Remedy 7.6.4 
>>> to Remedy 9.1.
>>> Here's my config file:
>>> rrrchive.cfg
>>> source_server = sourceservername
>>> source_tcp = 1100
>>> source_user = myusername
>>> source_password = PROMPT
>>> source_form = MyTestForm
>>> target_server = targetservername
>>> target_tcp = 1400
>>> target_user = myusername
>>> target_password = PROMPT
>>> target_form = MyTestForm
>>> splitsearch = YES
>>> transfertype = SYNCTOTARGET
>>> logfile = AUTO
>>> loglevel = DEBUG
>>> progressbar = YES
>>> and here's my log:
>>> rrrchive.log
>>> 1 rrrchive: 2018-05-02 11:51:50, type=APP, level=NOTICE, file=rrrchive.cpp, 
>>> line=5076
>>> 2 Program Start: configfile=rrrchive.cfg
>>> 3 rrrchive: 2018-05-02 11:51:50, type=ARS, level=DEBUG, file=rrrchive.cpp, 
>>> line=365
>>> 4 ARSetServerPort(server=sourceservername, tcp=1100, rpc=0)
>>> 5 rrrchive: 2018-05-02 11:51:50, type=ARS, level=DEBUG, file=rrrchive.cpp, 
>>> line=365
>>> 6 ARSetServerPort(server=targetservername, tcp=1400, rpc=0)
>>> 7 rrrchive: 2018-05-02 11:52:06, type=ARS, level=ERROR, file=rrrchive.cpp, 
>>> line=389
>>> 8 ARGetServerInfo(server=targetservername, 
>>> AR_SERVER_INFO_DELAY_RECACHE_TIME)
>>> 9 API CALL SEVERITY: AR_RETURN_ERROR, failure, status contains details
>>> 10 ARStatusList: contains 1 messages
>>> 11 Number: ARERR 91
>>> 12 Message: Cannot open catalog; Message number = 91
>>> 13 Append: RPC: Unable to receive; Asynchronous event occurred
>>> 14
>>> 15 rrrchive: 2018-05-02 11:52:06, type=APP, level=NOTICE, 
>>> 

AW: Trouble getting rrrchive to run

[Conny.Martin]

export ARAPILOGGING=1

If client side api logging is working, you should see files created in your 
current working directory. This works with every AR-Api Client using the native 
api libs

KR Conny

Von: ARSList [mailto:arslist-boun...@arslist.org] Im Auftrag von Thomas 
Miskiewicz
Gesendet: Freitag, 4. Mai 2018 12:10
An: ARSList 
Betreff: Re: Trouble getting rrrchive to run

Misi, you said: You could also set ARAPILOGGING to 1 prior to running RRR|Chive 
to get the exact API-calls and data to feed to driver in order to reproduce 
this.

How do I do that on a Linux box?


Thomas


On May 3, 2018, at 8:37 AM, Misi Mladoniczky > 
wrote:

Hi,

You see exactly what the problem is in the log with normal logging turned on.

You get ARERR 91 with the additional text "RPC: Unable to receive; Asynchronous 
event occurred".

You should might want to work with BMC support on this.

To debug you might use the driver program to do an RPC call both with the 
7.6.04 API and the 9.1 API to check if this makes a difference in your case.

You could also set ARAPILOGGING to 1 prior to running RRR|Chive to get the 
exact API-calls and data to feed to driver in order to reproduce this.

If you have the correct server IP and tcp port it should work.

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




May 2, 2018 3:44 PM, "Thomas Miskiewicz" 
>
 wrote:
Thank you, Misi!
Is there an advanced logging that would help where the problem is?
Thomas

On 2. May 2018, at 15:36, Misi Mladoniczky > 
wrote:
Hi,

No, different server versions work just fine.

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




May 2, 2018 2:55 PM, "Thomas Miskiewicz" 
>
 wrote:
The thing is we have 7.6.4 on one side and 9.1.4 on the other side. Problem?
On May 2, 2018, at 2:48 PM, Kevin M Candelaria 
> wrote:
It's definitely compatible with 9.x
I just did a 9.1.00 to 9.1.04 transfer and my config looks like this. Worked 
perfectly fine.
source_server =
source_tcp = 2020
source_user =
source_password =
target_server =
target_tcp = 2020
target_user =
target_password =
target_disabledeletefltr = YES
target_disablemergefltr = YES
target_disableaudit = YES
target_clearallrecords = YES
multipleforms = HPD:Template, \
HPD:Template Associations, \
HPD:TemplateCustMapping, \
HPD:TemplateSPGAssoc, \
splitsearch = YES
transfertype = SYNCIFNEWER
logfile = AUTO
progressbar = YES

From: ARSList > 
on behalf of Thomas Miskiewicz >
Sent: Wednesday, May 2, 2018 6:16 AM
To: arslist@arslist.org
Subject: Trouble getting rrrchive to run
Hi Listers,
I'm trying to use rrrchive tool (https://rrr.se/cgi/index?pg=chive-doc) to 
migrate data from Remedy 7.6.4 to Remedy 9.1.
Here's my config file:
rrrchive.cfg
source_server = sourceservername
source_tcp = 1100
source_user = myusername
source_password = PROMPT
source_form = MyTestForm
target_server = targetservername
target_tcp = 1400
target_user = myusername
target_password = PROMPT
target_form = MyTestForm
splitsearch = YES
transfertype = SYNCTOTARGET
logfile = AUTO
loglevel = DEBUG
progressbar = YES
and here's my log:
rrrchive.log
1 rrrchive: 2018-05-02 11:51:50, type=APP, level=NOTICE, file=rrrchive.cpp, 
line=5076
2 Program Start: configfile=rrrchive.cfg
3 rrrchive: 2018-05-02 11:51:50, type=ARS, level=DEBUG, file=rrrchive.cpp, 
line=365
4 ARSetServerPort(server=sourceservername, tcp=1100, rpc=0)
5 rrrchive: 2018-05-02 11:51:50, type=ARS, level=DEBUG, file=rrrchive.cpp, 
line=365
6 ARSetServerPort(server=targetservername, tcp=1400, rpc=0)
7 rrrchive: 2018-05-02 11:52:06, type=ARS, level=ERROR, file=rrrchive.cpp, 
line=389
8 ARGetServerInfo(server=targetservername, AR_SERVER_INFO_DELAY_RECACHE_TIME)
9 API CALL SEVERITY: AR_RETURN_ERROR, failure, status contains details
10 ARStatusList: contains 1 messages
11 Number: ARERR 91
12 Message: Cannot open catalog; Message number = 91
13 Append: RPC: Unable to 

Re: Trouble getting rrrchive to run

[Thomas Miskiewicz]

Hi Misi,

driver utility works just fine, i.e. I can connect from source to target 
without any delay.

API logs show on both source and target show no errors with rrrchive.

Connecting with alias, hostname or ip address makes no difference.  rrrchive 
throws ARERR 91 and would explain why.


Thomas

> On May 3, 2018, at 8:37 AM, Misi Mladoniczky  wrote:
> 
> Hi,
> 
> You see exactly what the problem is in the log with normal logging turned on.
> 
> You get ARERR 91 with the additional text "RPC: Unable to receive; 
> Asynchronous event occurred".
> 
> You should might want to work with BMC support on this.
> 
> To debug you might use the driver program to do an RPC call both with the 
> 7.6.04 API and the 9.1 API to check if this makes a difference in your case.
> 
> You could also set ARAPILOGGING to 1 prior to running RRR|Chive to get the 
> exact API-calls and data to feed to driver in order to reproduce this.
> 
> If you have the correct server IP and tcp port it should work.
> 
> 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 
> 
> 
> 
> 
> 
> May 2, 2018 3:44 PM, "Thomas Miskiewicz"  >> wrote:
> Thank you, Misi!
> Is there an advanced logging that would help where the problem is?
> Thomas
> 
> On 2. May 2018, at 15:36, Misi Mladoniczky > 
> wrote:
>> Hi,
>> 
>> No, different server versions work just fine.
>> 
>> 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 
>> 
>> 
>> 
>> 
>> 
>> May 2, 2018 2:55 PM, "Thomas Miskiewicz" > >> wrote:
>> The thing is we have 7.6.4 on one side and 9.1.4 on the other side. Problem?
>>> On May 2, 2018, at 2:48 PM, Kevin M Candelaria >> > wrote:
>>> It's definitely compatible with 9.x
>>> I just did a 9.1.00 to 9.1.04 transfer and my config looks like this. 
>>> Worked perfectly fine.
>>> source_server = 
>>> source_tcp = 2020
>>> source_user = 
>>> source_password = 
>>> target_server = 
>>> target_tcp = 2020
>>> target_user = 
>>> target_password = 
>>> target_disabledeletefltr = YES 
>>> target_disablemergefltr = YES
>>> target_disableaudit = YES
>>> target_clearallrecords = YES
>>> multipleforms = HPD:Template, \
>>> HPD:Template Associations, \
>>> HPD:TemplateCustMapping, \
>>> HPD:TemplateSPGAssoc, \
>>> splitsearch = YES
>>> transfertype = SYNCIFNEWER
>>> logfile = AUTO
>>> progressbar = YES
>>> From: ARSList >> > on behalf of Thomas Miskiewicz 
>>> >
>>> Sent: Wednesday, May 2, 2018 6:16 AM
>>> To: arslist@arslist.org 
>>> Subject: Trouble getting rrrchive to run
>>> Hi Listers,
>>> I'm trying to use rrrchive tool (https://rrr.se/cgi/index?pg=chive-doc 
>>> ) to migrate data from Remedy 7.6.4 
>>> to Remedy 9.1.
>>> Here's my config file:
>>> rrrchive.cfg
>>> source_server = sourceservername
>>> source_tcp = 1100
>>> source_user = myusername
>>> source_password = PROMPT
>>> source_form = MyTestForm
>>> target_server = targetservername
>>> target_tcp = 1400
>>> target_user = myusername
>>> target_password = PROMPT
>>> target_form = MyTestForm
>>> splitsearch = YES
>>> transfertype = SYNCTOTARGET
>>> logfile = AUTO
>>> loglevel = DEBUG
>>> progressbar = YES
>>> and here's my log:
>>> rrrchive.log
>>> 1 rrrchive: 2018-05-02 11:51:50, type=APP, level=NOTICE, file=rrrchive.cpp, 
>>> line=5076
>>> 2 Program Start: configfile=rrrchive.cfg
>>> 3 rrrchive: 2018-05-02 11:51:50, type=ARS, level=DEBUG, file=rrrchive.cpp, 
>>> line=365
>>> 4 ARSetServerPort(server=sourceservername, tcp=1100, rpc=0)
>>> 5 rrrchive: 2018-05-02 11:51:50, type=ARS, level=DEBUG, file=rrrchive.cpp, 
>>> line=365
>>> 6 ARSetServerPort(server=targetservername, tcp=1400, rpc=0)
>>> 7 rrrchive: 2018-05-02 11:52:06, type=ARS, level=ERROR, file=rrrchive.cpp, 
>>> line=389
>>> 8 ARGetServerInfo(server=targetservername, 
>>> AR_SERVER_INFO_DELAY_RECACHE_TIME)
>>> 9 API CALL SEVERITY: AR_RETURN_ERROR, failure, status contains details
>>> 10 ARStatusList: contains 1 messages

Re: Trouble getting rrrchive to run

[Thomas Miskiewicz]

Misi, you said: You could also set ARAPILOGGING to 1 prior to running RRR|Chive 
to get the exact API-calls and data to feed to driver in order to reproduce 
this.

How do I do that on a Linux box?


Thomas

> On May 3, 2018, at 8:37 AM, Misi Mladoniczky  wrote:
> 
> Hi,
> 
> You see exactly what the problem is in the log with normal logging turned on.
> 
> You get ARERR 91 with the additional text "RPC: Unable to receive; 
> Asynchronous event occurred".
> 
> You should might want to work with BMC support on this.
> 
> To debug you might use the driver program to do an RPC call both with the 
> 7.6.04 API and the 9.1 API to check if this makes a difference in your case.
> 
> You could also set ARAPILOGGING to 1 prior to running RRR|Chive to get the 
> exact API-calls and data to feed to driver in order to reproduce this.
> 
> If you have the correct server IP and tcp port it should work.
> 
> 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 
> 
> 
> 
> 
> 
> May 2, 2018 3:44 PM, "Thomas Miskiewicz"  >> wrote:
> Thank you, Misi!
> Is there an advanced logging that would help where the problem is?
> Thomas
> 
> On 2. May 2018, at 15:36, Misi Mladoniczky > 
> wrote:
>> Hi,
>> 
>> No, different server versions work just fine.
>> 
>> 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 
>> 
>> 
>> 
>> 
>> 
>> May 2, 2018 2:55 PM, "Thomas Miskiewicz" > >> wrote:
>> The thing is we have 7.6.4 on one side and 9.1.4 on the other side. Problem?
>>> On May 2, 2018, at 2:48 PM, Kevin M Candelaria >> > wrote:
>>> It's definitely compatible with 9.x
>>> I just did a 9.1.00 to 9.1.04 transfer and my config looks like this. 
>>> Worked perfectly fine.
>>> source_server = 
>>> source_tcp = 2020
>>> source_user = 
>>> source_password = 
>>> target_server = 
>>> target_tcp = 2020
>>> target_user = 
>>> target_password = 
>>> target_disabledeletefltr = YES 
>>> target_disablemergefltr = YES
>>> target_disableaudit = YES
>>> target_clearallrecords = YES
>>> multipleforms = HPD:Template, \
>>> HPD:Template Associations, \
>>> HPD:TemplateCustMapping, \
>>> HPD:TemplateSPGAssoc, \
>>> splitsearch = YES
>>> transfertype = SYNCIFNEWER
>>> logfile = AUTO
>>> progressbar = YES
>>> From: ARSList >> > on behalf of Thomas Miskiewicz 
>>> >
>>> Sent: Wednesday, May 2, 2018 6:16 AM
>>> To: arslist@arslist.org 
>>> Subject: Trouble getting rrrchive to run
>>> Hi Listers,
>>> I'm trying to use rrrchive tool (https://rrr.se/cgi/index?pg=chive-doc 
>>> ) to migrate data from Remedy 7.6.4 
>>> to Remedy 9.1.
>>> Here's my config file:
>>> rrrchive.cfg
>>> source_server = sourceservername
>>> source_tcp = 1100
>>> source_user = myusername
>>> source_password = PROMPT
>>> source_form = MyTestForm
>>> target_server = targetservername
>>> target_tcp = 1400
>>> target_user = myusername
>>> target_password = PROMPT
>>> target_form = MyTestForm
>>> splitsearch = YES
>>> transfertype = SYNCTOTARGET
>>> logfile = AUTO
>>> loglevel = DEBUG
>>> progressbar = YES
>>> and here's my log:
>>> rrrchive.log
>>> 1 rrrchive: 2018-05-02 11:51:50, type=APP, level=NOTICE, file=rrrchive.cpp, 
>>> line=5076
>>> 2 Program Start: configfile=rrrchive.cfg
>>> 3 rrrchive: 2018-05-02 11:51:50, type=ARS, level=DEBUG, file=rrrchive.cpp, 
>>> line=365
>>> 4 ARSetServerPort(server=sourceservername, tcp=1100, rpc=0)
>>> 5 rrrchive: 2018-05-02 11:51:50, type=ARS, level=DEBUG, file=rrrchive.cpp, 
>>> line=365
>>> 6 ARSetServerPort(server=targetservername, tcp=1400, rpc=0)
>>> 7 rrrchive: 2018-05-02 11:52:06, type=ARS, level=ERROR, file=rrrchive.cpp, 
>>> line=389
>>> 8 ARGetServerInfo(server=targetservername, 
>>> AR_SERVER_INFO_DELAY_RECACHE_TIME)
>>> 9 API CALL SEVERITY: AR_RETURN_ERROR, failure, status contains details
>>> 10 ARStatusList: contains 1 messages
>>> 11 Number: ARERR 91
>>> 12 Message: Cannot open catalog; Message number = 91
>>> 13