cancel
Showing results for 
Search instead for 
Did you mean: 

MII data pulling issue on iHistorian restart

Former Member
0 Kudos

One of our sites has reported that when the iHistorian is stopped/stops running and they restart it, initially each point polled from xMII is taking six minutes and then no new data is received.

The associated tag server is set to timeout at one minute, so it seems the xMII-to-UDS communication is not failing.

Why wouldn't we get back the data in MII once the iHistorian in restarted?

Note: We are using xMII 11.5

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

All have had some good suggestions (service dependency of the UDS, checking to make sure the collector is working) I've worked with GE iHistorian since ver 1.0. First off, 3.0 is pretty old, and had some issues especially on the collector side. Make sure that you have the latest iHistorian SIM's from GE. You need to run these sims both the server machine and any collector machines out there. Make sure you make back ups of your archives, ihc files and such.

MUST have SIM's are

iH30_1420920032 (DST patch)

iH30_1252827501 (Collector patch, make sure to read the instructions on this one!!! )

IH30_1140611962 (Supplemental SIM, fixes some bugs)

Also, make sure you have ample hard drive space on your collector machine. If you are running low, the collector won't start, or sometimes acts funny. Easiest way to check your tags is the "last 10 value" function in the ihistorian administrator. Or can check in the excel add-in.

You might consider moving to ihistorian 3.1 if you can, It has some significant performance enhancements. You will need to change your UDS to the 3.1 compatible version if you do. GE changes the program ID for each release of historian, therefor making life for SAP (and the rest of us who have written 3rd party apps to talk to historian) quite fun.

Good luck.

Former Member
0 Kudos

Hi,

Jermey is right. Also check the your Collector file in Historain is running or not.If it is the case check the running status of OPC client or OPC server configured to historian server.

If the Quality of the tag value is Bad then data won't display in MII. Craeted UDS instance and iHistorian archiver service will be made automatic in Services.

-Suresh

Edited by: Suresh Hiremath on Sep 1, 2009 2:06 PM

Former Member
0 Kudos

Any chance you are using the 2.5 release of the UDS?

jcgood25
Active Contributor
0 Kudos

Did you setup a service level dependency for the ihDataArchiver service when they created the UDS service? This way if they restart iHistorian the UDS would also follow suit.

Former Member
0 Kudos

We are using iHistorian 3.0.