That sounds similar to an issue we had here. There were some users (but
not all) that would occasionally (but not always) get an error like that
when they tried to open the ARTask file. After it being an "outstanding"
issue for a while, we tracked it down to the open action of the file
association. We needed to put double quotes around the filename parameter
("%1") in the "Open" action. The issue was only with filenames that had
spaces or other special characters in it and the double quotes took care
of that.
It was a goofy little bugger to find, but once found, it was simple to
fix. Hopefully, that helps.
Thad Esser
Remedy Developer
"Argue for your limitations, and sure enough, they're yours."-- Richard
Bach
"Kaiser Norm E CIV USAF 96 CS/SCCE" <[EMAIL PROTECTED]>
Sent by: "Action Request System discussion list(ARSList)"
<[email protected]>
07/30/2007 09:33 AM
Please respond to
[email protected]
To
[email protected]
cc
Subject
Re: Associating .ARTASK Files to VBS
Unfortunately that doesn't work. Windows won't allow it. It throws a
bogus error about ARTASK files not being valid executables.
And to answer your question, just use a "standard" password for all
users.
-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Heider, Stephen
Sent: Monday, July 30, 2007 10:57 AM
To: [email protected]
Subject: Re: Associating .ARTASK Files to VBS
**
Norm,
You should be able to change the associated program for file extensions
here: My Computer > Tools > Options > File Types > file extension.
How are you handling the User Tool authentication? The Windows user
name is easy enough to capture, but how do you handle feeding the User
Tool the password? Or how are you bypassing the password?
Stephen
________________________________
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Kaiser Norm E CIV USAF 96
CS/SCCE
Sent: Monday, July 30, 2007 11:40 AM
To: [email protected]
Subject: Associating .ARTASK Files to VBS
**
Hello everyone:
I have a creative problem and I'd sincerely appreciate any/all
suggestions or ideas. I don't even know if what I'm trying to do is
possible, but I'm open to all ideas.
I've written a neat little application that, when executed, launches the
Remedy User client and logs the user on automatically. What I really
like about it is that it also works with .artask attachments. That is,
Remedy shoots the user a message: "You have a ticket assigned to you.
Click the attachment below to view it." The user double clicks the
attachment, and my executable first checks to see if Remedy is running.
If it is not, it launches Remedy as the user logged on to the OS, and
then it launches ARTask, which in turn, displays the ticket.
It's a very simple (poor man's) SSO. It works great.
Here's the problem. The application I wrote is, well, an application.
That is, it's an .EXE. In my environment, putting new .EXE files on
workstations is a no-no, but putting scripts (such as VBS) is perfectly
fine. So I completely re-wrote the application as a VB script. It
works fine...except for the .ARTASK association. Evidently in Windows
XP, one cannot associate a file to be run by a VB script the way one
would, say, associate a .DOC file be opened with Word.
So now I'm stuck. I need some way to change the file association of
.ARTASK to ARtask.exe to .ARTASK to custom VBS. Any ideas?
Norm
__20060125_______________________This posting was submitted with HTML in
it___
__20060125_______________________This posting was submitted with HTML in
it___
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
the Answers Are"
***IMPORTANT NOTICE: This communication, including any attachment, contains
information that may be confidential or privileged, and is intended solely for
the entity or individual to whom it is addressed. If you are not the intended
recipient, you should delete this message and are hereby notified that any
disclosure, copying, or distribution of this message is strictly prohibited.
Nothing in this email, including any attachment, is intended to be a legally
binding signature.***
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"
