iHistorian 3.1 UDS Not installing correctly

[Former Member]

I am currently attempting to install the UDS for GE Historian 3.1 and am running into some issues. We have installed it a couple times on local test boxes with no issues, but at the customer site we can not get the installation to work correctly. After the software is installed (both the framework and the IHISTORIAN31UDS_SETUP) I attempt to run the UDS Admin. It returns an error everytime of: Unable to Load UDS Schema. Schema Does Not Exist. Application Will Exit.

Some more background. We had some other issues with installation. When we installed with any user other than the local "Administrator" user it would install the XML files in a specific location for that user. The files appear to be in the correct location now (C:\Windows), but the Admin is not seeing them for some reason.

Any ideas on how to proceed and get this resolved?

Thanks,

Zane

[Former Member · Accepted solution]

Remove Windows Component "Terminal Server"

Zane,

It was the installation (switching on) of Terminal Services that did the damage.

To allow RDP access to the server, we had enabled Terminal Services from:

Add/Remove Programs, Windows Components, Terminal Server

Removing this Windows component (by un-checking the box) allows us to run UDS Admin without the error.

To enable remote access to the server (for 2 sessions only for administrators):

My computer Properties (or Control panel System), Remote, Enable Remote Desktop on this Computer

Maurice

[jcgood25]

Is the C:\WINDOWS directory in the path or a permission problem perhaps? If the UDSAdmin console can't locate the UDSSchema.xml file (or load it because of parsing issues) then that might explain your error. I can emulate your error by renaming the file from UDSSchema.xml to UDSSchema2.xml.

Another thought related to the schema might be the MSXML parser - how old is the IE version on the problem machine?

[Former Member]

Thanks for the reply Jeremy. The file sits at C:\Windows\UDSSchema.xml. I think that the permissions are OK as I installed this using the Administrator user on the box itself.

I don't think that it is an issue with the XML parser. When I installed the software as another user, it would start the UDS Admin tool fine, but you couldn't start the UDS Connection service. Also, it that scenario, only the user that installed the software could run the UDS Admin tool. Anyone else that logged on would get the Schema Not found error.

[erik_schrampf]

Zane,

What version of the UDS do you have? There are problems with 2.5.x version similar to this problem. Try to open the UDS with the same person that did the install. There is a permissions problem if a different user tries to open the UDS from the user that performed the install.

[Former Member]

Eric,

It looks like I have 2.5.0.4 from the framework installation file. I installed the software as Administrator and I am trying to open the Admin tool as Administrator. We tried a couple of installations with other users previous to this, but we ended up uninstalling them as it didn't look like they were installing the xml files to the correct location.

[Former Member]

Zane,

Just a few questions... Are you installing this though terminal services or remote desktop? on a 2003/2008 OS? If so, then what may be happening is that the remote desktop manipulating some of these directories on exit.

[http://technet.microsoft.com/en-us/library/cc776114.aspx]

I would remommend installing the software on the machine or with the remote desktop in console mode (see the Microsoft Help documents for more details).

Martin

[Former Member]

Thanks Martin, I'll check that out.

I am installing this on a 2003 Server. It is a VMWare image that they are using for development (as were all of the test boxes that I installed the UDS on locally). I am logged on as the console user using RDC.

I'll keep digging. Thanks again.

[erik_schrampf]

Zane,

The 2.5.4 UDS has to be installed on the actual machine or through remote desktop in Console mode. That seems to be the issue since you are seeing the UDS.xml showing up in C:\Documents and Settings\Administrator\WINDOWS and not C:\WINDOWS.

If you are using a VMWare machine it has to be installed using the VMWare console.

One last thing 64 bit system are not supported I do not remember what this system was.

Edited by: Erik Schrampf on Jan 8, 2009 12:30 PM