473,322 Members | 1,671 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,322 software developers and data experts.

VS2008 creates a 2nd endpoint when actualising a web reference

Hello out there,

I changed an existing and good working webservice from an wsHttpBinding
to an NetTcpBinding.
This is working (after trying some time) and has real a better performance!

But one thing is strange: when I'm now actualising the web reference
from within VS2008, VS2008
creates a 2nd endpoint config in my app.conf.
The endpoint is exactly the same as the existing but the name and
bindingConfiguration have the suffix "1" . Additional VS2008
creates this entry:

<identity>
<userPrincipalName value="Domain\Username" />
</identity>

Where Domain\Username is my username in the domain.
The client does not run with these informations, I have to remove them
manually.
What's wrong with VS2008?
Thank you,
Frank

Jul 23 '08 #1
8 2112
Hi Frank,

From your description, you are developing an WCF service and a client
through VS 2008. The service used to use wshttpbinding, and when you switch
it to netTcpBinding and regenerate the service reference at client, you
found the client generate two configuration section for the service
endpoint , correct?

Based on my experience, such behavior might occur at the following
situation:

* you have an WCF service endpoint using certain configuration(binding and
behavior ...)

* you change its binding or other settings

* without remove the original client service reference(proxy class) in
client project, you directly update the reference, it might keep the
original reference setting and generate a new client endpoint entry.

Therefore for this issue, I suggest you always first remove the existing
client-side service reference(in solution explorer), this will make the IDE
remove the proxy class and also clear the app.config file. Then, add the
"service reference" again in the project.

For the second issue you mentioned:

=====================
but the name and
bindingConfiguration have the suffix "1" . Additional VS2008
creates this entry:

<identity>
<userPrincipalName value="Domain\Username" />
</identity>
=========================

based on the document you can see that this element <identityis used to
set a predefined identiy for the expected server-side service(not for
client):

#<identity>
http://msdn.microsoft.com/en-us/library/ms731721.aspx

