|
|
Rank: Newbie
Groups: Member
Joined: 3/25/2009
Posts: 8
Location: Aberdeen
|
I installed a PI-OPC interface in a PI node which will get data from OPC sever simulator(installed in another PC). However, it throwed an error message when I tried to start the interface. The error message is:
Error -10400 pipt_nextptwsourcelong failed for point source UI-IF_INFO
Intializing unit library failed
stopping interface
Is there anyone can help me?
|
|
|
|
|
OSIsoft vCampus is a subscription-based, online offering that consists of providing everything people need to develop applications on the PI System. We invite you to take a "tour" of the OSIsoft Virtual Campus - also feel free to consult the FAQ or contact OSIsoft vCampus for more details.
|
|
|
Rank: Advanced Member
Groups: Member
Joined: 4/7/2011
Posts: 137
Location: KZN, South Africa
|
Here we go, it sounds like MR DCOM Do yourself a favour and install the OPC interface on the same node as the server, this will solve 99% of your problems. As soon as you want to start transfering data from server to client if they are on located on different PC you will have to configure DCOM correctly, there are many thing that could cause this but it is most likely a DCOM issue. Another thing you shoudl check is your Trust setting for this new interface. Below you will see an detailed explanation on the OSISoft site. OSI TECHSUPPORT Issue No. 19454OSI8
|
|
|
Rank: Advanced Member
Groups: Member
Joined: 4/6/2011
Posts: 40
Location: Grimsby UK
|
As Squatty says, it's probably the DCOM settings which are giving you the issue and the best solution is to put the OPC interface on the same Pc as the OPC server. It also reduces installation costs as you only need 1 Pc for each interface (unless you start using virtual machines, and then things can get complicated). An added security bonus is if you have firewalls then you can lock down what network traffic is allowed through; Put the interface/OPC server Pc behind the firewall, and then configure the firewall to allow only port 5450 and the IP address of the your PC through.
Are you just testing how the OPC interface works? I'm guessing thats what you are doing by using a server simulator. If you decide to do a full installation with a "live" OPC server, then you might want to do the following to improve your data security;
Set up a user on the PI server specific for this data source, i.e. PLC1
Create a PI trust on the PI server for the OPC interface, say PLC1_Int, and set the PI user to PLC1. I use static IP addresses for my interfaces so I add the IP address to the trust with a netmask of 255.255.255.255. If you are using dynamic IP addresses then I think you can add the Pc name to the trust and it will check the Pc name when making a connection.
Configure all the points being retrieved by this interface with a datagroup of your username, in this case it's PLC1, and read/write access (r/w). Set the world access to read only.
All the steps above help to stop connections from any interface that DO NOT have the same username and IP address/PC name from editing your data for these points. It also stops people using the PI administrator account as the only one that can add data to the archive - the new user can add data but can't change point configuration, and it's limited to these points only.
|
|
|
Rank: Newbie
Groups: Member
Joined: 3/25/2009
Posts: 8
Location: Aberdeen
|
 Squatty and Caffreys_col, thanks for your prompt help. Issue fixed. PI tags can get data now. The steps I did are: 1. Put the OPC interface on the same Pc as the OPC server 2. Set up a PI trust for OPC interface I only did the first step at the begining and the problem still there until I did the second step. Without your help, it will take me ages to figure out where the problem is. Thanks again!
