Error Checking In Document

RE: Error Checking In Document

Matt Kovach — Tue, 07 Jun 2022 12:31:45 GMT

Hello Mark,

I have submitted a Support Request for this, and included Log Files to the Support Specialist. Waiting to hear back. I am hopeful that a Defect Item/Number will be created from this.

RE: Error Checking In Document

Mark Shamoun — Tue, 07 Jun 2022 09:05:40 GMT

Hi Matt, did you end up getting a defect logged for this?

RE: Error Checking In Document

Daniel Talevski — Tue, 07 Jun 2022 04:27:52 GMT

Hi Matt - I have also been experiencing issues with the check in dialog and general checking in DGNs on PW. Thank you - this post and XS kill helped me resolve this issue. Sounds like an ORD bug to me...

RE: Error Checking In Document

Matt Kovach — Wed, 25 May 2022 14:54:27 GMT

Yes sir.

RE: Error Checking In Document

Kevin van Haaren — Wed, 25 May 2022 14:53:06 GMT

did you test both ORD 10.9 and 10.10.21?

RE: Error Checking In Document

Matt Kovach — Wed, 25 May 2022 12:35:24 GMT

UPDATE:

After several hours of testing multiple data sets from multiple computers, it would appear that the culprit for this uninformative message (and error) is active/opened Dynamic Cross Section Views. If one leaves an OpenRoads Designer Design File with a Dynamic Cross Section View active/opened before closing the File, there is a good chance that you will see the above referenced error, with a bonus of not being able to Check In the Document (Status = Coming In). While we have been able to reproduce the issue almost in every instance/attempt, some OpenRoads Designer Design Files don't seem to have a problem with active/opened Dynamic Cross Section Views. So, perhaps these views are going corrupt somehow? While we have no "bulletproof" way of proving this "Dynamic Cross Section Views can become corrupt" theory, we have seen some other strange, related issues (to Dynamic Cross Section Views).

SUGGESTION:

If you do not wish to contend with this problem, we recommend that you close and even delete your active/opened Dynamic Cross Section View before closing your OpenRoads Designer Design Files. To delete Dynamic Cross Section Views, use this key-in command: geometry dynamicsection deletedxsviews

RE: Error Checking In Document

Matt Kovach — Wed, 11 May 2022 15:03:56 GMT

Thank you Kevin! This is a good share.

As for the workflow I used to enable logging and capture relevant information, I performed the steps just as you have described, except for deleting the log file before the user opened/worked in their Bentley Design File, since the issue is not reproduceable on demand. I did, however, delete existing log files after turning up the logging. So, the user started from a clean-ish slate (it didn't take too much time for the error to rear its ugly head again).

RE: Error Checking In Document

Kevin van Haaren — Tue, 10 May 2022 22:08:07 GMT

Does this happen to all files you have checked out or just the one? Can you copy new files in?

There is a little bit of an art to reading log files, you can't just look at the last few errors and see what is happening, and frequently you need to increase the logging information so you can see what was happening before the error itself occured.

The format of the log file (for pwc.log) is

Date/Time MessageLevel [ThreadNum] category - message

you can use the thread number to follow back the actions that were tied to a particular error. The category is useful for identifying which section of PW the problem is in.

I've found the pwise.netapi messages to be impossible to read/understand so day to day i keep that at the Fatal level. I'll lower it if i've nothing else to look at or want to send it to bentley.

pwise.socket category is good if you thing there is a network problem, but you need to run it at the info level to see what it was attempting to do on the network when the error occurred. the info level will tell you which server it was attempting to connect to and the port it was using, and how far into the transaction it got.

I set the pwise.database level to info so i can see the exact database queries that are being sent and if they succeeded.

In order to generate a more readable log file, I will:

Close projectwise
adjust log levels in the pwc.log.xml file
delete the pwc.log file
Open Projectwise
do the exact actions that cause the problem, so here check out a file, draw some lines, close ORD, check in the file.
close projectwise
open the pwc.log file, go to the end and start tracing backwards to find what was happening before the error occurred

RE: Error Checking In Document

Matt Kovach — Tue, 10 May 2022 12:39:23 GMT

Kevin,

I'm seeing a variety errors in the pwc.log File:

2022-05-06 16:43:53,007 ERROR [0x0000bca4] pwise.socket - Error -10054 on socket 2412 at func: socket_sendData line: 1378
2022-05-06 16:43:53,007 ERROR [0x0000bca4] pwise.netapi - Error -11502 "failed to send client request" reported at func: request_sendClientRequest2 line: 621
2022-05-06 16:46:25,348 ERROR [0x0000bca4] pwise.dms - Request 6400 return code 20188. Response size: 0

To me, these say nothing to aid in determining what causes the error/issue.

I'm also seeing these errors in the mcmintgr.log File:

2022-05-06 15:26:30,148|ERROR|0x0000c278|pwise.dms|Request 7800 return code -11702. Response size: 0
2022-05-06 15:26:32,860|ERROR|0x0000c278|pwise.MCM.DmsUtil|MCMDMSUtil::GetProjectInfoFromPathString @ e:\Builds\pw100003453\Source\dms\integration\ustation\mcm\v1000\mcmdmsutil.cpp:567 - Failed to find the file C:\FDOTConnect10.10\. Project information could not be retrieved!
2022-05-06 15:26:32,873|ERROR|0x0000c278|pwise.MCM|pwims::GetExpandedCfgVar @ e:\Builds\pw100003453\Source\dms\integration\ustation\common\v9\CfgVarUtils.cpp:69 - Invalid parameter passed to function.

The bolded line item makes no sense. The C:\FDOTConnect10.10\ path is the root of the WorkSpace Path (not managed) and DOES exist. So, it should have found it. Not sure what "Project information" that it is trying to retrieve and from where (i.e. which variable).

RE: Error Checking In Document

Kevin van Haaren — Mon, 09 May 2022 22:41:20 GMT

What does logging show? I'd check your pwc.log.xml file and make sure the following settings are set to 'all', then try and check in your document.

Just in case I'd also make a copy your document to your desktop or something so you have a backup.

    <!-- Messages related to file transfer operations (dmsft.dll). -->
    <category name="pwise.ft">                 <priority value="all"/></category>

    <!-- Messages related to ProjectWise DFT file transfer operations. -->
    <category name="pwise.ft.dft">              <priority value="all"/></category>

    <!-- Messages related to remote host name resolution. -->
    <category name="pwise.dns">                 <priority value="all"/></category>
    <category name="pwise.dns.cache">           <priority value="all"/></category>
    <category name="pwise.dns.local">           <priority value="all"/></category>

    <!-- Messages related to server discovery and connections. -->
    <category name="pwise.netapi.discovery">    <priority value="all"/></category>
    <category name="pwise.netapi.routecache">   <priority value="all"/></category>