ies software - access denied

[octavalent]

Hi,
Yesterday I installed the 6.4 I cannot access the software. Currently we use 6.3, I get 'Access Denied' which will not close even if I click on it many many times. It has to be shut down via the processes in task manager. We use a network licence and I do have access to the network path that resides in the keyspath.txt folder. I have uninstalled and reinstalled but nothing works. I have tried just using 6.3 which does not work anymore.

It is almost definitely the access to the network licence that is the issue. I can redirect the licence path and it then tells me that I need a valid licence for the installed componemts.

Any help would be appreciated.

Paul Smith
Coventry University

[vajindarladdad]

Dear Paul,
Sorry to see that you are facing problem with VE.
Could you please get in touch with our "Support" department with complete SystemReport ?

I have mentioned the procedure to generate SystemReport for you.

1)Start<VE>.
2)Select ‘Troubleshooting…’ action from ‘Help’ menu.
3)Click ‘Full Report’ button from the ‘Troubleshooting <Virtual Environment>’ form.
4)Now click ‘Copy’ button from the ‘Troubleshooting <Virtual Environment>’ form.
5)Paste it to the Text Editor (Notepad, Textpad and Microsoft-word) save the file & send it to us.

[octavalent]

Hi Vajindar,

I have sent the report to support@ies.com

The pin seems to have been disloged. The network chap is running both 6.2 and 6.4, so its me.

I would like to know how the network license operates, do I have to have the network pin installed and then the keyspath.txt file altered to the network location, or do I need the local pin installed which will then get overwritten by the network pin which should be displayed in the troubleshooting report.

I think I am getting closer to sorting it out, I just need to be able to tell it what pin to use.

Regards
paul

[octavalent]

Sorted it out:

When I installed the new software I have to give a keys location so that I could generate a keyspath file under C:\Documents and Settings\All Users\Application Data\ies\apps\Keys\keyspath.txt

I then alter the licence path in keyspath.txt to the network \\your network keysfile location\apps\keys

Normally it sees this licence and fires up with all the apps loaded. This time however it could not access this file so Access Denied.

I then realised that the local keys file pin number did not match the server licence pin. So I emailed a correct version of the keys info from a machine that was working correctly, Troubleshooting Keys Info and saved it locally as keys.txt

C:\Program Files\IES\VE 64\apps\keys\keys.txt

this meant that the local keys info imatched the remote info and it all worked.

I have no idea how software would not read the server keys file in the first place. It has worked many times before. Maybe I clicked a wrong button when setting up.

It might be a suggestion to be able to type in the file keys path as well as browsing for it under the 'set licence folder' as IES will not allow you to link to a mapped drive due to the limited file structure. It needs the \apps\keys path.

Thanks for the response anyway.

[Steven]

Hi Paul,

Just a couple on notes on network licenses.

I would like to know how the network license operates, do I have to have the network pin installed and then the keyspath.txt file altered to the network location, or do I need the local pin installed which will then get overwritten by the network pin which should be displayed in the troubleshooting report?

The network licence resides on a shared location on the network. For a client machine you simply need to install the software and point it to the keys folder on the network. You don't need a licence stored on the local machine.

When you first install the software the IES User Information dialog will appear. If your network licence has already been set up then simply click the “Change keys location” button and navigate to the shared location on the network. To be able to browse to the network location all the folders will need to be visible and not “hidden”. You can also manually edit the keyspath.txt so it points the the network folder.

You will need read/modify/write permission for the folder on the network. Without the correct permissions you will receive the Access Denied error message. Looking at your system report the software was not looking in the correct location. As you didn't have permission to write to this folder you received the Access Denied message.

If you have any further question then please feel free to ask.

Thanks,
Steven