|
|
|
Rank: Newbie
Groups: Member
Joined: 6/23/2011
Posts: 6
Location: Jakarta
|
Hi all, i have the same problem, but different configuration. so i have OPC Server PC (Using matrikon server simulator for testing), PI Interface Server, PI Server i have 3 different PC with LAN. OPC Server (Matrikon)------>PI Interface------->PI Server I can read data TAG from OPC Server to PI Interface through OPC Client, but whe i create in PI Server Point Builder, and look at the current value, the value show Pt Created. here the problem i saw in Message Log. Please take a look.  if this problem about DCOM, let me know how to setting the DCOM, i have read the DCOM setting manual book, but i didnt undarstand. Thanks
|
|
|
Rank: Advanced Member
Groups: Member
Joined: 4/6/2011
Posts: 40
Location: Grimsby UK
|
Hi Illank86,
As Squatty suggests, if possible put the PI interface on the same physical PC as the OPC server; that negates the need for DCOM, as both bits of software are on the same PC. This is the easiest (and possibly simplist solution).
If you need to have separate PC's for the OPC server and the PI interface (although I can't think why) then you need to follow the settings for DCOM in the PI OPC manual to set this up. Some things to make sure are correct...
1. Make sure you have a user on both machines with the same username and priveledges.
2. run the command dcomcnfg on the OPC server and make sure that all the permissions are setup as per the manuals.
3. The OPC foundation have a white paper which has some addtional mods that need to be done for DCOM, which is based on operating system (Windows 200/XP). You will need to check these as well.
If you need any of the manuals/white papers email me and I'll send you what I've got with the relevant sections highlighted.
Hope this helps,
Caffreys
|
|
|
Rank: Newbie
Groups: Member
Joined: 6/23/2011
Posts: 6
Location: Jakarta
|
caffreys_col wrote:Hi Illank86,
As Squatty suggests, if possible put the PI interface on the same physical PC as the OPC server; that negates the need for DCOM, as both bits of software are on the same PC. This is the easiest (and possibly simplist solution).
If you need to have separate PC's for the OPC server and the PI interface (although I can't think why) then you need to follow the settings for DCOM in the PI OPC manual to set this up. Some things to make sure are correct...
1. Make sure you have a user on both machines with the same username and priveledges.
2. run the command dcomcnfg on the OPC server and make sure that all the permissions are setup as per the manuals.
3. The OPC foundation have a white paper which has some addtional mods that need to be done for DCOM, which is based on operating system (Windows 200/XP). You will need to check these as well.
If you need any of the manuals/white papers email me and I'll send you what I've got with the relevant sections highlighted.
Hope this helps,
Caffreys Hi, Caffreys_col thanks for your reply, actually i have project in Chevron Indonesia, and the configuration should be separate between PI Interface and OPC Server (Devices such as Honeywell, Wonderware, etc), So that is impossible to install PI Interface to all of the OPC Server computer. maybe if you can provide me your email, i can send you the Chevron Topology. thanks
|
|
|
Rank: Advanced Member
Groups: Member
Joined: 4/7/2011
Posts: 137
Location: KZN, South Africa
|
With the new version of PI-OPC Interface you can set the dcom settings in the PI-ICU. If you are using Windows2003 you can set the "Default Authentication Level" to NONE. Not the safest way of settings but this would indicate to you that it is indeed a DCOM settings that needs to be modified. Have you also tried running the interface "Interactively"? Have you setup a trust on the PI Server? Can you connect to the OPC server using PI-OPCTools? DCOM U GOT TO LOVE IT 
|
|
|
Rank: Newbie
Groups: Member
Joined: 6/23/2011
Posts: 6
Location: Jakarta
|
squatty wrote:With the new version of PI-OPC Interface you can set the dcom settings in the PI-ICU. If you are using Windows2003 you can set the "Default Authentication Level" to NONE. Not the safest way of settings but this would indicate to you that it is indeed a DCOM settings that needs to be modified. Have you also tried running the interface "Interactively"? Have you setup a trust on the PI Server? Can you connect to the OPC server using PI-OPCTools? DCOM U GOT TO LOVE IT Hi Squatty, thanks for reply, im using PI 2010, for testing purpose, im using XP Have you also tried running the interface "Interactively"? yes, im doing that but its said : cannot have polled tag in scan calss 1 Have you setup a trust on the PI Server? already doing this step Can you connect to the OPC server using PI-OPCTools? i can read data from OPC Server to PI interface through OPC Client, but i cannot show the data to PI Server, the data just show "Pt Created" so here i am now : OPC Server ------> PI Interface -------> PI server ( with 3 computer, same workgroup, same account) OPC Server to PI Interface everything is OK i can read data, but PI Interface to PI Server NOT OK.. here the error i get from the PI SMT on server : 11/3/2011 11:27:44 PM (EPCS-026C7CDA9B\Admin) PI-IFL> Error retrieving service information for \\Marketing-RND\opcint1: Cannot open Service Control Manager on computer 'Marketing-RND'. This operation might require other privileges.(Access is denied)(Get ServiceName)(ProcessAccessor::Initialize) (GetInterfacesAL) do all DCOM setting but still no luck, in OPC Interface list (PI SMT) the status is "Unknown" What do you think?
|
|
|
Rank: Advanced Member
Groups: Member
Joined: 4/7/2011
Posts: 137
Location: KZN, South Africa
|
Yep, you can not have a polled tag in scan class1, this is reserved for advise tags, change the location3 = 1 in your tag and you should be able to get data, or you can create more scan classes and keep them as polled.
|
|
|
Rank: Newbie
Groups: Member
Joined: 6/23/2011
Posts: 6
Location: Jakarta
|
squatty wrote:Yep, you can not have a polled tag in scan class1, this is reserved for advise tags, change the location3 = 1 in your tag and you should be able to get data, or you can create more scan classes and keep them as polled. still cannot poll the data... the value show pt Created.... any idea
|
|
|
Rank: Advanced Member
Groups: Member
Joined: 4/7/2011
Posts: 137
Location: KZN, South Africa
|
Are you editing the interface through the PI-ICU or a bat file?
Can you confirm that the interface is connecting to the PI Server, check you server message logs?
Depending on your PI Server and interface versions you should be running pibufss and not bufserv, please supply me with your server version as well as interface version.
Set you debugging on your interface to the maximum, this will give us a clear indication if the interface is receiving values and then sending it to the pi server. Depeding on your version of softeware being used I know that some interfaces have issues with very long intrument tag attrubutes, you don't have very long attributes for this by any chance?
Try and add another scan class to the interface, it should look like this:
00:00:01 [This is scanclass1]
00:00:05 [This is scanclass2]
Change your point attribute "Location4" = 2 after making these changes.
|
|
|
Rank: Newbie
Groups: Member
Joined: 6/23/2011
Posts: 6
Location: Jakarta
|
squatty wrote:Are you editing the interface through the PI-ICU or a bat file?
Can you confirm that the interface is connecting to the PI Server, check you server message logs?
Depending on your PI Server and interface versions you should be running pibufss and not bufserv, please supply me with your server version as well as interface version.
Set you debugging on your interface to the maximum, this will give us a clear indication if the interface is receiving values and then sending it to the pi server. Depeding on your version of softeware being used I know that some interfaces have issues with very long intrument tag attrubutes, you don't have very long attributes for this by any chance?
Try and add another scan class to the interface, it should look like this:
00:00:01 [This is scanclass1]
00:00:05 [This is scanclass2]
Change your point attribute "Location4" = 2 after making these changes. Are you editing the interface through the PI-ICU or a bat file? Using bat file, create a new bat file Can you confirm that the interface is connecting to the PI Server, check you server message logs? Successful login ID: 25. Address: 192.168.0.133. Host: . Name: PI-ICU.exe(492):remote. User: piadmin. OSUser: . Trust: OPC Alamakbut sometime i got this information Credentials validation failed: ID: 25. Address: 192.168.0.133. Name: PI-ICU.exe(492):remote. Package: Windows Login (SSPI,NTLM) Details: GenerateContext: Login is denied. (0x8009030c) Last Error: [-10407] No Access - Secure ObjectDepending on your PI Server and interface versions you should be running pibufss and not bufserv, please supply me with your server version as well as interface version. Set you debugging on your interface to the maximum, this will give us a clear indication if the interface is receiving values and then sending it to the pi server. Depeding on your version of softeware being used I know that some interfaces have issues with very long intrument tag attrubutes, you don't have very long attributes for this by any chance? PI Server Version 2010, i dont know if this you mean
Interface : OPCInt_2.3.17.18
about instrument tag attributes, im using Matrikon Simulation Server, and the Tag im using is Real8 for instrument tag.here what i got so far when open the interafec list in PI SMT, 11/7/2011 12:56:17 AM (EPCS-026C7CDA9B\Admin) PI-IFL> Error retrieving service information for \\Marketing-RND\opcint1: Cannot open Service Control Manager on computer 'Marketing-RND'. This operation might require other privileges.(Access is denied)(Get ServiceName)(ProcessAccessor::Initialize) (GetInterfacesAL)if you have an email, please tell me so i can email you with the picture, because i cant add picture here. thanks
|
|
|
Rank: Advanced Member
Groups: Member
Joined: 4/6/2011
Posts: 40
Location: Grimsby UK
|
illank86 wrote:
Can you confirm that the interface is connecting to the PI Server, check you server message logs?
Successful login ID: 25. Address: 192.168.0.133. Host: . Name: PI-ICU.exe(492):remote. User: piadmin. OSUser: . Trust: OPC Alamak
but sometime i got this information
Credentials validation failed: ID: 25. Address: 192.168.0.133. Name: PI-ICU.exe(492):remote. Package: Windows Login (SSPI,NTLM) Details: GenerateContext: Login is denied. (0x8009030c) Last Error: [-10407] No Access - Secure Object
here what i got so far when open the interafec list in PI SMT,
11/7/2011 12:56:17 AM (EPCS-026C7CDA9B\Admin) PI-IFL> Error retrieving service information for \\Marketing-RND\opcint1: Cannot open Service Control Manager on computer 'Marketing-RND'. This operation might require other privileges.(Access is denied)(Get ServiceName)(ProcessAccessor::Initialize) (GetInterfacesAL)
if you have an email, please tell me so i can email you with the picture, because i cant add picture here.
thanks
illank86- Where you have your trust listed above it shows that the user is piadmin... you should not use piadmin as the user for a trust linked to an interface if possible. Create another user called Alamak and a group called Alamak-group, and then set the trust OPC Alamak to use the new PI user. Assign the user Alamak to the group Alamak-group. It looks like you can get a connection to the PI server for the PI interface configuration utility (PI-ICU) but then it drops out. Error -10407 is usually related to incorrect login details. Try this. 1. create a new trust called PI_ICU. Leave the IP address as 0.0.0.0 and netmask as 0.0.0.0. Where it says "application information" type in PI-ICU.exe. Set the user to piadmin. Whenever the interface configuration utility attempts to connect to the pi server on ANY interface node, then it will use the trust PI_ICU, with the PI admin user. 2. Edit your current trust OPC Alamak as follows: specify the IP address of the interface node and set the net mask to 255.255.255.255 in the box below it. Leave the application information box empty. Set the PI user to Alamak. Whenever any program, apart from the PI-ICU attempts to connect to the PI server it will use the OPC Alamak trust and the user Alamak. 3. Edit the configuration of you points for this interface to have the Datagroup as Alamak-group, with data access rights of o:rw g:rw w:r 4. restart your interface and check your logs to see if you connect with the new user/trust. Hopefully this will give you the correct permissions to connect to the PI server. One other thing to notice is in the interface config utility find the "OPCint" entry in the list on the left hand side and highlght it. In the list box next to it, select the "advanced options" tab under the "OPC server" tab. Look for the box which says "ignore OPC server access rights" - make sure this is checked. Just to make sure we are not doing anything stupid - is there a firewall between the PI server and the interface node, or between the interface node and OPC server?? If there is then this can cuase problems if the access lists are not correct.
|
|
|
|
Guest
|
