SQL server 2008 service: access to Excel object model
- From: David Walker <none@xxxxxxxx>
- Date: Wed, 17 Sep 2008 09:44:35 -0700
We have a situation where a service, which is running as a domain user,
gets an HResult of 0x800A03EC when calling the Excel 2003 object model,
only when actually running as a service.
The same code, when running as a console app, works fine.
We have already checked to make sure that Excel has been told to allow
access to the Excel/VBA object model, per KB article 282830. We made this
setting change while logged on as the domain user that the service runs
under. We stopped and restarted the service to make sure no registry
entries were cached or anything like that.
Are there more security checks that a *service* has to go through, like
policy settings, which apply to a service, that don't cause a failure when
running as a console application?
The code that's doing the calling is C#.
Thanks a bunch for any suggestions.
David Walker
.
- Follow-Ups:
- Re: SQL server 2008 service: access to Excel object model
- From: Erland Sommarskog
- Re: SQL server 2008 service: access to Excel object model
- Prev by Date: Re: Error 15404 - SQL 2005
- Next by Date: SQL Agent traffic
- Previous by thread: Error 15404 - SQL 2005
- Next by thread: Re: SQL server 2008 service: access to Excel object model
- Index(es):
Relevant Pages
|