" /> Unable to install Interaction Workspace SIP End point - Genesys CTI User Forum

Author Topic: Unable to install Interaction Workspace SIP End point  (Read 4306 times)

Offline carolroy

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Unable to install Interaction Workspace SIP End point
« on: March 22, 2012, 09:03:01 PM »
Advertisement
When I try to install Interaction Workspace SIP Endpoint (IP_IntWSpaceSIPEp_8020014b1_ENU_windows)

I have the following message "The target computer does not meet the following mandatory requirements: 1. There are pending operations waiting for a reboot. System reboot is required.".

I made multiple reboot, I also tried to unistall/re-install IW before, but I still have this message.  Does anyone have a way to resolve this?

Offline fnunezsa

  • Full Member
  • ***
  • Posts: 213
  • Karma: 5
Re: Unable to install Interaction Workspace SIP End point
« Reply #1 on: March 23, 2012, 01:01:45 AM »
http://social.technet.microsoft.com/Forums/en-US/systemcenterdeployment/thread/5eb50f0b-d788-480d-b2b8-f68281b4c726/

It would have taken less time to google the pending reboot message than creating this thread

Offline carolroy

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Re: Unable to install Interaction Workspace SIP End point
« Reply #2 on: March 23, 2012, 12:27:35 PM »
My question was for people who may already had see this problem.  Not for someone who is googling without having experiment it.

I already made the verification that you are pointing. And a bunch of other solutions that we could fine by googling. 

>:(

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Unable to install Interaction Workspace SIP End point
« Reply #3 on: March 23, 2012, 01:50:32 PM »
As fnunezsa points, it is an OS issue, not a IWS issue...
Try installing something else and then restart.

Offline fnunezsa

  • Full Member
  • ***
  • Posts: 213
  • Karma: 5
Re: Unable to install Interaction Workspace SIP End point
« Reply #4 on: March 24, 2012, 04:06:06 AM »
I have indeed faced that issue before and that was exactly the solution: delete the key PendingFileRenameOperations.

If you search Genesys Tech Support Knowledge Base you'll find exactly the same solution.

If you're looking for another solution you won't find it.