authentication stopped after installing 2.0 Framework

[Jason]

Hi,

I have developed many office addins using Vb.Net 2003 and the V1.1
Framework. Each addin connects to a web Service passing the default
credentials and has been working fine for the last year. A number of users
have recently installed VS2005 which has caused the addin to stop
functioning.

What I have found is that the authentication to the web service is no longer
taking place and the client is receiving a 403 error. This problem only
occurs when the code runs in the addin controlled by office. It does not
happen when run inside a regular Windows executable. Can you tell me why
installing the new framework would cause this issue?? Has office been updated
to use the V2.0 framework so now my V1.1 app does not function?

Any help would be greatly appreciated..

Thanks
Jason

 

[Thomas Möller]

Hi Jason,

I have developed many office addins using Vb.Net 2003 and the V1.1
Framework. Each addin connects to a web Service passing the default
credentials and has been working fine for the last year. A number of
users have recently installed VS2005 which has caused the addin to
stop functioning.

What I have found is that the authentication to the web service is no
longer taking place and the client is receiving a 403 error. This
problem only occurs when the code runs in the addin controlled by
office. It does not happen when run inside a regular Windows
executable. Can you tell me why installing the new framework would
cause this issue?? Has office been updated to use the V2.0 framework
so now my V1.1 app does not function?

Any help would be greatly appreciated..

take a look here:
http://support.microsoft.com/kb/908002/

HTH

 

[Jason]

Thanks but this is a different issue. The addin was built with VS2003, V1.1
of the framework. The addin initializaes and works fine, it just can't
connect to the web service because the service is expecting authentication
and since V2.0 Framework was installed the authentication does not work.

Jason

 

[Peter Huang [MSFT]]

Hi

I assume you have tried Thomas's suggestion and that did not work for you.
Commonly, after we installed .NET 2.0 Framework, the Addin will load .NET
framework 2.0.
Based on my research, I did not find a known issue there .NET 2.0 will
prevent the App from accessing Web Service.
So far I assume you did not do any change at the server side(where the
WebService located).
We can have some tests.
1. We can try to force the Addin to load the .NET 1.1 using app.config
<configuration>
<startup>
<supportedRuntime version="v1.1.4322"/>
<supportedRuntime version="v1.0.3705"/>
</startup>
</configuration>

Because we can not specified config for dll, we need to set for the exe.
e.g. you have using Word Addin, so we can save the xml above as
winword.exe.config and put it into the dir where the winword.exe is.

2. Try to build a new Winform application and access to the WebService
using the .NET 2.0 to see if that works.

If you are using IIS, please check the KB below.
IIS Status Codes
http://support.microsoft.com/?id=318380
We will find that there are many 403 error with different sub code for
different reasons.
What is the sub code for the 403 error? You can check the IIS log per the
KB above.

Please perform the tests and let me know the result.

Best regards,

Peter Huang

Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Jason]

Peter,

Thanks for the information.. Creating/Updating the config files of the
office applications worked great! My applications are now functioning as they
used to. Thanks!!!!

Now, I am getting ready to Port these apps to VS2005 and I am a little
concerned that the web service authentication will not function from within
an Office Addin. Was this a simple mis-match between VS2003 and V2.0
Framework? or do I need to connect to the web service with different
parameters to do an automatic authentication? I am VERY concerned that with
all the latest patches you have removed the ability for automatic
authentication to take place. Can you confirm when this should work with
VS2005 and V2.0 framework???

Again, Many Thanks!!!
Jason

 

[Peter Huang [MSFT]]

Hi Jason,

So far it is hard to say what is the cause.
One possible cause you may try to check is that when we access to a web
service.
We will add reference to the web service, for .NET 2.0 IDE and .NET 1.1
IDE, the generated web service proxy code may differ.

Also have you tried the other test that build a new winform application in
NET 2.0 IDE?
What is the IIS detailed return code. e.g. 403.3 or something else.

And we have CAS in .NET application, but for .NET 1.1 and 2.0 we have
different set of Security setting.
So I think you may try to set the CAS for the .NET 2.0 too as you do with
NET 1.1.
Simply, we can just disable the CAS security by using the command line
below.
caspol -s off

NOTE: please run the caspol tool in the 2.0 dir.
<windows>\Microsoft.NET\Framework\v2.0.50727

I look forward to hearing from you!

Best regards,

Peter Huang

Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Jason]

Thanks for the suggestion peter. I will try that next month when I begin
porting the application to the 2.0 Framework..

Jason

 

[Peter Huang [MSFT]]

Hi

Thanks for your reponse!
When you have concern, please feel free to post here.

Best regards,

Peter Huang

Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.