Also tried this: "C:\Program Files\AR System\Admin\arimportcmd" -u user -p password -M C:\Mappings\Findings.arm -l C:\Mappings\logfile.log
Same error. Rick On Thu, Mar 27, 2008 at 3:45 PM, Rick Cook <[EMAIL PROTECTED]> wrote: > "C:\Program Files\AR System\Admin\arimportcmd.exe" -u user -p password -M > "C:\Mappings\Findings.arm" -l C:\Mappings\logfile.log > > Rick > > > On Thu, Mar 27, 2008 at 3:40 PM, Joe D'Souza <[EMAIL PROTECTED]> wrote: > > > ** Could you let us know what the import command that you typed looks > > like? If its complaining about the command, maybe there must be something in > > there that is offending its syntax? > > > > I've got feed like that from support ranging from have you read the > > manual to you should go for training when I was working on the RKM product.. > > Almost every other ticket I raised on RKM ended up being a software bug. So > > I'm hardly likely to consider spending $$$'s for training myself on > > something that is flaky in the first place! To add to that the documentation > > on that product is far from 100% accurate.. Even the screen shots on some > > places are inconsistent to what you actually see when you install the > > product (Version 7.1 patch 1 of RKM).. > > > > Joe > > > > -----Original Message----- > > *From:* Action Request System discussion list(ARSList) [mailto: > > [EMAIL PROTECTED] Behalf Of *Rick Cook > > *Sent:* Thursday, March 27, 2008 5:34 PM > > *To:* [email protected] > > *Subject:* Re: arimportcmd error > > > > ** Thanks, Joe. It will take the long format as long as the string is > > in quotes - it worked for me yesterday. I'll keep that suggestion in my > > back pocket, though, in case nothing else works. > > > > Your response was much more helpful than the initial one from Support, > > which was basically some script monkey in India saying RTFM. Gee, I hadn't > > thought of that. If there was any troubleshooting data in the docs or the > > KB, I wouldn't have needed to make a ticket. sigh... > > > > Rick > > > > On Thu, Mar 27, 2008 at 2:12 PM, Joe D'Souza <[EMAIL PROTECTED]> wrote: > > > > > ** Try putting a 8.3 format DOS path in the path instead of the > > > regular windows path.. If all else as you say is correct, it may be not > > > liking the long path format if you have it set like that.. > > > > > > Joe > > > > > > -----Original Message----- > > > *From:* Action Request System discussion list(ARSList) [mailto: > > > [EMAIL PROTECTED] Behalf Of *Rick Cook > > > *Sent:* Thursday, March 27, 2008 4:51 PM > > > *To:* [email protected] > > > *Subject:* arimportcmd error > > > > > > ** First, I can't believe that there are no Remedy KB entries for > > > arimportcmd. None. Wow. > > > > > > We are attempting to use arimportcmd in an Active Link to import a > > > small number of records into a form. We have a mapping file that works > > > just > > > fine in the Import Tool. When we attempt to run it from the Active Link > > > or > > > the command line, using the same user/pw and mapping file, we get an error > > > that says that the Import command line is missing the schema option or > > > has a > > > wrong format. There isn't even an arimportcmd parameter for the schema, > > > so > > > I don't know what it's complaining about. > > > > > > Any ideas to help us out? We verified the paths, file names, etc., > > > and all names match exactly, including case. > > > > > > Rick > > > > > > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > > html___ > > > > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
