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 <m...@rrr.se> 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 <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 > <http://rrr.se/> > > > > > May 2, 2018 3:44 PM, "Thomas Miskiewicz" <tmisk...@gmail.com > <mailto:%22Thomas%20Miskiewicz%22%20<tmisk...@gmail.com>>> 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 <m...@rrr.se <mailto:m...@rrr.se>> > wrote: >> Hi, >> >> No, different server versions work just fine. >> >> Best Regards - Misi, RRR AB, http://www.rrr.se <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 >> <http://rrr.se/> >> >> >> >> >> May 2, 2018 2:55 PM, "Thomas Miskiewicz" <tmisk...@gmail.com >> <mailto:%22Thomas%20Miskiewicz%22%20<tmisk...@gmail.com>>> 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 <ke...@temple.edu >>> <mailto:ke...@temple.edu>> 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 <arslist-boun...@arslist.org >>> <mailto:arslist-boun...@arslist.org>> on behalf of Thomas Miskiewicz >>> <tmisk...@gmail.com <mailto:tmisk...@gmail.com>> >>> Sent: Wednesday, May 2, 2018 6:16 AM >>> To: arslist@arslist.org <mailto: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 >>> <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, >>> file=rrrchive.cpp, line=5090 >>> 16 Program End: configfile=rrrchive.cfg, timetorun=0:00:16 <> >>> Questions: >>> 1. Does the error ARERR 91 mean, that rrrchive is not compatible with >>> Remedy 9.1? I found here, that it is possible cause of this error: >>> https://communities.bmc.com/message/133550 >>> <https://communities.bmc.com/message/133550>: >>> "A less common cause of this error is running an API program that is >>> incompatible with the AR System server." >>> 2. The rrrchive config installation instruction says: >>> "Make sure that the following shared objects are in the LD_LIBRARY_PATH. >>> Copying the included libraries to the installation directory will allways >>> work." >>> My guess is, that in my case the app should use different shared objects >>> for the source server and different for the target server. >>> Is it possible to configure it that way? >>> Thanks! >>> Thomas >> -- >> ARSList mailing list >> ARSList@arslist.org <mailto:ARSList@arslist.org> >> https://mailman.rrr.se/cgi/listinfo/arslist >> <https://mailman.rrr.se/cgi/listinfo/arslist>-- > ARSList mailing list > ARSList@arslist.org > https://mailman.rrr.se/cgi/listinfo/arslist
-- ARSList mailing list ARSList@arslist.org https://mailman.rrr.se/cgi/listinfo/arslist