Issue in PCo 2.1

Hello Experts,
We are facing an issue with SAP PCo while working in SAP MII 12.2.We are not able to start a particular agent instance.First we are stopping the agent instance and then when we are trying to start the same it is taking a huge time and finally showing the following error.
"Error 1053: The service did not respond to the start or control request in a timely fashion."
The PCo version is 2.1
Kindly advise.
Regards,
Shawna

Hi Shawna,
Please provide more information on your system.
What patch or SP is PCo on?
What version, SP, and build/patch are your MII and NW installations?
What are you connecting PCo to (what historian or OPC data source)?
Where is PCo installed relative to NW/MII and relative to the data source (firewalls?)?
Regards,
Mike

Similar Messages

Issues regarding PCO Notification

Hi experts,
I have a question.Is there any way to make the notification of tags time-based so that the notification will be generated only after a certain specified interval of time?Even if I specify the trigger type as WhileTrue the notifications are generated randomly whenever the value is changed without any specified time interval..
Thanks,
Suman

Suman,
Ok, I believe I understand your situation now. I have never done it but you should review the [date/time |http://help.sap.com/saphelp_pco21/helpdata/en/42/3550f08e2e444ea4d24a5e12bbfe54/content.htm]functions in PCo. You could try it with a complex trigger expression using the "if" expression, and then using the date or other time based functions in the condition part. However, since PCo doesn't store variables you wouldn't really be able to compare +-5 minutes. Even if you use the different trigger types I am not sure how you would be able to keep track of the baseline time (via minuteCtr) and compare it with future values (if threshold reached and minuteCtr==5).
What some customers implement is a notification of the initial event to MII and then have an MII transaction run a query on the tag to monitor there. If the tag gets out of control they can alert via dashboard screen or email to a shop floor operator.
Regards,
Kevin

Pco Query Event Mode Issue

Hi Experts,
I am having issue with Pco query with event view following are details.
SAP MII 14.0 SP04
SAP Pco Version 2.2 (2.200.894.206)
OSI PI (connectivity using PI Trust)
Suppose I write one PI tag 4 times in history mode for same time stamp with values (10,12,12,25)
than I am using Pco query with event mode to get data for that time stamp with row count 4 and I am receiving 4 entries with same time stamp.
However I need single entry with last value written (25) with single time stamp.
Please let me know what I am missing here.
Thanks & Regards,
Manoj Bilthare

Thanks Steve
I really appreciate your response and it is very helpful.
We need data in history mode with multiple data points.so we can not use current mode and rowcount as 1.
I am assuming that to achieve this either I have to use interpolated view or for event view OSI PI have to remove archiving so that it will maintain single data point for one timestamp.
Please let me know if my assumption is right or is there any better way.
However with rowcount 1 it is returning the first value.
Regards,
Manoj Bilthare

Errors when Starting Agents in PCo 15.0 SP3

We are in the process of upgrading to PCo 15.0 and are getting the following error when starting an agent. We used the same configuration and setup using PCo 2.3 with no issue but we are having issues with PCo 15.0 SP3. This issue is happening on both DA and HDA agents. Has anyone see this before:
1910     Manufacturing Fault: REASON = FileNotFoundException
Could not load file or assembly 'WebSocket, Version=15.0.3.2284, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.; SEVERITY = Fatal
STACK TRACE:
    at SAP.Manufacturing.Connectivity.Protocol.Custom.PCoQueryListener.Start()
   at SAP.Manufacturing.Connectivity.AgentBase.InitializeProtocol()
   at SAP.Manufacturing.Connectivity.AgentBase.Start()
Thanks,
George

HI George,
Re-apply the PCo Installer, expand the list of installation items, and scroll down to Additional Components to select Websockets, and deploy. That should correct your issue.
Regards, Steve
Message was edited by: Steve Stubbs

Pco monitoring issue.

Hi Experts,
I m trying to achieve Pco monitoring in SAP MII 14.0. I m refering following document:
http://help.sap.com/saphelp_pco21/helpdata/en/f2/b1d0e885284db2baabef7eea15373e/content.htm
I m able to do the Alert Configuration using active monitoring.
But what condition should i check in MII transaction or which parameter from remote monitoring will tell me that PCo is down?
I want to send e-mail once PCo is down.
I have enabled the active monitoring and configured the MII system and got test connecttion as success.
I am able to see the all projects in MII server . I configured the transaction and input variable (xml). After click on ok ,getting success message.
After that I could not see any trx in transaction manager.
I made dataserver connection to pco as error but still I could not see the configured trx in transation manager.
Pls suggest me to overcome this issue.
Configuration:
SAP MII 14.0
PCO 2.3 SP3
Regards,
Raj.

Hi Raj,
Question: But what condition should i check in MII transaction or which parameter from remote monitoring will tell me that PCo is down?
Answer: The MII Transaction will called only when the PCo agent goes down or not able to connect to its source system. So you need not check anything in MII. The input param of the MII transaction will receive the error detection time-stamp and the node name (PCo instance or PCo and agent instance).
Question: I made dataserver connection to pco as error but still I could not see the configured trx in transation manager
Answer: Making the MII PCo data server go down or disabling it will not execute the alert or call the configured MII transaction. When the PCo agent is not able to connect to its source system then the configure MII transaction will be called.
Hope that these clarifications will clear your doubts.
Regards,
Rohit Negi.

PCo 2.2 - ECC Connection Issue

Hello,
We have got PCo 2.2 version. I have to call a simple BAPI from PCo agent.
I have created new destination system of type: RFC Destination (SAP NW).
I have followed the steps mentioned in:
http://help.sap.com/saphelp_pco22/helpdata/en/bf/3a68c28c1f4b8190d55b3e1e85a716/content.htm
But, I am not able to connect to ECC system. I have given application server name, SAP router, System No, Client, User Password and other details correctly. I am also getting the same error when I am creating the connection from SAP SM59 transaction.
Please let me know if you have any clue on this.
Thanks in advance.

Hi Michael,
I want to test the functionality of "RFC destination" in PCo 2.2 (and also to create an agent which use this destination for notification).
Also, I have filled all the details on the 'Query Port' tab. But I am getting error as host 'xxx' unknown.

PCO Approval strt condition issue

Hi,
I have two scenarios for PCO Approval worklfow.
For the first scenario, the PR has no scheduled lines and for this scenario, I need to implement WS14500001 and this is an automatic workflow.This is working fine.
For the second scenario, I have scheduled lines and for this I need to implement, WS14500019. I have tried to implement this also. But I am unable to set the start conditions as required. i.e. I am unabale check in start conditions that I have scheduled lines in item or not.
Due to that, the workflow is not at all triggered and I am getting errors in updating the po.
"Error when transferring from PO confirmation data to PO"
I need to know the best method to :
1. to disable the workflow WS14500001 to getting triggered when there is scheduled itmes.
2. to enable the workflow WS14500019 to getting triggered when there is scheduled itmes.
It would very great if any one could throw light on this.
With Thanks and Regards
Ravishankar Vembu

i have checked the workflow start conditions --> in your case --> unfortunately it is not possible to check for schedule lines --> at the start conditions.
you have to look for other options with which you can differentiate between the documents --> using any other option...

Issue with PO Response in SRM 7.0

Hi Experts,
We have upgraded our system from SRM 4.0 to 7.0. Post upgrade we are facing an issue with PO Response document.
Scenario:
When the PO is ordred, Vendor sends a the PO response through XML. Our middleware call the an FM which uses BBP_PD_POC_CREATE to create the PO response(BUS2209) with acceptance status.
Problem:
The status of the PO response is always + In Process+. But in SRM 4,0 we are having the responce with accepted status.
Could you please throw somw light on this.
Thanks in Advance,
Vishnu Reddy

There is this note that might help you.
Note 1393346 - PCO:Header status is open, even all items in PCO accepted
Although a relatively new note, this note is only relevant for SRM5.0 at the moment. What I'd suggest you do is to (temporarily) modify the standard code (in your development or test system) based on the correction instruction of this note. If it resolves your problem, create an OSS mesasge to SAP and ask them to upport the note to SRM7.0. Then you could reverse your modification back to standard and apply the note officially.

Oracle connector issues

Hi Experts,
We have 40 to 50 connectors including SQL server, Oracle,Pco,OLAP etc in SAP MII system.
SAP MII version 12.2 SP6.
We got the Java Heap space on the SAP MII server and due to lack of disk space the server process is shutdown.
#2.0#2015 04 14 09:30:16:473#0-400#Fatal#com.sap.engine.frame.ProcessEnvironment#
com.sap.ASJ.krn_frm.000041#BC-JAS-COR#kernel.sda#C0000A0E68F54AF20000000100000D58#307331950000768373##com.sap.engine.frame.ProcessEnvironment#Guest#0##7F961CADD61211E4A26400001251836F#7f961cadd61211e4a26400001251836f#7f961cadd61211e4a26400001251836f#0#Thread[Managed_Application_Thread_37,5,Managed_Application_Thread]#Plain##
Server process shutting down with exit code [666]; memory allocation error [OutOfMemoryError]#
#2.0#2015 04 14 09:30:16:473#0-400#Fatal#com.sap.engine.frame.ProcessEnvironment#
com.sap.ASJ.krn_frm.000041#BC-JAS-COR#kernel.sda#C0000A0E68F54AF20000000200000D58#307331950000768373##com.sap.engine.frame.ProcessEnvironment#Guest#0##7F961CADD61211E4A26400001251836F#7f961cadd61211e4a26400001251836f#7f961cadd61211e4a26400001251836f#0#Thread[Managed_Application_Thread_37,5,Managed_Application_Thread]#Plain##
Server process shutting down with exit code [666] memory allocation error [OutOfMemoryError]
[EXCEPTION]
java.lang.OutOfMemoryError: Java heap space (failed to allocate 56 bytes)
After clearing the dump and make available disk space all the connectors like SQL server, OLAP,PCo etc working fine. But Oracle connectors are unstable.I can say oracle connectors keep loosing connections. The following errors were seen in logs. After I restart the server , the oracle connector starts working fine.
Unable to create connection to database for GDW
[EXCEPTION]
java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver
at com.sap.lhcommon.system.CustomClassLoader.findClass(CustomClassLoader.java:232)
at java.lang.ClassLoader.loadClass(ClassLoader.java:367)
at java.lang.ClassLoader.loadClass(ClassLoader.java:308)
at com.sap.xmii.Illuminator.tools.database.JDBCDriverManager.getClassInstance(JDBCDriverManager.java:104)
at com.sap.xmii.Illuminator.tools.database.ConnectionPool.<init>(ConnectionPool.java:62)
at com.sap.xmii.Illuminator.tools.database.ConnectionHolder.addDBConnectionPool(ConnectionHolder.java:121)
at com.sap.xmii.Illuminator.server.Server.createHolder(Server.java:277)
at com.sap.xmii.Illuminator.server.Server.start(Server.java:134)
at com.sap.xmii.Illuminator.server.ServerManager$ServerInitializer.run(ServerManager.java:451)
at com.sap.xmii.Illuminator.server.ServerManager.startServer(ServerManager.java:414)
at com.sap.xmii.Illuminator.server.ServerManager.reload(ServerManager.java:370)
at com.sap.xmii.ejb.ServiceHandlerBean.doServerFunction(ServiceHandlerBean.java:222)
at com.sap.xmii.ejb.ServiceHandlerBean.onMessage(ServiceHandlerBean.java:75)
at sun.reflect.GeneratedMethodAccessor276.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:47)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:50)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MessageListenerType.invoke(Interceptors_MessageListenerType.java:111)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:191)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:23)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:25)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:17)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Lock.invoke(Interceptors_Lock.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:179)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:138)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at com.sap.engine.services.ejb3.runtime.impl.MDBProxyInvocationHandler.invoke(MDBProxyInvocationHandler.java:78)
at $Proxy435.onMessage(Unknown Source)
at com.sap.jms.client.session.JMSSession.deliverMessage(JMSSession.java:1046)
at com.sap.jms.client.session.JMSSession.run(JMSSession.java:894)
at com.sap.jms.resourceadapter.RaServerSession.run(RaServerSession.java:139)
at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:410)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
Error occurred while creating a database connection
[EXCEPTION]
com.sap.xmii.Illuminator.system.CommunicationException: Error occurred while creating a database connection
at com.sap.xmii.Illuminator.connectors.IDBC.IDBC.doProcessRequest(IDBC.java:81)
at com.sap.xmii.Illuminator.connectors.AbstractConnector.processRequest(AbstractConnector.java:83)
at com.sap.xmii.Illuminator.server.QueryEngine.run(QueryEngine.java:49)
at com.sap.xmii.Illuminator.services.handlers.IlluminatorService.processRequest(IlluminatorService.java:82)
at com.sap.xmii.Illuminator.services.ServiceManager.run(ServiceManager.java:69)
at com.sap.xmii.servlet.Illuminator.service(Illuminator.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:202)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:103)
at com.sap.xmii.system.SecurityFilter.doFilter(SecurityFilter.java:186)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.xsrf.filter.XSRFProtectorFilter.doFilter(XSRFProtectorFilter.java:62)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:79)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:441)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:210)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:441)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:430)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:38)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:81)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:278)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:81)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.SessionSizeFilter.process(SessionSizeFilter.java:26)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:57)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:475)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:269)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:56)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
I am not sure of OJDBC jar file version .we have either OJDBC5 or OJDBC6 jar deployed in SAP MII.
The oracle database version that we are connecting in the data server is Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit
My questions are
After the server process shutdown and recovered , While all other connectors working fine why oracle connectors have problems?
Is it due to oracle driver issue? or any other issue related to Netweaver.
Please help.

