Solved

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

Posted on 2013-11-27
4
695 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 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

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

When you start your Windows 10 PC and got an "Operating system not found" error or just saw  "Auto repair for startup" or a blinking cursor with black screen. A loop for Auto repair will start but fix nothing.  You will be panic as there are no back…
A procedure for exporting installed hotfix details of remote computers using powershell
In this Micro Tutorial viewers will learn how to use Windows Server Backup to create full image of their system. Tutorial shows how to install Windows Server Backup Feature on Windows 2012R2 and how to configure scheduled Bare Metal Recovery backup.…
In this Micro Tutorial viewers will learn how to restore single file or folder from Bare Metal backup image of their system. Tutorial shows how to restore files and folders from system backup. Often it is not needed to restore entire system when onl…

705 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