Jump to content

Can't open eCapture Controller, nucleus error


Michael Atkin

Recommended Posts

  • Administrators

If you are getting an error that says eCapture is "Unable to connect to Ipro Nucleus" when trying to open the Controller, you may need to do the following:

Try to load the ADD Services website by entering the ADD services URL in an internet browser. If you have access to the web server running IIS you can get the URL by looking at the ADD services site and clicking the "Browse Website" on the right.

 

If you see the following error when the page loads then use the next steps to correct it-

 

"Parser Error Message: Unrecognized attribute 'targetFramework'. Note that attribute names are case-sensitive."

 

[ATTACH=CONFIG]n1951[/ATTACH]

 

 

In order to fix this, you have to change the Application Pool settings in IIS:

-Check the .NET framework version for the ADDSrvAppPool in IIS under basic settings

 

[ATTACH=CONFIG]n1950[/ATTACH]

-change the value in the dropdown from v2.0 to v4.0

-recycle the app pool and then eCapture should start normally.

 

Link to comment
Share on other sites

  • Administrators

If you are getting an error that says eCapture is "Unable to connect to Ipro Nucleus" when trying to open the Controller, you may need to do the following:

Try to load the ADD Services website by entering the ADD services URL in an internet browser. If you have access to the web server running IIS you can get the URL by looking at the ADD services site and clicking the "Browse Website" on the right.

 

If you see the following error when the page loads then use the next steps to correct it-

 

"Parser Error Message: Unrecognized attribute 'targetFramework'. Note that attribute names are case-sensitive."

 

1420424419_2017-06-1514_05_09-Conversations.png.653b5ad40f88e59a0d80ab61fb81f073.png

 

 

In order to fix this, you have to change the Application Pool settings in IIS:

-Check the .NET framework version for the ADDSrvAppPool in IIS under basic settings

 

2079769588_2017-06-1514_03_11-Conversations.png.c635840b27a0642ad1d7477b44aef875.png

-change the value in the dropdown from v2.0 to v4.0

-recycle the app pool and then eCapture should start normally.

 

Link to comment
Share on other sites

  • Administrators

If you are getting an error that says eCapture is "Unable to connect to Ipro Nucleus" when trying to open the Controller, you may need to do the following:

Try to load the ADD Services website by entering the ADD services URL in an internet browser. If you have access to the web server running IIS you can get the URL by looking at the ADD services site and clicking the "Browse Website" on the right.

 

If you see the following error when the page loads then use the next steps to correct it-

 

"Parser Error Message: Unrecognized attribute 'targetFramework'. Note that attribute names are case-sensitive."

 

[ATTACH=CONFIG]n1951[/ATTACH]

 

 

In order to fix this, you have to change the Application Pool settings in IIS:

-Check the .NET framework version for the ADDSrvAppPool in IIS under basic settings

 

[ATTACH=CONFIG]n1950[/ATTACH]

-change the value in the dropdown from v2.0 to v4.0

-recycle the app pool and then eCapture should start normally.

 

Link to comment
Share on other sites

  • 1 month later...
  • IPRO Employee

In addition, please check time sync between the Controller and the ADD Services (nucleus) webserver.

 

Often times, the time sync will be more than 5 seconds off, causing an invalid session token when trying to work with ADD Services.

 

The error you would typically see for this would be in the eCapture Controller log with the statement 401: Unauthorized.

 

This may also effect other eCapture components. The ADD webserver, Authorization service server, and eCapture component servers must ALL be on the same time (down to the second).

 

 

Link to comment
Share on other sites

  • IPRO Employee

In addition, please check time sync between the Controller and the ADD Services (nucleus) webserver.

 

Often times, the time sync will be more than 5 seconds off, causing an invalid session token when trying to work with ADD Services.

 

The error you would typically see for this would be in the eCapture Controller log with the statement 401: Unauthorized.

 

This may also effect other eCapture components. The ADD webserver, Authorization service server, and eCapture component servers must ALL be on the same time (down to the second).

 

 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...