for item #1...If you add the line "gal_enableldapsearch = FALSE" to the "[ENG]" section of the calendar server configuration file, it will only put calendar users in the GAL and not all Internet Directory users.
--Bill

How to pass tag name and value dynamically in the output of PCo notification?

Hi,
I have a requirement to develop such a scenario where there can be multiple no of tags in PCo (Say 10) but there will be single notification to push the tag name when the value got changed and the changed value to MII. for any value change for any of the tag, the notification will be trigger. So As per my knowledge I have to pass the tag name and value dynamically in the "output" tab of the notification. But need your support to find out how to pass them dynamically.
Thanks in advance.
Regards,
Suman

Hi Suman/Jeedesh,
As per Pco notification, it will trigger whenever any of the tag value changes in Agent instance subscription items.
For above issue, My suggestion
1. Create DB table name TAGLIST with 200 tags as rows in columns (Tagname, TagValue)
2. Based on notification trigger, create a transaction and update values w.r.t TagNames in above table
3. Next time, when notification trigger with fresh value for any of the tag, cross check with existing TagName with Value and update in DB table.
4. And in the mean time, send those Tag details vie mail trigger or as per requirement
Instead of creating 200 notification, above is a just alternate way suggestion to achieve dynamic tag value change notification.
Hope it might solve your problem
Regards,
Praveen Reddy

