Conflicts between RSAP 2013 and 2014... Need help!

[ukdxb012]

Hi,

A user we have is experiencing issues when working in both RSAP 2013 and 2014.

Everything is fine if they work in RSAP 2013, however, if they open RSAP 2014 they will get the following dialog...

"Launching this version of the program requires repeating a short registration procedure for its components. To ensure correct registration, you will need to accept further warnings displayed by the system".

When you select "OK", you then have to enter log in details with admin rights for the components to be registered. When thats done, RSAP 2014 works fine, HOWEVER, if you then go back to RSAP 2013, this will now repeat the message above and you have to do the same process.

Not having the required rights makes the product crash and you cannot access it.

Also, once you have entered details for the version you want to use, the issue goes away for that version so it would appear that their is a conflict between 2013 and 2014.

Does anyone have a fix for this?

Regards,

Duncan

[Artur.Kosakowski · Accepted solution]

Robot to work correctly needs to register some of its components. This is done during the installation process but is also required while you switch from one version to another so that the versions of the registered components match the version of Robot that is used. This process requires sufficient rights of a computer user. There is no workaround available.

[ukdxb012]

Hi Arthur,

Thanks for the response, really appreciated.

Unfortunately this will not go down too well with our IT depratment regarding the further adoption of RSAP, can you tell me if this is this being looked at for future versions?

Also, do you know when this change came about as we didnt experience this previously...

Regards,

Duncan

[Artur.Kosakowski]

For the older Windows the registration could be done even for users with restricted rights. As systems became more restrictive the information as displayed now was introduced (if I remember correctly starting from Robot 2012) to avoid situations that registration fails with no notification to a user.

This will also be necessary for Robot 2015.