WinAutomation Logo

1.

Getting this particular error on 'Run VBScript' action:

On WinXP x86:

 

Input Error: Can not find script file "C:\Documents".

 

 

 

On Win7 x86:

 

Input Error: Can not find script file "C:\Users\xyz".

 

 

 

Any space in the file-path is making the 'Run VBScript' action module to error out?

Where does it want to expand to? %temp% path? to save/run a temporary VBScript file (*.vbs)?

-------------------------------------------------------------------------
2.

The "Custom Headers" in 'Invoke Web Service' action has a few limitations:
 

The following headers can't be set:

Connection
Content-Length
Date
Expect
Host
If-Modified-Since
Range
Referer
Proxy-Connection

 

If the above ^ are used, it results in:
 

Runtime Error: Failed to download from Web:This header must be modified using the appropriate property.Parameter name: name

 

The "referer" header part is very important when automating. I tried setting it as --> Referer: host.com
got the error previously mentioned.

Reference: http://stackoverflow.com/questions/239725/c-sharp-webrequest-class-and-headers

-------------------------------------------------------------------------
3.

'Invoke Web Service' action > 'Advanced' tab > 'Connection Timeout' field

Accepts integer values but defaults to the default value (30) after being set.

How to replicate:
  [i] Set the 'Connection Timeout' to say 31 > Click 'OK' to save an exit the 'Invoke Web Service' action dialog box
 [ii] Now open/double-click the action you just added to the queued actions window
[iii] Go to 'Connection Timeout' field > You'll see that it has default-ed to 30
-------------------------------------------------------------------------

Can users please report back? Thanks.

(*.waj file attached)

 

I got the same error on XP:

Input Error: Can not find script file "C:\Documents".

Is there already a solution?

Hi gwidon

 

No official soln./patch/fix available for any of the above bugs at the moment, after the v4.0.0.1256 release.

------------------

A workaround:

 

http://www.winautomation.com/forum/getting-data-computer-when-application-runinstalled#post_4

 

From post #4, get the "WMI_HDD_serial_using_vbs.waj" file.

 

=================================

 

This bug is/might be related to:

 

http://www.winautomation.com/forum/possible-bug-run-dos-command-module

@WA

 

Any update?

Hi t-hex,

 

sorry for the delayed reply. Yes, I can confirm both bugs, and we'll have a fix in our next maintentance release asap (if possible by the end of the week).

 

 

Hi all,

 

I got the same error on Windows 2003 server:

Input Error: Can not find script file "C:\Documents".

is the fix patch available please ?

 

Kind regards

 

Cyril
 

we're expecting a maintenance realease to be made available within the next couple of weeks at the latest

 

Samantha

Ditto on this Run VBScript action error on Windows XP 32-bit with WinAutomation 4.0.0.1256

 

%VBScriptOutput% = Input Error: Can not find script file "C:\Documents"

 

Charles

Yes, this is a known bug Charles, and a fix for it has been implemented already, and will be available shortly, within the forthcoming maintenance release

 

Samantha

Found another "interesting" situation. Just upgraded to V4 at work. So, I opened an previous V3 job and noticed that, although my job designer options were set to "Show Small Icons" and no "Show Action Name" - that the Action Names were actually displayed. That only happened on the FIRST open of the job, and only that job. After that, all was well. Kind of odd.

It's odd indeed! I'm afraid I could not reproduce it, however, I'll keep my eyes open for any similar cases, before I can open a ticked for this one.

 

Samantha

 

 

3.

 

'Invoke Web Service' action > 'Advanced' tab > 'Connection Timeout' field

Accepts integer values but defaults to the default value (30) after being set.

How to replicate:
  [i] Set the 'Connection Timeout' to say 31 > Click 'OK' to save an exit the 'Invoke Web Service' action dialog box
 [ii] Now open/double-click the action you just added to the queued actions window
[iii] Go to 'Connection Timeout' field > You'll see that it has default-ed to 30
 

 

^ still there on v4.0.3.1892

 

---------------------------------------------------------------------------

 

4.

 

"Cookie" header, if present in "Invoke Web Service > Custom Headers" has no effect.

Hi t-hex,

 

you are right, we've corrected this in v. 4.0.4 which we made available today. Thanks for bringing this into attention

updated to the latest version getting this error 

Edited: Ignore it , working fine now.

Thanks for the reply Marios. Issue no. 3 was fixed after upgrading WA to v4.0.4.2093. Thanks again for the awesome support :)

Also, can you please look into this:

4.

"Cookie" header, if present/set in "Invoke Web Service > Custom Headers" has no effect.

Setting client side cookie, does not show up in the actual request sent during the execution of the "Invoke Web Service" action/command. Client set cookie seems to be stripped off from the request.

How to replicate:
  [i] Set the 'Custom Headers' field in the 'Invoke Web Service' action dialog box to, say:

      "Cookie: name1=value1; name2=value2"
      (without quotes)
      
      > Click 'OK' to save and exit the 'Invoke Web Service' action dialog box

 [ii] Setup a TCP/HTTP debugger to capture client-side requests
[iii] Run the concerned 'Invoke Web Service' action/command
[iv] View the captured request in TCP/HTTP debugger

      > See if 'Cookie' header is present/set in the request.

thanks for the details, we entered it in our issue tracking system and we'll fix it in our next maintenance release. The current release was already scheduled, so we only had time to to correct the timeout glitch, which was a quick fix

Any update on the 'Cookie' header issue? Having a really hard time processing jobs dependent on cookie manipulation :|

The "Cookie" header issue has been fixed already and a fix for it will be included within the next maintenance release

 

Samantha

Thanks so much for the reply Samantha :)