Transporting PCo Setting Through Landscape

Hello,
We are using PCo 2.1 and MII 12.1. We have 3 instances of each for development, staging, and production.
In order to transport changes from one environment to another, I am using PCo's Export/Import capability. This works ok except that, after importing, I have to manually edit the Destination System's Server Name setting to change it to point to my staging MII host instead of my development MII host. I have the same issue going from staging to production.
I would like to avoid the manual editing. Is there a way around this?
Thanks,
Mike

Mike,
I belive you could just import the Agent by iteself. Instead of importing the source and destination everytime.
Regards
Ajay.

PCO Query: tag not found

Hi,
I am writing values to a datablock on a PLC using SAP PCO and OPC as middleware.
It is working for all tags in the datablock except for 2.
This is a screenshot of both tags in the OPC Quick client (I am using Kepware OPC server).
I can read and write the tags from here.
I have created a small test. In the MII workbench I created a PCO Query.
Next I dragged the two tags from the tag browser on the left, to the right.
For both tags I filled in a value.
When I execute the query I get following error messages.
M1 Order Dispatch/OrderQuantityTarget: Tag PoederMagazijn/ATS PLC/M1 Order Dispatch/OrderQuantityTarget not found.
M1 Order Dispatch/OrderQuantityConfirmed: Tag PoederMagazijn/ATS PLC/M1 Order Dispatch/OrderQuantityConfirmed not found.
Any other tags work fine.
Thank you for your time.

