Thanks for the hint - I was not providing a filename for the log file, only the export.arx file. As soon as I provided the log file name.log it worked. I also ran it locally on the AR Server instead of on a workstation like I was doing yesterday, but it would have to work from a remote client to useful if your AR is on *nix. I'll try importing them now, after I make sure the SLM environment on the production server is identical to that of the development box. Thanks again!
Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Leonard Neely - FOJ > Sent: Friday, February 22, 2008 8:33 PM > To: [email protected] > Subject: Re: SLM 7.1 Questions > > This addresses your first question. From what I can see, I > think you may need to provide a file extension with your > export and log file name. I tested this, and it seemed to > work fine for me. I did notice that it took a while (over a > minute) before it actually created the .arx file at the > destination path. > > It also took several minutes to complete, even when only > exporting a few ST's. I do belie that there may be some > documentation errors, as a login and password is not needed > to export Service Targets. Also, yes..., when you click OK > on the message, the export window closes and leaves you back > at the app admin console. > > HTH > > Leonard Neely > Column Technologies _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
