Question

COnnector 10

Connector

Updated October 4, 2016

asked on September 27, 2016

A customer has the connector and has it integrated into a program. One specific PC errors out with the error message that states could not read the value of the specified control, token '%(order number)'. If you goes to another PC and runs the search it works fine. Any one have this issue before?

0 0

Replies

replied on September 27, 2016

Do the machine's have the same operating systems?

0 0

View 1 previous reply

replied on September 27, 2016

Is the issue user specific? If you have the user from the other machine login to the problem machine, do you get the same behavior or does it work for this other user?

0 0

replied on September 27, 2016

Another user can log into that pc and the issue remains

0 0

replied on September 28, 2016

So Connector does not work for any user on the machine? Have you tried to simply recreate the profile?

0 0

replied on September 27, 2016

Check to make sure both Connector and the program you are using with connector are in the both same user context. If your program is launched with run as administrator and connector is not, it will not find data.

0 0

replied on September 28, 2016

It' isn't it is using their normal user account

0 0

replied on September 28, 2016

A case has been opened with Laserfiche Support. The thread will be updated when a resolution is found.

0 0

replied on September 28, 2016

After creating the profile fresh on one of the machines, the new profile was able to run without issue. Comparing this new profile to the existing one, the control path for the token in question differed. The original profile was created on Windows Server 2008 R2 operating system so it seems that OS difference may have accounted for this behavior.

1 0

replied on October 4, 2016

Addendum: After further investigation in the case, it seems that the difference in operating system did not wholly (if at all) account for the error in failing to read the control.

The profile would work on a machine where it had been created, but not on another machine of the same operating system (Windows 7).
From comparing the XML of the control structure between these two machines, it seems that the "working" machine had an additional panel which seemed to correspond to a split view on the original machine when the profile was created, which was the case for most machines on the system.
From looking at the control path in the profile XML, the XPath was navigating based on counts of the elements.

Thus Connector was getting thrown off by the absence of the one element and was not finding the control correctly. To remedy this situation we were able to identify the control that was supposed to be found, and choose an XPath that identified it directly, without using counts of the intervening elements along the path.

2 0

You are not allowed to follow up in this post.

Question

Question

COnnector 10

Replies

Sign in to reply to this post.