Hi Philippe,
I tested a similar tag name in Kepware with the Simulator device as I do not have a Siemens hardware connection at present. I was able to read and write DWord tags without issues on these versions:
Kepware V5.15.585.0
MII 14.0 SP5 Patch 15
PCo 2.305.2141.1051 (Patch 3)
Additional question: What is the Agent Instance Tag Query Cache Mode set for?
Regards, Steve

PCO 2.2 - OPC and IP21

Hi,
We are looking at connecting to IP21 via PCO OPC DA connector.
Can PCo only poll the IP21 OPC server for eventing or can one set up the IP21 OPC server to advise PCO on data changes for
eventing purposes ?
Also what is required on the server where PCo is installed to enable OPC connectivity, for browsing the IP21 we have established that you need the following dlls in the PCo system directory :
cimsrvapi.dll
CimWin32Util.dll
infoplus21_api.dll
ip21admin_client.dll
ip21ezrpcw32.dll
ip21winrpc32.dll
libc21.dll
PCo is running on Windows server 2008 R2 and the IP21 is not on the same box.
thanks

Hi ,
I got it working to be able to get the notification working. Although one still cannot browse the IP21 tags, and all tags are still shown as a name space.
a. I installed the Matricon IP21 OPC server on the same box as IP21 Historian.
b. I connected to the IP21 server and configured new aliases in the Matricon IP21 OPC server to look at the IP21 tags
c. I then configured PCo OPC DA agent to look at the Matricon IP21 OPC server and got the subscriptions to work, and PCo can browse the MAtricon IP21 OPC server tags that I configured , so the browsing seems to work via this OPC server
d. Then I tried to fire up the OPC DA agent in PCo that I previously configured to look at the Aspentech IP21 OPC server, and the configuration now started to work (still can't browse the tags)
e. I uninstalled the Matricon IP21 OPC server and the configuration in step d. still worked.
So the conclusion is that the Matricon IP21 OPC server did some sort of a configuration that made the orginal configuration functional, this however now leaves me the question of what did this driver do to get things working.
Now I sit with a new challenge I have PCo installed on a seperate server and in a different domain as the IP21 OPC server.
What I have so far
1. The Same local user on both the PCo box and the IP21 OPC server with Admin rights
2. I can see the IP21 OPC server from the PCo box and access it
But the issue is as soon as I fire up the Agent to run it fails to start with the following error:
ConnectivityAgentProxy|"The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
Below is the PCo Log file:
Date Time| Machine| Thread ID| Process ID| Process Name| Event Type| Source| Message| Stack Trace
2012/02/24 04:12:01 PM|.|8|7888|IP21_OPC_DA|Information|AgentBase|Start ignored. Agent state = Faulted|""
2012/02/24 04:12:01 PM|.|6|7888|IP21_OPC_DA|Information|Host|WCF service is started.|""
2012/02/24 04:12:01 PM|.|6|7888|IP21_OPC_DA|Error|Host|failed to create ConnectivityAgentProxy|"The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly. Server stack trace: at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at SAP.Manufacturing.Connectivity.IPCoAgentControl.Start() at SAP.Manufacturing.Connectivity.ConnectivityAgentProxy.Start() at SAP.Manufacturing.Connectivity.WcfHost.Start()"
2012/02/24 04:12:01 PM|.|8|7888|IP21_OPC_DA|Error|ServiceFaultManager|Manufacturing Fault: REASON = The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly. ; SEVERITY = Fatal|""
2012/02/24 04:12:01 PM|.|8|7888|IP21_OPC_DA|Verbose|AgentBase|beginning PublishSubscribe CommunicationMode initialization...|""
2012/02/24 04:12:00 PM|.|8|7888|IP21_OPC_DA|Verbose|AgentBase|starting...|""
2012/02/24 04:12:00 PM|.|6|7888|IP21_OPC_DA|Information|Host|implicitly calling start on the hosted IConnectivityAgent service contract|""
2012/02/24 04:11:59 PM|.|6|7888|IP21_OPC_DA|Information|Host|using default NetTcpBinding endpoint for internal IConnectivityAgent proxy|""
2012/02/24 04:11:59 PM|.|6|7888|IP21_OPC_DA|Verbose|Host|Service endpoints:|""
2012/02/24 04:11:59 PM|.|6|7888|IP21_OPC_DA|Verbose|Host|SAP.Manufacturing.Connectivity.Agents.Opc.Da.OpcDaAgent is running with the following endpoints:|""
2012/02/24 04:11:58 PM|.|6|7888|IP21_OPC_DA|Information|Host|WCF service is starting.|""
2012/02/24 04:11:58 PM|.|1|7888|IP21_OPC_DA|Verbose|OpcDaAgent|Creating the OPC DA agent.|""
2012/02/24 04:11:58 PM|.|1|7888|IP21_OPC_DA|Verbose|BrowserSessionManager|Created browse manager.|""
2012/02/24 04:11:58 PM|.|1|7888|IP21_OPC_DA|Verbose|OpcDaAgent|Creating the OPC DA agent.|""
2012/02/24 04:11:58 PM|.|1|7888|IP21_OPC_DA|Verbose|BrowserSessionManager|Created browse manager.|""
2012/02/24 04:11:58 PM|.|1|7888|IP21_OPC_DA|Verbose|Host|Running [IP21_OPC_DA] as a windows service...|""

Pro*Cobol PCO Compilation problem in Linux

Hi,
DB :oracle 11g on RHEL 5.5
when we are compiling the (Pro*cobol ) PCO code it is giving us the error :
System default option values taken from: /oracle/oracle11g/app/product/11.2.0/dbhome_1/precomp/admin/pcbcfg.cfg
Error at line 320, column 35 in file BR2385.PCO
WHERE A.SOC_NO = :PARAM-SOC
..................................1
PCB-S-00223, Undeclared variable "PARAM-SOC".
when we change the pcbcfg.cfg file with flag : declare_section=no it's compile without error.
But in this scenario cobol app doesn't run.
if we declare the undeclared variable in the section
EXEC SQL BEGIN DECLARE SECTION END-EXEC.
PARAM-SOC PIC X(25).
EXEC SQL END DECLARE SECTION END-EXEC.
and compile it with declare_section=yes then cobol app. run fine.
Are different files generated (cob,int,gnt) after compilation with the option declare_section=no and declare_section=yes.
Pls help us in this regards. we have lot of file which having these issue and we don't want to do manual changes "EXEC SQL BEGIN" in it.
Thanks in advance..

Your code is faulty and has to be fixed.
No compilation problem is present, the compiler correctly barfs.
As this is not a support forum, kindly keep your non-issues out of this forum.
Thank you!!!
Sybrand Bakker
Senior Oracle DBA

Notification Create time in PCO 2.1

Hello,
I am using PCo 2.1.6.0 and I have observed a difference of 4 hrs between the Notification Create time and the time zone where actually PCo is installed.
In my current scenario both PCo & the data source (OSI PI) are installed on the same server which follows the EDT/EST time zone.
The notification message create date that is sent to MII (which also resides in the EST/EDT TZ) show a + 4 hrs (I think it shows GMT). I observe the same time when I do a "Test Notification Delivery" --> "View Sample" for a notification.
On the PCo Mgmt Console if I navigate to Tools --> Options and further expand Global Properties and click Date/Time format the correct time is displayed.
Additionally if I run a TAG query against the same Agent the correct time is returned.
Why is there a difference for the notification then, when everything is in the same TZ? Am I missing some config setting in PCo?
I have not come across any SAP note on this issue and could not find any older posts referring to this behavior.
Thanks for the help.
Udayan
Edited by: Udayan Upreti on Sep 19, 2011 9:30 AM

Ud,
Ok, so to fully answer your original question as to why there is a difference in the timestamps of a PCo notification and a MII Query to a PCo agent.
The notifications always use UTC which is universal time regardless of timezones or system settings and was agreed upon as the best approach to keep track of when messages were actually created. If you want current timestamp of the server in the message payload you can add an Expression with the value of "datenow()" and I believe that this will give you the current timestamp of the PCo server.
When you query a PCo agent from MII, the MII Time Engine will take care of the timezone conversion for you in order to ensure that date from the proper time ranges the user is asking for is returned to them. Since the MII and PCo servers can be located in diffferent regions/timezones we have to handle this in our time engine.
Does this make sense?
Regards,
Sam

Issue in PCo 2.1

Similar Messages

Maybe you are looking for