Re: SQL server 2008 service: access to Excel object model
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Wed, 17 Sep 2008 15:02:53 -0700
David Walker (none@xxxxxxxx) writes:
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?
I'm not sure that I understand where SQL 2008 comes into the
picture. But calling Excel from a service seems dubious to me. Excel
usually likes to have a desktop, and services do not have a desktop.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- Follow-Ups:
- Re: SQL server 2008 service: access to Excel object model
- From: David Walker
- Re: SQL server 2008 service: access to Excel object model
- References:
- SQL server 2008 service: access to Excel object model
- From: David Walker
- SQL server 2008 service: access to Excel object model
- Prev by Date: RE: message digests and sql server
- Next by Date: Re: SQL server 2008 service: access to Excel object model
- Previous by thread: SQL server 2008 service: access to Excel object model
- Next by thread: Re: SQL server 2008 service: access to Excel object model
- Index(es):
Relevant Pages
|