Solved

COM+ does not keep http session on Windows 2012, but works fine on Windows 8

Posted on 2013-11-27
4
676 Views
Last Modified: 2013-12-13
I have a Windows COM+ component that makes two calls to a WebService, using a gsoap generated proxy. It needs to make both calls in the same http session.

It works fine, but not if the component runs on Windows 2012 Server under Local Service account.

It works as expected on
 - Windows 2012 as the current user
 - Windows 8 as both current user and Local Service account

When I run it on Windows Server 2012 as Local Service (or Network Service) account, however, the second call is made in a different http session.

I have checked many times all settings from COM+ installation to IIS configurations (It is a ASP.NET application that calls the COM), comparing them with the working Windows 8 counterpart, and it is all exactly the same. I can´t see any clue of what may be wrong. As far as I´m concerned it looks like that if I run the COM+ as Local Service it is not able to keep a session cookie.

I´m wondering if someone has any clue of what I may be missing here. Is there any significant Windows 2012 x Windows 8 difference that I should look at, maybe on settings or even on the COM+ implementation?
0
Comment
Question by:cristiantm
  • 2
4 Comments
 
LVL 3

Author Comment

by:cristiantm
ID: 39710926
We´ve found a workaround:

 - Setup the application on IIS to run as a normal user (not application id pool) and load profile set to true;
 - Setup the COM+ to run as the same user

That way, the COM+ is loaded and works fine even if the user is not logged in.

Moreover, we think that the problem is that is something related to wininet x winhttp on the COM+ implementation. We are working on this to check this.

If anyone has another suggestion, I´m still open to hear about it.
0
 
LVL 3

Accepted Solution

by:
cristiantm earned 0 total points
ID: 39716295
We found out the problem. It is really related to using WinInet instead of WinHttp. WinInet is not good for service accounts, creating this kind of problem. Replacing it by WinHttp solved the problem.
0

Featured Post

Webinar: Aligning, Automating, Winning

Join Dan Russo, Senior Manager of Operations Intelligence, for an in-depth discussion on how Dealertrack, leading provider of integrated digital solutions for the automotive industry, transformed their DevOps processes to increase collaboration and move with greater velocity.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Resolve DNS query failed errors for Exchange
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …
The viewer will learn how to successfully download and install the SARDU utility on Windows 8, without downloading adware.

860 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question