Asp.Net, Security/Permission issue with OWC 11.0 on a Windows 2003 server running IIS 6.0

1. Security/Permission issue with OWC 11.0 on a Windows 2003 server

Hi all,

I've got what I think is a security/permission issue related to using the
OWC 11 components on a Windows 2003 server.  My web app has a client side
Excel grid, and it also creates an server side OWC Excel component to do
some formatting.  This app all runs just fine and dandy on a Windows 2000
server.  But, when I try and run my app on a Windows 2003 server I get a
message when I try and display my grid about the XML not being formatted
correctly.  This error message is usually the result of a failure with the
the server side
OWC Excel component.  If I run my app with a case that doesn't require the
server side
OWC Excel component to be created, I don't have this problem.  So I'm
thinking that I need to grant permission on something - the OWC files, to
someone - the ASPNet worker account, ???.  I'm just not sure what needs
access to what.  Does anyone have any experience with this ?

Thanks in advance,
Nick

2. IIS 6.0 do not run .asp pages under Windows 2003 server standart e - Asp.Net Web Service

3. Crystal Reports v8.5 Pro & IIS 6.0 on Windows Server 2003

My web app fails to show the crystal report when on Windows Server 2003.  It 
uses a report template.  My app returns the following cryptic error:

   Error #507
   An exception occurred
   (Source: Microsoft VBScript runtime error)
   Please contact your administrator about the problem
   (ifrmReportViewerReport.asp). 

The cache folder shows:
04/20/2005  11:16 AM                 0 {A6E9EE464E6D4471B6C5CBFD7AD012F6}.rpt 

On a Windows 2000 Server, the web app and report comes up fine.
Help appreciated!
<Khanh>

4. IIS 6.0 and Windows Server 2003 - Cookie Problem with .NET WebRequ

5. Windows Server 2003/IIS 6.0/ASP.NET "Could not find a part of the path"

I have an ASP.NET web application running on a load-balanced Windows
Server 2003 web farm running IIS 6.0, using Active Directory
authentication.  I'm trying to programmatically create a new directory
on a different server in the same domain.  Before we switched to 2003,
I was able to simply change the user in the machine.config file to a
domain user with permissions.  In 2003 I have done the following:

1.	Created a new domain user account.
2.	Made this user an Administrator on all servers.
3.	Created a new application pool and set the Identity of the App Pool
to the new user.
4.	Set my application to use this app pool.
5.	Added this user account to the IIS_WPG group.
6.	Added User Rights of "adjust memory quotas for a process" and
"Replace a process level token" to this user account.
7.	Used the SETSPN to add a SPN for this user account using syntax:
SETSPN.EXE  HOST/<computer name> Domain\UserAccount

I'm still getting the "Could not find a part of the path error when
the System.IO.Directory.CreateDirectory method is called.

Any ideas?

6. WSE 3.0, Kerberos & Windows Server 2003 (IIS 6.0)

7. IIS 6.0, Windows 2003, SQL Server 2000 Integrated Authentication error (null user)

Hello,

I have been attempting to configure an intregrated (AD and Windows)
authentication between two servers running an ASP.NET/SQL Server 2000
environment for months.  I have not been able to make this work as
documented, no matter what KB articles I follow or how much I upgrade
software.

Right now,  I have upgraded the IIS server to Windows 2003 Server with
FPSE, Service Pack 2 of .NET Framework 1.0, and set authentication to
Windows Integrated authentication only.  We are using Visual
Studio.NET 2002, and upgrading to 2003 is not currently an option.

The SQL Server 2000 box has also been upgraded to Windows 2003, uses
mixed authentication, and has the AD group in the database.

The user authenticates properly to the main page, but when he attempts
to authenticate to the database (on a separate Windows 2003 Server)
via a Web Form, the following error message occurs (yes I know it's a
common one):

Error=Login failed for user '(null)'. Reason: Not associated with a
trusted SQL Server connection.

I've tried a variety of connection strings, even played with OLE DB,
but nothing works.  The string I am using right now is:

"Data Source=MYSERVER;Initial Catalog=MYDB;Integrated Security=SSPI;" 

In my web config fille, I also have the following settings.  

<authorization>
	<allow roles="mydomain\mygroup" />
	<deny users="*" />
</authorization>

<identity impersonate="true" />

The AD group has been granted public, datareader, and datawriter
permission in the SQL Server database, and basic permissions on the
web site.  Standard database password and userid connection strings
work, but that's not acceptable for this application.

I do not have DBA or Administrator access to the SQL server box, so if
the problem is on that end, I need an explanation in very plain terms
to convey to the DBA as to what needs reconfiguring.

Please email me as well as post to the groups, as I am desparate for
an answer, and the next step is a support ticket with Microsoft that
will have to be coordinated amongst organziations and vendors.  Need I
say more?

Thanks in advance,
Julie Cooper
 XXXX@XXXXX.COM ;
 XXXX@XXXXX.COM 
	

8. .NET 3.0 and IIS 6.0 on Windows Server 2003 SP2 - .Net Framework