Home› Analyst Portal

Trouble with Fix included in v7.3 -- AppPool ID making updates to Work Items

David_DarlingDavid_Darling Customer IT Monkey ✭
in Analyst Portal

Hi, v7.3 (SCSM 2012 R2) of the Portal included the following fix: “PR58784 - When using Windows Authentication and the Data Access Service is restarted the Service Account is making all updates”.

 

However, we have installed v7.3 and have found that this fix does not work for us at all.  Here’s a scenario… we open the portal (via windows authentication), a new SCSM SDK connection is established (we verify this), then we restart the “System Center Data Access Service” on the portal server, and check to ensure that the SDK session for that same user has in fact been disconnected (again, we verify), and then finally we have the user perform some action (open a Work Item, make an update to a Work Item, create a new Work Item, etc.) and in all cases, the SDK session is not re-established.

 

We were actually given a POC patch for this issue when we were on version 7.1, and tested it at that time quite extensively – and it worked flawlessly, so we know what to expect.  Which was the following:

 

  • When a user’s SDK session had become disconnected, and then they attempted to open a Work Item, they were presented with the error “An error occurred while processing your request.  The connection to Service Manager is stale and has been refreshed please reattempt your request.”.  At that point, the users SDK session was re-established.

  • If the user happened to be already in a Work Item when their SDK session became disconnected and then made an update and clicked APPLY, the user was presented with the error “The connection to Service Manager is stale and has been refreshed please reattempt your request”, and upon clicking OK their SDK session would be re-established and could proceed.

  • If the user happened to be already in a Work Item when their SDK session became disconnected and then made an update and clicked SAVE, the user was not presented with any error message, but the SDK session was re-established (although we noticed in this scenario that the Save took a little longer than it would normally).

 

On 7.3 – none of this holds true.  It’s almost as if this fix has been completely excluded from v7.3.  Can anyone confirm that this fix actually works for them?  It’s simple to test… open the portal with any user via Windows Authentication (not forms based authentication), then restart the “System Center Data Access Service” on the portal server, and finally make any update to a Work Item.  At this point, check the history of that Work Item – does it say that the update was made by the account running your Application Pool?


Thanks!

Best Answer

Answers

Sign In or Register to comment.