Error installing published app

[John]

Hi

When I try to install a published app using a url like
http://www.mydomain.com/publish.htm, it starts the download but then comes
up with the eror given at the end below. I am installing the app on an sbs
2003 (windows 2003 + ISA 2000) server. I suspect ISA 2000 is the problem but
don't know where and how to give proxy credentials in the whole publishing
and installing process. Any help to fix this will be appreciated.

Thanks

Regards
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later
in the log.
* Activation of http://www.mydomain.com/MyApp.application resulted in
exception. Following failure messages were detected:
+ Downloading http://www.mydomain.com/MyApp.application did not succeed.
+ The remote server returned an error: (407) Proxy Authentication
Required.

ERROR DETAILS
Following errors were detected during this operation.
* [06/05/2007 02:38:13]
System.Deployment.Application.DeploymentDownloadEx ception (Unknown subtype)
- Downloading http://www.mydomain.com/MyApp.application did not succeed.
- Source: System.Deployment
- Stack trace:
at
System.Deployment.Application.SystemNetDownloader. DownloadSingleFile(DownloadQueueItem
next)
at System.Deployment.Application.SystemNetDownloader. DownloadAllFiles()
at
System.Deployment.Application.FileDownloader.Downl oad(SubscriptionState
subState)
at
System.Deployment.Application.DownloadManager.Down loadManifestAsRawFile(Uri&
sourceUri, String targetPath, IDownloadNotification notification,
DownloadOptions options, ServerInformation& serverInformation)
at
System.Deployment.Application.DownloadManager.Down loadDeploymentManifestDirectBypass(SubscriptionSto re
subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState,
IDownloadNotification notification, DownloadOptions options,
ServerInformation& serverInformation)
at
System.Deployment.Application.DownloadManager.Down loadDeploymentManifestBypass(SubscriptionStore
subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState,
IDownloadNotification notification, DownloadOptions options)
at
System.Deployment.Application.ApplicationActivator .PerformDeploymentActivation(Uri
activationUri, Boolean isShortcut)
at
System.Deployment.Application.ApplicationActivator .ActivateDeploymentWorker(Object
state)
--- Inner Exception ---
System.Net.WebException
- The remote server returned an error: (407) Proxy Authentication
Required.
- Source: System
- Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at
System.Deployment.Application.SystemNetDownloader. DownloadSingleFile(DownloadQueueItem
next)

[Mr. Arnold]

"John" <Jo**@nospam.infovis.co.ukwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...

Hi

When I try to install a published app using a url like
http://www.mydomain.com/publish.htm, it starts the download but then comes
up with the eror given at the end below. I am installing the app on an sbs
2003 (windows 2003 + ISA 2000) server. I suspect ISA 2000 is the problem
but don't know where and how to give proxy credentials in the whole
publishing and installing process. Any help to fix this will be
appreciated.

I think it comes down to you have to set the *Client* to give the
authentication. I don't know of that *Client* authentication is produced at
an O/S level, ISA client software, or maybe you set the client machine's
browser to give the authentication.

I think a solution is in the links for you or is going to get you in the
ballpark.

BTW, Google is your friend.

http://support.microsoft.com/kb/309814
http://preview.tinyurl.com/3slqb

[John]

Hi

This app was published to an ftp/web site using the Publish Wizard in
VS2005. The app installs fine from url on a standalone PC. So the problem
seems to be ISA2000. What I am not sure is how to provide the
authentication. I can't see anywhere in the publish process to enter the
authentication. On the SBS 2003 (Win 2003/ISA2000) server where I am trying
to install the app there is no firewall client as it is not recommend on a
server. So I am really at a loss how to provide the proxy authentication in
this scenario. Has no one ever published an app and had to install their app
behind ISA 2000?

Thanks

Regards

"Mr. Arnold" <MR. Ar****@Arnold.comwrote in message
news:E4**********************************@microsof t.com...

>
"John" <Jo**@nospam.infovis.co.ukwrote in message
news:%2****************@TK2MSFTNGP04.phx.gbl...

>Hi

When I try to install a published app using a url like
http://www.mydomain.com/publish.htm, it starts the download but then
comes up with the eror given at the end below. I am installing the app on
an sbs 2003 (windows 2003 + ISA 2000) server. I suspect ISA 2000 is the
problem but don't know where and how to give proxy credentials in the
whole publishing and installing process. Any help to fix this will be
appreciated.

I think it comes down to you have to set the *Client* to give the
authentication. I don't know of that *Client* authentication is produced
at an O/S level, ISA client software, or maybe you set the client
machine's browser to give the authentication.