Therefore, it is generated by the IDE according to the server-side
service's identity. By default when using netTCPBinding, WCF service
endpoint will use windows authentication and if you are using the VS IDE
test server(instead of IIS), the service's running process identity is the
current logon user(that should be the "domain\username" for your case. You
can manually specify another expected identity(but the default one is ok).

Or if you do not need security feature for the current case, you can turn
it off in your service configuration( in the NetTcpBinding configuration):

For example:
==============================
<system.serviceModel>

<services>
<service behaviorConfiguration="WCFIDESvr.TestServiceBehavi or"
.............

<endpoint address="net.Tcp://localhost:8989/TestService"
binding="netTcpBinding"
bindingConfiguration="TSBinding"
contract="WCFIDESvr.ITestService">
</endpoint>

......................
</service>
</services>

<bindings>
<netTcpBinding>
<binding name="TSBinding" >
<!-- i turn off the security here -->
<security mode="None" >
<transport clientCredentialType="None"/>
<message clientCredentialType="None"/>
</security>

</binding>
</netTcpBinding>
</bindings>
================================

You can get more about the WCF configuration schema info here:

#Windows Communication Foundation Configuration Schema
http://msdn.microsoft.com/en-us/library/ms731734.aspx

and for WCF security programming:

#Windows Communication Foundation Security
http://msdn.microsoft.com/en-us/library/ms732362.aspx

If there is anything unclear, please feel free to post here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Date: Wed, 23 Jul 2008 19:52:42 +0200
From: Frank Hauptlorenz <ec***********@nospam.nospam>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
Subject: VS2008 creates a 2nd endpoint when actualising a web reference

Hello out there,

I changed an existing and good working webservice from an wsHttpBinding
to an NetTcpBinding.
This is working (after trying some time) and has real a better performance!

But one thing is strange: when I'm now actualising the web reference
from within VS2008, VS2008
creates a 2nd endpoint config in my app.conf.
The endpoint is exactly the same as the existing but the name and
bindingConfiguration have the suffix "1" . Additional VS2008
creates this entry:

<identity>
<userPrincipalName value="Domain\Username" />
</identity>

Where Domain\Username is my username in the domain.
The client does not run with these informations, I have to remove them
manually.
What's wrong with VS2008?
Thank you,
Frank
Jul 24 '08 #2
Hi Steven,

okay I will try to remove and add the service reference again.
As for the identity: I think I want to use transport security.
So the question is:
If I remove the

<identity>
<userPrincipalName value="Domain\Username" />
</identity>

section the client uses my user name anyway, or?
More problematic If I leave this in, I can't connect to the service
(SSPI-Failure).
Frank

Steven Cheng [MSFT] schrieb:
Hi Frank,

From your description, you are developing an WCF service and a client
through VS 2008. The service used to use wshttpbinding, and when you switch
it to netTcpBinding and regenerate the service reference at client, you
found the client generate two configuration section for the service
endpoint , correct?

Based on my experience, such behavior might occur at the following
situation:

* you have an WCF service endpoint using certain configuration(binding and
behavior ...)

* you change its binding or other settings

* without remove the original client service reference(proxy class) in
client project, you directly update the reference, it might keep the
original reference setting and generate a new client endpoint entry.

Therefore for this issue, I suggest you always first remove the existing
client-side service reference(in solution explorer), this will make the IDE
remove the proxy class and also clear the app.config file. Then, add the
"service reference" again in the project.

For the second issue you mentioned:

=====================
but the name and
bindingConfiguration have the suffix "1" . Additional VS2008
creates this entry:

<identity>
<userPrincipalName value="Domain\Username" />
</identity>
=========================

based on the document you can see that this element <identityis used to
set a predefined identiy for the expected server-side service(not for
client):

#<identity>
http://msdn.microsoft.com/en-us/library/ms731721.aspx

Therefore, it is generated by the IDE according to the server-side
service's identity. By default when using netTCPBinding, WCF service
endpoint will use windows authentication and if you are using the VS IDE
test server(instead of IIS), the service's running process identity is the
current logon user(that should be the "domain\username" for your case. You
can manually specify another expected identity(but the default one is ok).

Or if you do not need security feature for the current case, you can turn
it off in your service configuration( in the NetTcpBinding configuration):

For example:
==============================
<system.serviceModel>

<services>
<service behaviorConfiguration="WCFIDESvr.TestServiceBehavi or"
.............

<endpoint address="net.Tcp://localhost:8989/TestService"
binding="netTcpBinding"
bindingConfiguration="TSBinding"
contract="WCFIDESvr.ITestService">
</endpoint>

......................
</service>
</services>

<bindings>
<netTcpBinding>
<binding name="TSBinding" >
<!-- i turn off the security here -->
<security mode="None" >
<transport clientCredentialType="None"/>
<message clientCredentialType="None"/>
</security>

</binding>
</netTcpBinding>
</bindings>
================================

You can get more about the WCF configuration schema info here:

#Windows Communication Foundation Configuration Schema
http://msdn.microsoft.com/en-us/library/ms731734.aspx

and for WCF security programming:

#Windows Communication Foundation Security
http://msdn.microsoft.com/en-us/library/ms732362.aspx

If there is anything unclear, please feel free to post here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Date: Wed, 23 Jul 2008 19:52:42 +0200
From: Frank Hauptlorenz <ec***********@nospam.nospam>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
Subject: VS2008 creates a 2nd endpoint when actualising a web reference

Hello out there,

I changed an existing and good working webservice from an wsHttpBinding
to an NetTcpBinding.
This is working (after trying some time) and has real a better performance!

But one thing is strange: when I'm now actualising the web reference
from within VS2008, VS2008
creates a 2nd endpoint config in my app.conf.
The endpoint is exactly the same as the existing but the name and
bindingConfiguration have the suffix "1" . Additional VS2008
creates this entry:

<identity>
<userPrincipalName value="Domain\Username" />
</identity>

Where Domain\Username is my username in the domain.
The client does not run with these informations, I have to remove them
manually.
What's wrong with VS2008?
Thank you,
Frank
Jul 25 '08 #3
Hi Steven,

a little follow up:

1. Removing and adding the service had no effect. The same issue happens
again.
2. The issue has exactly to do with the identity segment. If I leave it
in, the actualizing is working.
If I remove it and then actualise, VS2008 will create me a second client
entry.

I do still not know, for what I need the identy segment in the client.
(PS: I switched to security mode "none" now, this is working)

Thank you,
Frank

Frank Hauptlorenz schrieb:
Hi Steven,

okay I will try to remove and add the service reference again.
As for the identity: I think I want to use transport security.
So the question is:
If I remove the

<identity>
<userPrincipalName value="Domain\Username" />
</identity>

section the client uses my user name anyway, or?
More problematic If I leave this in, I can't connect to the service
(SSPI-Failure).
Frank

Steven Cheng [MSFT] schrieb:
>Hi Frank,

From your description, you are developing an WCF service and a client
through VS 2008. The service used to use wshttpbinding, and when you
switch it to netTcpBinding and regenerate the service reference at
client, you found the client generate two configuration section for
the service endpoint , correct?

Based on my experience, such behavior might occur at the following
situation:

* you have an WCF service endpoint using certain
configuration(binding and behavior ...)

* you change its binding or other settings

* without remove the original client service reference(proxy class)
in client project, you directly update the reference, it might keep
the original reference setting and generate a new client endpoint
entry.
Therefore for this issue, I suggest you always first remove the
existing client-side service reference(in solution explorer), this
will make the IDE remove the proxy class and also clear the
app.config file. Then, add the "service reference" again in the
project.

For the second issue you mentioned:

=====================
but the name and bindingConfiguration have the suffix "1" .
Additional VS2008
creates this entry:

<identity>
<userPrincipalName value="Domain\Username" />
</identity>
=========================

based on the document you can see that this element <identityis
used to set a predefined identiy for the expected server-side
service(not for client):

#<identity>
http://msdn.microsoft.com/en-us/library/ms731721.aspx

Therefore, it is generated by the IDE according to the server-side
service's identity. By default when using netTCPBinding, WCF service
endpoint will use windows authentication and if you are using the VS
IDE test server(instead of IIS), the service's running process
identity is the current logon user(that should be the
"domain\username" for your case. You can manually specify another
expected identity(but the default one is ok).
Or if you do not need security feature for the current case, you can
turn it off in your service configuration( in the NetTcpBinding
configuration):

For example:
==============================
<system.serviceModel>
<services>
<service
behaviorConfiguration="WCFIDESvr.TestServiceBehav ior"
.............
<endpoint
address="net.Tcp://localhost:8989/TestService"
binding="netTcpBinding"
bindingConfiguration="TSBinding"
contract="WCFIDESvr.ITestService">
</endpoint>
......................
</service>
</services>

<bindings>
<netTcpBinding>
<binding name="TSBinding" >
<!-- i turn off the security here -->
<security mode="None" >
<transport clientCredentialType="None"/>
<message clientCredentialType="None"/>
</security>
</binding>
</netTcpBinding>
</bindings>
================================

You can get more about the WCF configuration schema info here:

#Windows Communication Foundation Configuration Schema
http://msdn.microsoft.com/en-us/library/ms731734.aspx

and for WCF security programming:

#Windows Communication Foundation Security
http://msdn.microsoft.com/en-us/library/ms732362.aspx

If there is anything unclear, please feel free to post here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments
and suggestions about how we can improve the support we provide to
you. Please feel free to let my manager know what you think of the
level of service provided. You can send feedback directly to my
manager at: ms****@microsoft.com.

================================================= =
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif

ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent
issues where an initial response from the community or a Microsoft
Support Engineer within 1 business day is acceptable. Please note
that each follow up response may take approximately 2 business days
as the support professional working with you may need further
investigation to reach the most efficient resolution. The offering is
not appropriate for situations that require urgent, real-time or
phone-based interactions or complex project analysis and dump
analysis issues. Issues of this nature are best handled working with
a dedicated Microsoft Support Engineer by contacting Microsoft
Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================= =
This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
Date: Wed, 23 Jul 2008 19:52:42 +0200
From: Frank Hauptlorenz <ec***********@nospam.nospam>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
Subject: VS2008 creates a 2nd endpoint when actualising a web reference

Hello out there,

I changed an existing and good working webservice from an
wsHttpBinding to an NetTcpBinding.
This is working (after trying some time) and has real a better
performance!

But one thing is strange: when I'm now actualising the web reference
from within VS2008, VS2008
creates a 2nd endpoint config in my app.conf.
The endpoint is exactly the same as the existing but the name and
bindingConfiguration have the suffix "1" . Additional VS2008
creates this entry:

<identity>
<userPrincipalName value="Domain\Username" />
</identity>

Where Domain\Username is my username in the domain.
The client does not run with these informations, I have to remove
them manually.
What's wrong with VS2008?
Thank you,
Frank
Jul 25 '08 #4
Frank,

When using default setup with wsHttpBinding, the authentication will be done
via NTLM or SspiNegotiate.
The client, when generating a proxy will (most of the time) generate an
entry like:
<identity>
<userPrincipalName va************@yourdomain.com />
</identity>

This is due to Kerberos and how clients reference the target they want to
access. A kerberos target can be referenced by a UPN (User Principal Name)
which is what you see above, or by an SPN (Service Principal Name) in the
format of:
<identity>
<servicePrincipalName value="http/yourhostname" />
</identity>

The SPN free the client from the knowing the account being used on the
backend and allows the target to be "moved" or "configured" with no impact
on the client side.

Now, going back to your issue, you're most probably suffering from the fact
that your client and your service are probably on the same box. And since I
did not mention NTLM here, its probably an option (in your specific case) to
make the client try to connect via NTLM like this:
<identity>
<servicePrincipalName />
</identity>

What this means is that a client without the value attribute will
automatically use NTLM when authenticating to the service.
Give it a try, and let us know how it goes.

cheers,
Tiago Halm

"Frank Hauptlorenz" <ec***********@nospam.nospamwrote in message
news:eX**************@TK2MSFTNGP04.phx.gbl...
Hi Steven,

a little follow up:

1. Removing and adding the service had no effect. The same issue happens
again.
2. The issue has exactly to do with the identity segment. If I leave it
in, the actualizing is working.
If I remove it and then actualise, VS2008 will create me a second client
entry.

I do still not know, for what I need the identy segment in the client.
(PS: I switched to security mode "none" now, this is working)

Thank you,
Frank

Frank Hauptlorenz schrieb:
>Hi Steven,

okay I will try to remove and add the service reference again.
As for the identity: I think I want to use transport security.
So the question is:
If I remove the

<identity>
<userPrincipalName value="Domain\Username" />
</identity>

section the client uses my user name anyway, or?
More problematic If I leave this in, I can't connect to the service
(SSPI-Failure).
Frank

Steven Cheng [MSFT] schrieb:
>>Hi Frank,

From your description, you are developing an WCF service and a client
through VS 2008. The service used to use wshttpbinding, and when you
switch it to netTcpBinding and regenerate the service reference at
client, you found the client generate two configuration section for the
service endpoint , correct?

Based on my experience, such behavior might occur at the following
situation:

* you have an WCF service endpoint using certain configuration(binding
and behavior ...)

* you change its binding or other settings

* without remove the original client service reference(proxy class) in
client project, you directly update the reference, it might keep the
original reference setting and generate a new client endpoint entry.
Therefore for this issue, I suggest you always first remove the existing
client-side service reference(in solution explorer), this will make the
IDE remove the proxy class and also clear the app.config file. Then,
add the "service reference" again in the project.

For the second issue you mentioned:

=====================
but the name and bindingConfiguration have the suffix "1" . Additional
VS2008
creates this entry:

<identity>
<userPrincipalName value="Domain\Username" />
</identity>
=========================

based on the document you can see that this element <identityis used
to set a predefined identiy for the expected server-side service(not for
client):

#<identity>
http://msdn.microsoft.com/en-us/library/ms731721.aspx

Therefore, it is generated by the IDE according to the server-side
service's identity. By default when using netTCPBinding, WCF service
endpoint will use windows authentication and if you are using the VS IDE
test server(instead of IIS), the service's running process identity is
the current logon user(that should be the "domain\username" for your
case. You can manually specify another expected identity(but the
default one is ok).
Or if you do not need security feature for the current case, you can
turn it off in your service configuration( in the NetTcpBinding
configuration):

For example:
==============================
<system.serviceModel>
<services>
<service
behaviorConfiguration="WCFIDESvr.TestServiceBeha vior"
.............
<endpoint
address="net.Tcp://localhost:8989/TestService" binding="netTcpBinding"
bindingConfiguration="TSBinding"
contract="WCFIDESvr.ITestService">
</endpoint>
......................
</service>
</services>

<bindings>
<netTcpBinding>
<binding name="TSBinding" >
<!-- i turn off the security here -->
<security mode="None" >
<transport clientCredentialType="None"/>
<message clientCredentialType="None"/>
</security>
</binding>
</netTcpBinding>
</bindings>
================================

You can get more about the WCF configuration schema info here:

#Windows Communication Foundation Configuration Schema
http://msdn.microsoft.com/en-us/library/ms731734.aspx

and for WCF security programming:

#Windows Communication Foundation Security
http://msdn.microsoft.com/en-us/library/ms732362.aspx

If there is anything unclear, please feel free to post here.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments
and suggestions about how we can improve the support we provide to you.
Please feel free to let my manager know what you think of the level of
service provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

================================================ ==
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent
issues where an initial response from the community or a Microsoft
Support Engineer within 1 business day is acceptable. Please note that
each follow up response may take approximately 2 business days as the
support professional working with you may need further investigation to
reach the most efficient resolution. The offering is not appropriate for
situations that require urgent, real-time or phone-based interactions or
complex project analysis and dump analysis issues. Issues of this nature
are best handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================ ==
This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
Date: Wed, 23 Jul 2008 19:52:42 +0200
From: Frank Hauptlorenz <ec***********@nospam.nospam>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
Subject: VS2008 creates a 2nd endpoint when actualising a web reference

Hello out there,

I changed an existing and good working webservice from an wsHttpBinding
to an NetTcpBinding.
This is working (after trying some time) and has real a better
performance!

But one thing is strange: when I'm now actualising the web reference
from within VS2008, VS2008
creates a 2nd endpoint config in my app.conf.
The endpoint is exactly the same as the existing but the name and
bindingConfiguration have the suffix "1" . Additional VS2008
creates this entry:

<identity>
<userPrincipalName value="Domain\Username" />
</identity>

Where Domain\Username is my username in the domain.
The client does not run with these informations, I have to remove them
manually.
What's wrong with VS2008?
Thank you,
Frank

Jul 26 '08 #5
Hi Frank,

Thanks for your followup.

So currently, what's the error message/exception you got, is it an
exception about "security negotiate"? Seems the VS will generate different
client proxy class based on different service credential setting. Would
you let me know what's your WCF service's current running process identity?
Is it an system account(such as network service ) or a normal domain user
account?

here are some threads and article mentioned how the service process idneity
will affect the client-side's negotiate with server-side(when using windows
authentication):

#Moving Services and User Principals
http://blogs.msdn.com/drnick/archive...s-and-user-pri
ncipals.aspx

#serPrincipalName element generated in client config
http://forums.microsoft.com/MSDN/Sho...04622&SiteID=1

I suggest you also try Tiago's suggestion. If there is any other findings
or questions, please feel free to post here.

Sincerely,

Steven Cheng
Microsoft MSDN Online Support Lead

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Date: Fri, 25 Jul 2008 10:37:31 +0200
From: Frank Hauptlorenz <ec***********@nospam.nospam>
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
Subject: Re: VS2008 creates a 2nd endpoint when actualising a web reference
References: <#R**************@TK2MSFTNGP04.phx.gbl>
<qR**************@TK2MSFTNGHUB02.phx.gbl<#EEL9hh7I HA.5024

Hi Steven,

a little follow up:

1. Removing and adding the service had no effect. The same issue happens
again.
2. The issue has exactly to do with the identity segment. If I leave it
in, the actualizing is working.
If I remove it and then actualise, VS2008 will create me a second client
entry.

I do still not know, for what I need the identy segment in the client.
(PS: I switched to security mode "none" now, this is working)

Thank you,
Frank
Jul 28 '08 #6
Hi Frank,

Have you got any progress on this issue or have you tried something
mentioned in previous messages?

If there is still anything unclear or need help, please feel free to post
here.

Sincerely,

Steven Cheng
Microsoft MSDN Online Support Lead

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------

From: st*****@online.microsoft.com (Steven Cheng [MSFT])
Organization: Microsoft
Date: Mon, 28 Jul 2008 02:46:03 GMT
Subject: Re: VS2008 creates a 2nd endpoint when actualising a web reference
Hi Frank,

Thanks for your followup.

So currently, what's the error message/exception you got, is it an
exception about "security negotiate"? Seems the VS will generate different
client proxy class based on different service credential setting. Would
you let me know what's your WCF service's current running process identity?
Is it an system account(such as network service ) or a normal domain user
account?

here are some threads and article mentioned how the service process idneity
will affect the client-side's negotiate with server-side(when using windows
authentication):

#Moving Services and User Principals
http://blogs.msdn.com/drnick/archive...s-and-user-pri
ncipals.aspx

#serPrincipalName element generated in client config
http://forums.microsoft.com/MSDN/Sho...04622&SiteID=1

I suggest you also try Tiago's suggestion. If there is any other findings
or questions, please feel free to post here.

Sincerely,

Steven Cheng
Microsoft MSDN Online Support Lead

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Jul 30 '08 #7
Hi Steven, Tiago,

thank you both for your suggestions. I will try them later, I will now
fill the WCF services with life.
If this is finished and the project goes to the implementation state, I
will specify the correct endpoint settings.

Thank you,
Frank
Steven Cheng [MSFT] schrieb:
Hi Frank,

Have you got any progress on this issue or have you tried something
mentioned in previous messages?

If there is still anything unclear or need help, please feel free to post
here.

Sincerely,

Steven Cheng
Microsoft MSDN Online Support Lead

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------

From: st*****@online.microsoft.com (Steven Cheng [MSFT])
Organization: Microsoft
Date: Mon, 28 Jul 2008 02:46:03 GMT
Subject: Re: VS2008 creates a 2nd endpoint when actualising a web reference
Hi Frank,

Thanks for your followup.

So currently, what's the error message/exception you got, is it an
exception about "security negotiate"? Seems the VS will generate different
client proxy class based on different service credential setting. Would
you let me know what's your WCF service's current running process identity?
Is it an system account(such as network service ) or a normal domain user
account?

here are some threads and article mentioned how the service process idneity
will affect the client-side's negotiate with server-side(when using windows
authentication):

#Moving Services and User Principals
http://blogs.msdn.com/drnick/archive...s-and-user-pri
ncipals.aspx

#serPrincipalName element generated in client config
http://forums.microsoft.com/MSDN/Sho...04622&SiteID=1

I suggest you also try Tiago's suggestion. If there is any other findings
or questions, please feel free to post here.

Sincerely,

Steven Cheng
Microsoft MSDN Online Support Lead

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Aug 4 '08 #8
Thanks for your reply Frank,

No problem. If you need any further help later, please feel free to post
here.

Sincerely,

Steven Cheng
Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
Date: Mon, 04 Aug 2008 09:55:02 +0200
Subject: Re: VS2008 creates a 2nd endpoint when actualising a web reference
Hi Steven, Tiago,

thank you both for your suggestions. I will try them later, I will now
fill the WCF services with life.
If this is finished and the project goes to the implementation state, I
will specify the correct endpoint settings.

Thank you,
Frank
Steven Cheng [MSFT] schrieb:
Hi Frank,

Have you got any progress on this issue or have you tried something
mentioned in previous messages?

If there is still anything unclear or need help, please feel free to post
here.

Sincerely,

Steven Cheng
Microsoft MSDN Online Support Lead

Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you.
Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
ms****@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.
=
Aug 4 '08 #9

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

3
by: Andy | last post by:
If I use Visual Studio.Net 2003 to generate "web references" for clients using either sproxy.exe (for C++) client or wsdl.exe (for C#) clients, the web service endpoint gets "baked" into the...
0
by: tovbinm | last post by:
I failed to make a Web Reference to SQL 2005 HTTP endpoint for stored procedure, It works fine only on locahost. Whan i surf or make a web reference in VS2005 to http://locahost/TestWS?wsdl - i...
0
by: rkprasad | last post by:
I am able to create BASIC-CLEAR-INTEGRATED sql http endpoint and consume it on a LAN. But i am not able to consume the created endpoint on inter domain network. If i create endpoint on a server...
8
by: Joe Withawk | last post by:
I have a solution consisting of a c# project as win application and a c++ project as classlibrary. Both are .net 2.0 The classlibrary handles some loading of quicktime movies, but that should not...
4
by: K Viltersten | last post by:
We have a project working well today and it's developed on VS2005. Since we're planing to switch to VS2008 in a soon future, i've been trying to move the project to VS2008 Express (Web...
3
by: Lance Wynn | last post by:
Hello, I am receiving this error when trying to instantiate a webservice component. I have 2 development machines, both are XP sp2 with VS 2008 installed. On one machine, the code works fine. On...
4
by: eschneider | last post by:
I get the following error when trying to browse the .asmx. I get the same thing when trying to add a reference. using .NET 2.0 There is no error message. Any ideas? Thanks,
16
by: Harry Simpson | last post by:
I've been away from ASPNET - I open up a new Web app in VS2008 and go into properties and select to use IIS instead of the personal web server. Then I run in debug mode and it says I have to set...
3
by: Jeff | last post by:
hi I'm wondering how to open a web browser window in VS2008. I've created a simple windows Live Agent and just want to test it in the VS2008 before I deploy it... any ideas how to open a...
0
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
1
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: jfyes | last post by:
As a hardware engineer, after seeing that CEIWEI recently released a new tool for Modbus RTU Over TCP/UDP filtering and monitoring, I actively went to its official website to take a look. It turned...
0
by: ArrayDB | last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
1
by: PapaRatzi | last post by:
Hello, I am teaching myself MS Access forms design and Visual Basic. I've created a table to capture a list of Top 30 singles and forms to capture new entries. The final step is a form (unbound)...
1
by: CloudSolutions | last post by:
Introduction: For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
1
by: Defcon1945 | last post by:
I'm trying to learn Python using Pycharm but import shutil doesn't work
1
by: Shællîpôpï 09 | last post by:
If u are using a keypad phone, how do u turn on JavaScript, to access features like WhatsApp, Facebook, Instagram....
0
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome former...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.