Yes, Excel is on the machine and I am able to open up the file (which downloaded correctly). That's the only error I have, unfortunately. I was hoping someone using Excel and Watir together might know of an environment issue that could be causing the problem, since I agree it doesn't seem to be the code ;-) It never triggers on my development box with all the nice debugging tools.
On Oct 14, 12:07 pm, Ethan <[email protected]> wrote: > I don't think this has anything to do with AutoIt, or indeed Watir - the > error is about excel, and looks like a WIN32OLE error. > > Is Excel actually installed on your automation box? I've seen this error on > machines where Excel has not been installed. > > If that's not the issue, you'll need to include more than the error message > - at a bare minimum include the full error class, stacktrace, and message, > and the code that raised the error. But if it's not actually anything to do > with Watir (and it doesn't look like it is), I don't know that anybody will > necessarily be able to help you here. > > On Thu, Oct 14, 2010 at 14:58, Schase <[email protected]> wrote: > > I have a watir test that downloads some information from a web app to > > an Excel file, and I then open the file to confirm the contents. On my > > dev box everything works fine, but the scheduled automation runs (via > > Hudson) always fail attempting to open the Excel file. I have checked > > that the correct version of AutoITX3.dll is registered on both > > machines (Ruby 1.8, Watir 1.6.5). No other versions of AutoITx3 are > > registered on either machine. The error on the Hudson box is the one > > expected if the dll is NOT registered, but it is present in regedit in > > the same location as on my dev box. Both machines are WinXP. Running > > the test manually on the Hudson box results in the same error -- > > unknown OLE server: 'Excel.Application' HRESULT error code:0x800401f3 > > Invalid class string. > > > I searched for similar errors and saw one instance here where running > > on a virtual machine had caused similar problems, but only if the VM > > window was closed. I don't think this is a code error since it runs on > > the dev box. Any suggestions for debugging this? > > > TIA, Sabrina > > > -- > > Before posting, please readhttp://watir.com/support. In short: search > > before you ask, be nice. > > > [email protected] > >http://groups.google.com/group/watir-general > > [email protected]<http://groups.google.com/group/watir-generalwatir-general+unsubscribe...> -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. [email protected] http://groups.google.com/group/watir-general [email protected]