I think a solution is in the links for you or is going to get you in the
ballpark.

BTW, Google is your friend.

http://support.microsoft.com/kb/309814
http://preview.tinyurl.com/3slqb

[Mr. Arnold]

"John" <Jo**@nospam.infovis.co.ukwrote in message
news:e8****************@TK2MSFTNGP03.phx.gbl...

Hi

This app was published to an ftp/web site using the Publish Wizard in
VS2005. The app installs fine from url on a standalone PC. So the problem
seems to be ISA2000. What I am not sure is how to provide the
authentication.

An FTP site is different and a client of any kind may be able to access the
site with no issues. After all, it's FTP that may be possibly open to the
public with Anonymous credentials being used.

I can't see anywhere in the publish process to enter the authentication.

You can't give the authentication the way you seem to think that you can do
it.

If it's there you would have seen it. It's not there and I don't think you
can give it the way you want, otherwise, you would have seen the solution by
now.

>On the SBS 2003 (Win 2003/ISA2000) server where I am trying to install the
app there is no firewall client as it is not recommend on a server.

I think you are off base here about the client. You just said that the
application installed fine from a pc to the FTP site, which I'll take it
you're trying to do the same to install to this WEB site for HTTP.

That machine with the browser, some kind of ISA client software possibly on
that machine or the O/S on the machine must give the Authentication to the
ISA server.

So I am really at a loss how to provide the proxy authentication in this
scenario. Has no one ever published an app and had to install their app
behind ISA 2000?

If it were me, I would have ended it long ago and just called MS Tech
Support (paid for support if need be), I would be done with it and I would
have moved on.

Maybe, you need to do the same.

[John]

Hi

Just for clarification;

1. Application gets published from vs2005 fine.

2. The published application gets installed fine from the url on a
standalone PC.

3. Application does not gets installed from the url on the sbs server
(win2003+ isa2000). Raising the suspicion specially with the proxy
authentication error that it is ISA2000.

I asked here as it seems to be a fairly standard set-up and I wondered if
someone else had a similar experience.

Thanks

Regards
"Mr. Arnold" <MR. Ar****@Arnold.comwrote in message
news:3F**********************************@microsof t.com...

>
"John" <Jo**@nospam.infovis.co.ukwrote in message
news:e8****************@TK2MSFTNGP03.phx.gbl...

>Hi

This app was published to an ftp/web site using the Publish Wizard in
VS2005. The app installs fine from url on a standalone PC. So the problem
seems to be ISA2000. What I am not sure is how to provide the
authentication.

An FTP site is different and a client of any kind may be able to access
the site with no issues. After all, it's FTP that may be possibly open to
the public with Anonymous credentials being used.

>I can't see anywhere in the publish process to enter the authentication.

You can't give the authentication the way you seem to think that you can
do it.

If it's there you would have seen it. It's not there and I don't think you
can give it the way you want, otherwise, you would have seen the solution
by now.

>>On the SBS 2003 (Win 2003/ISA2000) server where I am trying to install the
app there is no firewall client as it is not recommend on a server.

I think you are off base here about the client. You just said that the
application installed fine from a pc to the FTP site, which I'll take it
you're trying to do the same to install to this WEB site for HTTP.

That machine with the browser, some kind of ISA client software possibly
on that machine or the O/S on the machine must give the Authentication to
the ISA server.

>So I am really at a loss how to provide the proxy authentication in this
scenario. Has no one ever published an app and had to install their app
behind ISA 2000?

If it were me, I would have ended it long ago and just called MS Tech
Support (paid for support if need be), I would be done with it and I would
have moved on.

Maybe, you need to do the same.

[Mr. Arnold]

"John" <Jo**@nospam.infovis.co.ukwrote in message
news:eh******************@TK2MSFTNGP02.phx.gbl...

Hi

Just for clarification;

1. Application gets published from vs2005 fine.

The last time I used VS 2005 to publish, I published to a local folder on
the workstation and copied the files to the Web server.

>
2. The published application gets installed fine from the url on a
standalone PC.

The stand alone PC and a Web server or ISA are two different things.

>
3. Application does not gets installed from the url on the sbs server
(win2003+ isa2000). Raising the suspicion specially with the proxy
authentication error that it is ISA2000.

Agreed, then why don't you turn the authentication off, install the app, and
turn the authentication back on, even if you have to take the Web server or
ISA offline? If the authentication is not active during the time of the
install, how is it going to ask for authentication?

>
I asked here as it seems to be a fairly standard set-up and I wondered if
someone else had a similar experience.

You may have someone post with a solution, but that seems questionable. And
sometimes, you simply need to take matters into your own hands.