Prev: The tracking database on <> is not available...
Next: Exchange 2007 error: 451 4.4.2 Connection dropped
From: Troy Bruder on 6 Jan 2009 18:48
I inadvertently set a HTTP redirect on my Exchange 2007 / IIS7 server on the
Default Website and let it apply to all inherited virtual directories.
Whoopsie. I was able to simply turn off the redirect on MOST of the virtual
directories, but there are a bunch that generate an error when I click Apply
changes: Exadmin, Exchange, Exchweb, Public,

Error: Cannot write configuration file.

Help!! Any ideas for me?

Troy


From: milind.naphade on 7 Jan 2009 07:48
Why don�t you go ahead and paste the bunch of errors that you get while
applying the changes? you may also want to rename the internal and
confidential information.

if "Cannot write to configuration file" is the only error message you see
then probably you are missing on looking at application logs and the IIS
logs as well.

Thanks

"Troy Bruder" <troy_bruder(a)hotmail.com> wrote in message
news:#WFj9kFcJHA.552(a)TK2MSFTNGP06.phx.gbl...
I inadvertently set a HTTP redirect on my Exchange 2007 / IIS7 server on the
Default Website and let it apply to all inherited virtual directories.
Whoopsie. I was able to simply turn off the redirect on MOST of the virtual
directories, but there are a bunch that generate an error when I click Apply
changes: Exadmin, Exchange, Exchweb, Public,

Error: Cannot write configuration file.

Help!! Any ideas for me?

Troy

From: Troy Bruder on 7 Jan 2009 11:06
OK... here's the error when I try to turn off the redirect on the Public:

There was an error while performing this operation.

Details:

Filename: \\?\BackOfficeStorage\our-public-domain-name.com\Public
Folders\web.config

Error: Cannot write configuration file.


Which logs details should i look for?

Troy



<milind.naphade(a)hotmail.com> wrote in message
news:CF4FDB79-F846-4F60-9FEE-5795044C6D25(a)microsoft.com...
> Why don�t you go ahead and paste the bunch of errors that you get while
> applying the changes? you may also want to rename the internal and
> confidential information.
>
> if "Cannot write to configuration file" is the only error message you see
> then probably you are missing on looking at application logs and the IIS
> logs as well.
>
> Thanks
>
> "Troy Bruder" <troy_bruder(a)hotmail.com> wrote in message
> news:#WFj9kFcJHA.552(a)TK2MSFTNGP06.phx.gbl...
> I inadvertently set a HTTP redirect on my Exchange 2007 / IIS7 server on
> the
> Default Website and let it apply to all inherited virtual directories.
> Whoopsie. I was able to simply turn off the redirect on MOST of the
> virtual
> directories, but there are a bunch that generate an error when I click
> Apply
> changes: Exadmin, Exchange, Exchweb, Public,
>
> Error: Cannot write configuration file.
>
> Help!! Any ideas for me?
>
> Troy
>


From: milind.naphade on 7 Jan 2009 11:48
Ok... you can not write to that file because there is no such location
available on the physical drive of you server. If you have the path should
be \\?\BackofficeStorage\<yourADdomainName>\Public Folders. You can edit
this path into the properties of the each virtual directory you have
problems with and then save the changes manually. Restart IIS and see if you
can get your OWA working. As far as I understand it, it must have broken OWA
on your exchange server as well. I was referring to were the w3svc and
HTTPERR logs.

Thanks,


"Troy Bruder" <troy_bruder(a)hotmail.com> wrote in message
news:eGQ7lHOcJHA.1704(a)TK2MSFTNGP05.phx.gbl...
OK... here's the error when I try to turn off the redirect on the Public:

There was an error while performing this operation.

Details:

Filename: \\?\BackOfficeStorage\our-public-domain-name.com\Public
Folders\web.config

Error: Cannot write configuration file.


Which logs details should i look for?

Troy



<milind.naphade(a)hotmail.com> wrote in message
news:CF4FDB79-F846-4F60-9FEE-5795044C6D25(a)microsoft.com...
> Why don�t you go ahead and paste the bunch of errors that you get while
> applying the changes? you may also want to rename the internal and
> confidential information.
>
> if "Cannot write to configuration file" is the only error message you see
> then probably you are missing on looking at application logs and the IIS
> logs as well.
>
> Thanks
>
> "Troy Bruder" <troy_bruder(a)hotmail.com> wrote in message
> news:#WFj9kFcJHA.552(a)TK2MSFTNGP06.phx.gbl...
> I inadvertently set a HTTP redirect on my Exchange 2007 / IIS7 server on
> the
> Default Website and let it apply to all inherited virtual directories.
> Whoopsie. I was able to simply turn off the redirect on MOST of the
> virtual
> directories, but there are a bunch that generate an error when I click
> Apply
> changes: Exadmin, Exchange, Exchweb, Public,
>
> Error: Cannot write configuration file.
>
> Help!! Any ideas for me?
>
> Troy
>

From: Troy Bruder on 7 Jan 2009 12:24
I'm confused... What are you asking me to try? These virtuals were all
setup during a fresh installation of Win2k8 and Exchange 2k7 SP1.


<milind.naphade(a)hotmail.com> wrote in message
news:D88E7023-2095-461F-B61E-89B5D8053A74(a)microsoft.com...
> Ok... you can not write to that file because there is no such location
> available on the physical drive of you server. If you have the path should
> be \\?\BackofficeStorage\<yourADdomainName>\Public Folders. You can edit
> this path into the properties of the each virtual directory you have
> problems with and then save the changes manually. Restart IIS and see if
> you
> can get your OWA working. As far as I understand it, it must have broken
> OWA
> on your exchange server as well. I was referring to were the w3svc and
> HTTPERR logs.
>
> Thanks,
>
>
> "Troy Bruder" <troy_bruder(a)hotmail.com> wrote in message
> news:eGQ7lHOcJHA.1704(a)TK2MSFTNGP05.phx.gbl...
> OK... here's the error when I try to turn off the redirect on the Public:
>
> There was an error while performing this operation.
>
> Details:
>
> Filename: \\?\BackOfficeStorage\our-public-domain-name.com\Public
> Folders\web.config
>
> Error: Cannot write configuration file.
>
>
> Which logs details should i look for?
>
> Troy
>
>
>
> <milind.naphade(a)hotmail.com> wrote in message
> news:CF4FDB79-F846-4F60-9FEE-5795044C6D25(a)microsoft.com...
>> Why don�t you go ahead and paste the bunch of errors that you get while
>> applying the changes? you may also want to rename the internal and
>> confidential information.
>>
>> if "Cannot write to configuration file" is the only error message you see
>> then probably you are missing on looking at application logs and the IIS
>> logs as well.
>>
>> Thanks
>>
>> "Troy Bruder" <troy_bruder(a)hotmail.com> wrote in message
>> news:#WFj9kFcJHA.552(a)TK2MSFTNGP06.phx.gbl...
>> I inadvertently set a HTTP redirect on my Exchange 2007 / IIS7 server on
>> the
>> Default Website and let it apply to all inherited virtual directories.
>> Whoopsie. I was able to simply turn off the redirect on MOST of the
>> virtual
>> directories, but there are a bunch that generate an error when I click
>> Apply
>> changes: Exadmin, Exchange, Exchweb, Public,
>>
>> Error: Cannot write configuration file.
>>
>> Help!! Any ideas for me?
>>
>> Troy
>>
>


 |  Next  |  Last
Pages: 1 2
Prev: The tracking database on <> is not available...
Next: Exchange 2007 error: 451 4.4.2 Connection dropped