Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / Interop / March 2005

Tip: Looking for answers? Try searching our database.

Windows 2003, Excel and SAP.NET

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Carmen - 17 Mar 2005 18:47 GMT
I have an ASP.NET application that exports some data to Excel via Interop.
The application is working fine in Windows 2000 Server. Now we are changing
our servers and we have installed Windows 2003 Server Enterprise Edition,
the application works fine, but it does not export to Excel. I have looked
into the Task Manager of the Server and I don?t see the Excel.exe process,
so I suppose that it is a privileges problem and the application is not able
to load this process.

Could anyone help me?

Thanks in advance.
Fredrik Wahlgren - 18 Mar 2005 22:02 GMT
> I have an ASP.NET application that exports some data to Excel via Interop.
> The application is working fine in Windows 2000 Server. Now we are changing
[quoted text clipped - 7 lines]
>
> Thanks in advance.

Do you use the same version of Excel as before? Have you checked the log?

/Fredrik
Carmen - 21 Mar 2005 08:45 GMT
Antes ten?a instalado el Office XP, pero tambi?n fallaba, por tanto, he
decidido instalar el Office 2003.
En el EventViewer tengo el siguiente error:

Access denied attempting to launch a DCOM Server. The server is:

{00024500-0000-0000-C000-000000000046}

The user is NETWORK SERVICE/NT AUTHORITY, SID=S-1-5-20.

Access denied attempting to launch a DCOM Server. The server is:

{00024500-0000-0000-C000-000000000046}

The user is NETWORK SERVICE/NT AUTHORITY, SID=S-1-5-20.

?Alguna idea?

Muchas gracias por responder.

> > I have an ASP.NET application that exports some data to Excel via Interop.
> > The application is working fine in Windows 2000 Server. Now we are
[quoted text clipped - 13 lines]
>
> /Fredrik
Andrew Hayes - 31 Mar 2005 07:30 GMT
This is similiar to a problem I am having. Windows 2003 Server is far more
strict when it comes to what users/identities can run which applications.
The only thing I've come across is references to the DCOM Config of the
Microsoft Excel Application.

Here's what I did:

On the Windows 2003 server, start Component Services from the Administrative
Tools. Open the Component Services tree, open the Computers tree, and open
the My Computer tree.

You should see one or more of COM+ Applications, DCOM Config, Distributed
Transation Coordinator and Running Processes, and maybe others.

Open the DCOM Config tree. Scroll down to Microsoft Excel Application,
right-click it and select Properties. Click on the Security tab, and in the
first frame (Launch Permissions), click the Customize radio button and then
click on the Edit... button.

In the Launch Permission dialog, click Add... and add the NETWORK SERVICE
account. Click OK, close all the dialogs and reboot the server just to make
sure the changes take.

Try your app again.

Hope this helps.

Regards...Andrew

> Antes ten$ByB(B instalado el Office XP, pero tambi$BqO(B fallaba, por tanto, he
> decidido instalar el Office 2003.
[quoted text clipped - 37 lines]
> >
> > /Fredrik

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.