DCO 7.3.6 client giving error in Win7 64 bit

[DCIM_Support]

DCO 7.3.6 when installing on Windows 7 64 bit giving error. please advise?

32 bit installation is working fine.

DCO 7.3.6 Client Error.jpg

(CID:93913977)

[DCIM_Support]

Hi Shemil, I guess you are installing as administrator? I'm a bit worried about the folder called homes$. I'm not sure if that might cause trouble for our installation? When are you seeing the error message, while installing, logging in or starting the client? Please attach the mentioned log file to the question above. That will help investigation further. Also if the error occurs while logging in to the system please attache the server log files that can be gathered using the server configuration interface https://:10000 StruxureWare Data Center Operation>Download server log files

(CID:93913992)

[DCIM_Support]

Hi Soren, Yes the DCO client is installed as administator.The error comes when logging in after entering the IP, username and password. The system gets stuck in "Initializing Application" and afterwards the error pops up. The server log file is around 30mb and in the site for security reasons they can't share any file with us in USB or in dropbox. Thanks & Regards Shemil

(CID:93914064)

[DCIM_Support]

The path in the screenshot tells us that the user folder is located on a network share. That may work fine but unless we get the client log file, it is very hard to come up with an explanation (and a solution).

(CID:93914144)

[DCIM_Support]

Hi Shemil, It is fine to start with the client log that is mentioned in the screenshot you posted in the initial question. The log file should in your case be located in \\users\homes$\7701590\.isxo\7.3.6-86630\Operations\.metadata\.log When you state it is working on 32-bit is the client installed in the same folder?

(CID:93914328)

[DCIM_Support]

For the 32 bit client it is in different folder C:\Users\6962\.isxo\7.3.6-86630\Operations\.metadata\.log is this because of JMS binding and JMS control ports 4457 & 4460 being blocked from Firewall. I thought of this but they tested Telnet from the 64 bit PC to these ports and its working. Also the 32 bit client is also on the same vlan.

(CID:93914597)

[DCIM_Support]

Hi Shemil, it seems like the 64bit version for some reason is installed on a network shared folder and that is causing problems? If possible try to install the 64 bit locally on the client machine. Since the 32 bit version is working and based on your comment seems to be installed in a local folder trying to install the 64bit locally would be the next step as I see it. Also make sure the network settings are the same for the 2 client machines. Fianally please share the mentioned log file from the 64bit machine that is failing if that is still the case when installed locally.

(CID:93914625)

[DCIM_Support]

Hi Soren, We created a new VM for Win7 64 bit and also added a user local to the machine and it is working fine. Now what we noticed is that there are users who are using VDI (Virtual desktops) using Cirtix and as per group policy a Universal profile manager manages all their profiles in users\homes$ shared folder. We checked the installation and it is happening locally in C:\ program files folder for all users. But if a user has profile in the shared folder users\homes$\ folder then it is not working even if the software is installed in local folder.

(CID:93914794)

[DCIM_Support]

Hi Soren,

We created a new VM for Win7 64 bit and also added a user local to the machine and it is working fine. Now what we noticed is that there are users who are using VDI (Virtual desktops) using Cirtix and as per group policy a Universal profile manager manages all their profiles in users\homes$ shared folder. We checked the installation and it is happening locally in C:\ program files folder for all users. But if a user has profile in the shared folder users\homes$\ folder then it is not working even if the software is installed in local folder.

I am attaching the log from client found in users\homes$ shared folder.

(CID:93914796)

[DCIM_Support]

Hi Shemil, From the log file it seems like the user do not have full write access to the network folder. This will give all sorts of errors when launching the client. It might be worth trying if possible to rename the folder to not including $ or if possible map the network drive to a local drive.

(CID:93914852)

[DCIM_Support]

Hi Soren, We tested with a user having write access to the shared folder and for him also it did not work. Also please clarify how the log file is written in "users\homes$\7638\.isxo\7.3.6-86630\Operations\.metadata\.log" if the user (7638) does not have write permission? I checked with the client to change folder name to remove $ sign and it is not possible from their side since they have around 200 live users accessing VDI. We also tried mapping the network drive to a local drive and it also did not give any result. Does Operations client have any condition or scripting written in Java that the user have to be local admin with his profile stored in C:\users directory? Does Operations client support Virtual PC with Microsoft Roaming profile environment where VDI (Citrix) manages user profiles and it will be in a shared folder? Thanks & Regards Shemil

(CID:93915190)

[DCIM_Support]

Hi Shemil, I'm not an expert in these virtual desktop environments and to my understanding they are fairly complex to manage. I would imagine that the user rights can be administered at different levels giving access to some operations of various files and others not. The only requirement for administrative rights are during installation. In regards to Microsoft Roaming profile environment where VDI (Citrix) manages user profiles this has not been tested in our test environment and therefore we can say this is supported. However I am aware a virtual desktop environment has been made running, I do not know of the details though.

(CID:93915191)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.