Re: Failed to create virtual directory

From: Kevin (klocke_at_techdata.com)
Date: 04/30/04 

Date: 30 Apr 2004 09:48:46 -0700

Marty,

I was able to resolve the problem by adding the computer account to
the local admin group of DP. We are using advanced security and after
looking through the log files on my primary site it should that it
couldn't connect to the DP. Once I added the computer account of my
primary site to the DP local admin group I re-pushed the Software
Package to the DP and it work.

Hope this helps you too.
Kevin

klocke@techdata.com (Kevin) wrote in message news:<be48a764.0404291004.2e393592@posting.google.com>...
> Marty,
> I having the same problem? For some reason I can't push any install or
> Updates because the packages never get to my DP and the error keep
> stating the I need to have the Base IIS installed. I'm running Windows
> 2003 with IIS 6 install and have ASP, Bits, WebDav enabled?
>
>
>
> "Marty List" <Bill.Gates@sun.com> wrote in message news:<c6k3kj$csbv3$1@ID-172409.news.uni-berlin.de>...
> > I'm trying to get SMS 2003 setup in a lab, I'm experienced with 2.0 but new
> > to 2003. So far so good, until I tried to configure the Software
> > Updates/Inventory Scanning Tools/Security Patch puzzle. Is anyone using
> > this? Seems like a lot of smoke and mirrors, if you understand what's going
> > on maybe it's better to do it manually?
> >
> > So anyway, I'm getting this error logged by the SMS_DISTRIBUTION_MANAGER:
> >
> > ================================
> > Failed to create virtual directory on the defined share or volume on
> > distribution point "["Display=\\TOPAZ1\"]MSWNET:["SMS_SITE=OX1"]\\TOPAZ1\".
> >
> > Possible cause: Distribution Manager requires that IIS base components be
> > installed on the local SMS Site Server in order to create the virtual
> > directory. Distribution Manager also requires that IIS Web Services be
> > installed on the Distribution Point Server that needs to support Background
> > Intelligent Transfer Service (BITS).Solution: Verify that IIS base
> > components are installed on the local SMS Site Server, and IIS Web Services
> > are installed on the Distribution Point Server.
> > ================================
> >
> > The Site Server and the Distribution Point are the same server, and IIS is
> > installed and running. The BITS Server Extensions are also installed. I'm
> > using Advanced Security in case that matters.
> >
> > Any suggestions?

Relevant Pages

  • Re: adding user to local admin group on sbs server
    ... in the local admin group of the server. ... I was able to install Spectorsoft ... agent on another workstation fine, ... There is no such thing as a local admin group on a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: Advanced client install!
    ... > the local admin group on the DC's. ... Now have brought up a new installation and things are working fine ... Well i am able to logon to the server ... >> the server from the site server using the same account. ...
    (microsoft.public.sms.admin)
  • Re: Reinstall SMS on a different server w/ different site name
    ... > finally decided to just do a fresh install of SMS. ... > install SMS Site on a different server. ... > same site code on a different site server will the clients pick up the new ...
    (microsoft.public.sms.setup)
  • Re: adding user to local admin group on sbs server
    ... in the local admin group of the server. ... I was able to install Spectorsoft ... agent on another workstation fine, ... There is no such thing as a local admin group on a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: SCCM with a remote SQL instance problems
    ... This is one of the reason why I ALWAYS recommend that SQL be on the same box as the site server, you will not run into these issues. ... "Setup failed to install SMS Provider" ...
    (microsoft.public.sms.installer)
Loading