cancel
Showing results for 
Search instead for 
Did you mean: 

Pco agent going down

Former Member
0 Kudos

Hello Everyone,

I am struggling in connecting with my PCo agent.

Once the agent instance is started it works fine for some time and then suddenly goes down(not in error but goes down).

This results in no connectivity between MII and PCo.

Apart from this,

My Pco server is a licensed version of PCo 2.3 and I am using MII 14.0 SP5.

I cannot see any error in agent log(in verbose mode).

Please help me with this issue.

Regards,

Minakshi.

Accepted Solutions (1)

Accepted Solutions (1)

0 Kudos

Hi Minakshi,

Pco agent getting down may be combination of issues.

1) you can check the PCo and dependent services are in automatic mode.(if mode is manual change to automatic)

2) you can check the logs activity on PCo machine under event logger (check the pco agent turned off time , by that you can get the exact issues )

Regards,

Adhikesh

Former Member
0 Kudos

Hello Adhikesh,

Thanks for your suggestions.

But the issue was with access rights associated to the excel files server. It has been resolved now.

Regards,

Minakshi

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Minakshi,

somehow you PCo lisence file get corrupted or not uploaded properly. In that case only this kind of issue happens. You can see the title bar of the PCo version if it is showing [evaluation version], then you have to reload your lisence ceritificate, then the issue will be solved.

Hope it will help you.

Regards,

Suman

former_member196557
Active Contributor
0 Kudos

Hi Minakshi,

1. Do you have the latest SP/Patch level for PCo 2.3 deployed?

2. If this is a license issue, consider upgrading PCo 2.3 to PCo 15.0 SP4. the new version is still fully backwards compatible, supports MIi14.0, and with the release of SP no longer requires a license registration.

Regards, Steve

Former Member
0 Kudos

Hello Suman and Steve,

Thanks for your response. I checked the environment. But I do not see any license issue.

One more point to add, My ODBC connection works well without going down. The issue is with OLEDB type of connectors.


Scenario and my Observations:

  • I am having 5 PCo instances out of which 2 are ODBC and 3 are OLEDB.
  • ODBC instances works well.
  • For OLEDB, if its in use, it works well. Else if it remains in idle state for some time, all the OLEDB agents stops.
  • Please provide your inputs.
former_member196557
Active Contributor
0 Kudos

Hi Minakshi,

What OLEDB connection or connections are you using in the OLEDB Agents?

Also, please check the Windows Event Viewer logs to see if there are any Errors associated with any of the OLEDB Agent Instances. Check both the Application and System event logs.

Regards, Steve

Former Member
0 Kudos

Hello Steve,

I checked Windows Event Viewer logs but there is no error related to OLEDB Agent Instances in the given time period.

I doubt the OLEDB driver of PCo.

Please provide your valuable inputs.

Regards,

Minakshi

former_member196557
Active Contributor
0 Kudos


HI Minakshi,

Please provide the following:

  1. PCo Version and Patch Level
  2. OLEDB connector details for each different OLEDB connector
  3. How long does it take for the OLEDB Agent instance to fail if not being "refreshed"?

PCo agent should not just stop with no shutdown details when the Agent Instance Log level is set to Verbose.

Regards, Steve

Former Member
0 Kudos

Hello Steve,

Thanks for your suggestions.

But the issue was with access rights associated to the excel files server. It has been resolved now.

Regards,

Minakshi

Former Member
0 Kudos

Hi Minakshi ,

Are you able to see errors on my side ?

Go to the log viewer - > View -> change it to developer traces.

Regards,

Willian.

Former Member
0 Kudos

Hello Willaim,

Thanks for your reply.

I cannot see any error on MII side.

I would like to add an additional input to my query:

I am using OLEDB type of connector to access an EXCEL file on shared folder.

If I keep refreshing the agents, they will not go down.

Please let me know your views.

Regards,

Minakshi