Hi Dave:What about using this utility I designed purposely when we get troubles
with archive
ArLiteUser[2.0] Multi-threading BMC-REMEDY API | BMC Communities
|
|
| |
ArLiteUser[2.0] Multi-threading BMC-REMEDY API | BMC Communities
ArLiteUser[2.0] Multi-threading BMC-REMEDY API Overview The ArLiteUser utility
consist of 2-modules, data-migr...
|
|
|
Thanks & Regards
____________________________________________
AliAbdelaziz Musa
BMC-REMEDYTechnical Lead
BMC-REMEDYPartener - Saudi TELECOMProject
____________________________________________
On Thursday, May 3, 2018 12:18:44 AM, Dave Shellman
<[email protected]> wrote:
If there is a firewall the telnet port is likely open. It would be unusual a
firewall to have all ports open to a server.
Dave
On Wed, May 2, 2018 at 4:35 PM Thomas Miskiewicz <[email protected]> wrote:
Yes, it is.
On 2. May 2018, at 21:46, Dave Shellman <[email protected]> wrote:
The port for the ARSystem should be a completely different port than the Telnet
port.
Dave
On Wed, May 2, 2018 at 3:41 PM Thomas Miskiewicz <[email protected]> wrote:
telnet hostname port works just fine. I’ll try the IP address.
On 2. May 2018, at 20:56, Fawver, Dustin <[email protected]> wrote:
Usually when I get that error message, it’s because of one of two things.
1) I don’t have an appropriate firewall exemption on the ARS server for the
machine that’s running RRRCHIVE.
2) For whatever reason, I have to specify the IP address of the source
and/or target server instead of the hostname.
I hope this helps.
Dustin Fawver
Sr. Help Desk Technician
Information Technology Services
P: 423-439-4648
[email protected]
<image001.png>
From: ARSList [mailto:[email protected]]On Behalf Of Thomas Miskiewicz
Sent: Wednesday, May 02, 2018 9:42 AM
To: ARSList <[email protected]>
Subject: [EXTERNAL] Re: Trouble getting rrrchive to run
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 <[email protected]> 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" <[email protected]> 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 <[email protected]> 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 <[email protected]> on behalf of Thomas Miskiewicz
<[email protected]>
Sent: Wednesday, May 2, 2018 6:16 AM
To: [email protected]
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, 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:
"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
[email protected]
https://mailman.rrr.se/cgi/listinfo/arslist
The [EXTERNAL] tag in the subject line identifies emails that do NOT originate
from an ETSU person or service. Please exercise caution when handling emails
from external sources. Any email that is unsolicited and requires you to take
immediate action, appears to be forged or is PHISHING for information can be
verified by emailing the ITS help desk.
--
ARSList mailing list
[email protected]
https://mailman.rrr.se/cgi/listinfo/arslist
--
ARSList mailing list
[email protected]
https://mailman.rrr.se/cgi/listinfo/arslist
--
ARSList mailing list
[email protected]
https://mailman.rrr.se/cgi/listinfo/arslist
--
ARSList mailing list
[email protected]
https://mailman.rrr.se/cgi/listinfo/arslist
--
ARSList mailing list
[email protected]
https://mailman.rrr.se/cgi/listinfo/arslist
--
ARSList mailing list
[email protected]
https://mailman.rrr.se/cgi/listinfo/arslist
