This did not happen with Framework 1.0.

When we do a 'Copy Project" of our asp.net application via Visual
Studio 2003 using FrontPage Extensions to our servers that have either
IIS 5 (deployment server) or IIS 6 (test server) with the 1.1
framework, we get the following error:

"An error occurred while copying the project
'http://1.2.3.4/zzz.vbproj'. The web server reported the following
error when attempting to create or open the web project located at the
following URL: 'http://1.2.3.4/zzz' The certificate authority is
invalid or incorrect."

Note that we are deploying to an IP address, not a domain name. Also
note that a Versign certificate is installed on the deployment server
and has been issued to the server's domain name. The test server has a
self-issued certificate.

We believe this to be a bug, or at least inconsistent behavior.

We have discovered two workarounds:

1. On both servers, if we use the Internet Services Manager to require
that a secure channel be used for our entire application (the virtual
directory on down), then we can copy the project over to both servers
without the above error. Then we change the ISM setting back to not
require a secure channel for the entire application after the project
is copied over.

2. If we copy the project to the domain name (www.xyz.com) of the
deployment server instead of the IP address, 1.2.3.4, then we don't
get this error message regardless of the application's SSL settings
within ISM.

Has anyone else run into this problem?

Thanks,
Katie

Hello Katie,

Based on my experience and reserach, I did not find any known issue about
this problem. I'd like to check the following:

1. Make sure the path that was used to issue the certificate is the same as
what he is using to browse a page or open a project.

2. Here are the steps to set up the trust of the certificate on the client
machine.

a. When the message appears, choose View Certificate
b. Click on the Certification path tab in the certificate window
c. Go to the top node in the available paths select it (most likely it will
be in red)
d. Click View Certificate
e. In this new certificate window, choose to install the certificate

3. In addition, could you tell me the detailed steps to reproduce the
problem? I will be glad to check it on my side.

I look forward to your response.

Have a nice day!

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! ¨C www.microsoft.com/security
This posting is provided ¡°as is¡± with no warranties and confers no rights.

HuangTM,

Thank you for your last response. Please note that this problem
exhibits itself when we're sending our application over to our
deployment server using the menu item in Visual Studio called
Project|Copy Project.

Here are the steps to reproduce the problem:
Requirements:
- a deployment server with Framework 1.1 installed and a certificate
issued to it by Verisign or some official agency using its domain name.
- a development machine with Framwork 1.1 installed and Visual Studio
2003 installed.
Steps:
1. Create an ASP.NET project in Visual Studio 2003.
2. In Visual Studio select the project in solution explorer and do a
Project|Copy Project. When the dialog comes up asking for the
destination project folder, type in the IP address of the deployment
server and the project to copy (1.2.3.4/project1). Choose FrontPage and
All Files. Fill in the login information. You'll get the error dialog
box I referred to in my previous note.
3. Now test the first workaround. In Visual Studio, do Project|Copy
Project. When the dialog comes up asking for the destination server,
type in the domain name of the deployment server that the certificate
was issued to and the project to copy (xyz.com/project1). Fill in the
login information. Now the error does not come up and the project can
be copied over successfully.
4. Now test the second workaround. Using Internet Services Manager
(ISM) on the deployment server, select the web site you are deploying
to. Choose Properties. Select the Directory Security tab. Edit the
Secure communications. Check the checkbox for Require secure
channel(SSL). Now repeat Step 2 above. In this scenario, the error
does not come up and the project can be copied successfully to the IP
address of the deployment. The 'Require secure channel(SSL)' setting can
now be turned off on the deployment server if desired.

We did not have this error prior to upgrading from Framework 1.0 to 1.1
on the deployment server. Please note that the reason we deploy to an
IP address rather than the domain name is because this is how we refer
to our server on our Virtual Private Network. If we deploy to the
domain name, the bits/pages are sent over the public internet which we
do not want to do.

Thanks again for your attention to this problem.

Katie





*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!