"Could not find a part of the path… " error on IIS 6.0

From: dsh (darrienhess_at_yahoo.com)
Date: 01/19/04


Date: 19 Jan 2004 04:59:24 -0800

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 –A 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?



Relevant Pages

  • Re: Configuring Active Directory to Run as a Domain User Account
    ... I need to do this so that Active Directory can do DNS ... > queries upstream to a DNS server that is on the other side of a proxy ... Proxy Server is configured to only let queries go out of our ...
    (microsoft.public.windows.server.active_directory)
  • Configuring Active Directory to Run as a Domain User Account
    ... I need to do this so that Active Directory can do DNS ... queries upstream to a DNS server that is on the other side of a proxy ... Proxy Server is configured to only let queries go out of our ...
    (microsoft.public.windows.server.active_directory)
  • Re: Server 2003 newbie questions
    ... Biggest problem in a workgroup is that you have to configure the same user account and password on all machines, where the user should have access. ... So in your case with at least 12 users, all accounts and passwords have also to be configured on the server to access the share. ... Active directory groups can be used for this. ...
    (microsoft.public.windows.server.setup)
  • Re: help with domains
    ... the user account. ... then log on to terminal server and they need different ... what we want to do is use a third server running ... do active directory stuff for each user, ...
    (microsoft.public.windows.server.active_directory)
  • Re: 2003 Migration
    ... Best Practice Active Directory Design for Managing Windows Networks ... Windows Server 2003 Tools ... ensure that you have designed a DNS and Active ...
    (microsoft.public.windows.server.active_directory)

Loading