infopath sp2 - automation failed in windows service

[minjie s]

Hi,

I have a windows service that can be started on the local computer. What it
does is to run a batch file that calls a JScript program which has a bunch of
Infopath automation code. It was working perfectly under infopath SP1 until
yesterday I upgrade to SP2. The following line

var oApp = new ActiveXObject("InfoPath.Application");

caused familiar error "Microsoft Office Infopath has encountered a problem
and needs to close".

When I go into the event viewer, it shows the following error:

Faulting application infopath.exe, version 11.0.6565.0, stamp 42cace3a,
faulting module mso.dll, version 11.0.6568.0, stamp 42e18ef6, debug? 0, fault
address 0x0003446c.

I reproduced the same error on three XP machines.

Is this some bug introduced in SP2? Did anyone experience the same problem?

Any help is greatly appreciated.

 

[Franck Dauché]

Hi,

If you open IP and go to Help / About....
which version do you have? 11.6565.6568 (SP2), right?

Franck Dauché

 

[minjie s]

Yes, it is!

I forgot to mention in my original post that the same batch file that calls
the JScript program works fine under the command prompt. The problem only
occur when it is shelled out from the windows service.

Thanks for the reply. I am in desperate trying to figure this one out.

 

[Franck Dauché]

...and I bet you that it works if you are calling the script from InfoPath
code behind. If it is the case, you may want to check if there are
references to this in a newsgroup related to general Office Install and
Upgrades.
That issue may not be InfoPath related at all.

Regards,

Franck Dauché

 

[minjie s]

Hi, franck,

Thanks for the replay. You know, you were absolutely right about the issue
having nothing to do infopath. It turns out that once I uninstalled office
2003 and reinstalled and reapplied SP1, the program got to work again. I
assume the problem is caused by the mso.dll in C:\Program Files\Common
Files\Microsoft Shared\OFFICE11. The version of the file from SP1 is
11.0.6360.0 and the version of the file from SP2 is 11.0.6568.0.

Because I have two other XP machine (one being windows 2003 server and one
being windows XP) that is experiencing the same problem, I think I could
safely assume this is a bug in office 2003 SP2.

I am so glad this one worked out finally, this is the only way (using
windows service, shell script and JScript) I can automate the infopath to be
used by client computer.

Thanks again for your input!