• State Verified Answer
  • Replies 2 replies
  • Subscribers 57 subscribers
  • Views 2798 views
  • Users 0 members are here

Autodesk Civil 3D integration user working directory setting

Kevin
Offline

Hello,

We currently use the default working folder setting for users. The users login name is included in the path. This makes sense, if different users use the same workstation, then each user has their own local working directory.

We are also trying to use Project Wise integratio9n with Civil 3D.

We encounter 2 problems:

.1 - Time to open DWG files take longer as we proceed with design work. We typically use hundreds of data shortcuts. It looks like, the more data shortcuts you have, the longer it takes for the integration to make the DWG available. Wait times are getting bad, well over 5 minutes to open a DWG.

.2 - Sometimes, for some unknown reason, the data shortcuts become broken. It takes about an hour to make them again; production is held up while the data shortcuts are recreated.

Will it help to just remove the login name from the working directory path? Then the paths will be constant, the same for all users.

Has anyone already done this?

We are not sure what to do, but we cannot continue this way.

Thanks for reading,

Kevin.

Parents
  • 0 Offline
    Issued an SR (7000371286) ... received excellent feedback from Bentley ...

    It would not suggest allowing the users to have the same working directory to resolve the performance issues. Having the same working directory will introduce other problems that are worse.
    I'd recommend we start by trying to understand why it is slow. If you have not yet had a chance to review the documentation on how ProjectWise is managing the datashortcut references, I've provided the links below. I highly recommend taking the time to review the documentation so understand how ProjectWise integration is managing datashortcuts.
    In my experience the number 1 cause of performance issues with datashortcuts are circular references. Use the dependency viewer in ProjectWise to view the Civil 3D project to see if the project has circular referencing. This slows down ProjectWise because it processes the same file more than it has to. If you notice the Dmskrnl.exe process spiking when opening the project, this is the reason. I have a SQL script that will temporarily solve the problem but the real solution is to clean up the project and remove the circular references.
    If you don't think the issue mentioned above is the case, I'd want to review the verbose logging from a client machine and the server. Below are the steps for turning up the logs.
    Training/Learning
    Training Videos: learn.bentley.com/.../ViewLearningPathDetails
    ProjectWise and Civil 3D FAQ: communities.bentley.com/.../download.aspx
    ProjectWise and Civil 3D Green Book: communities.bentley.com/.../greenbook-_2D00_-projectwise-civil-3d-advanced-integration.pdf

    Implementation Files
    Civil 3D AppInfo XML: communities.bentley.com/.../download.aspx
    Civil 3D DS Proj MIME Mapping: communities.bentley.com/.../download.aspx

    To turn up logging on the Gateway/Caching/Integration Server
    1. On the server go to C:\Program Files\Bentley\ProjectWise\bin and open dmskrnl.log.xml in notepad
    2. Select ctrl+h to find and replace. In the "Find What" field enter "warn" (with the quotes). In the "replace with" field enter "all" (with the quotes). Select "Replace All"
    3. Close the find and replace dialog
    4. Example:
    <category name="pwise.system"> <priority value="all"/>
    5. Save the file and exit
    6. The log file will be written to:
    Windows 2003: C:\Documents and Settings\All Users\Application Data\Bentley\Logs\dmskrnl.log
    Windows 2008: C:\Users\Public\Bentley\Logs

    To turn up logging for ProjectWise Explorer
    1. Go to C:\Program Files\Bentley\ProjectWise\bin and open pwc.log.xml in notepad
    2.
    o Also repeat these steps under C:\Program Files (x86) if this is a 64 bit machine
    3. Select ctrl+h to find and replace. In the "Find What" field enter "warn" (with the quotes). In the "replace with" field enter "all" (with the quotes). Select "Replace All"
    4. Close the find and replace dialog
    5. Select ctrl+f to find. In the "find what" field, enter "hook" (without the quotes). This should take you to the line that looks like this:
    <category name="pwise.hook"> <priority value="all"/></category>
    5. Change the priority value to warn. We want to turn up the log levels to all for everything except pwise.hook.
    6. Save the file and close it.
    7. The log file will be written to:
    Win 7 - C:\Users\<Current User>\AppData\Local\Bentley\Logs\pwc.log

    To turn up logging for the Integration Application issues:
    1. Go to C:\Program files\Bentley\ProjectWise\bin and open odma.log.xml in notepad.
    2. Select ctrl+h to find and replace. In the "Find What" field enter "warn" (with the quotes). In the "replace with" field enter "all" (with the quotes). Select "Replace All"
    3. Close the find and replace dialog
    4. Select ctrl+f to find. In the "find what" field, enter "hook" (without the quotes). This should take you to the line that looks like this:
    <category name="pwise.hook"> <priority value="all"/></category>
    5. Change the priority value to warn. We want to turn up the log levels to all for everything except pwise.hook.
    6. Save the file and close it.
    7. The log file will be written to
    Win XP - C:\Documents and Settings\user.name\Application Data\Bentley\Logs\odma.log.
    Win 7 - C:\Users\<Current User>\AppData\Local\Bentley\Logs\odma.log
Reply
  • 0 Offline
    Issued an SR (7000371286) ... received excellent feedback from Bentley ...

    It would not suggest allowing the users to have the same working directory to resolve the performance issues. Having the same working directory will introduce other problems that are worse.
    I'd recommend we start by trying to understand why it is slow. If you have not yet had a chance to review the documentation on how ProjectWise is managing the datashortcut references, I've provided the links below. I highly recommend taking the time to review the documentation so understand how ProjectWise integration is managing datashortcuts.
    In my experience the number 1 cause of performance issues with datashortcuts are circular references. Use the dependency viewer in ProjectWise to view the Civil 3D project to see if the project has circular referencing. This slows down ProjectWise because it processes the same file more than it has to. If you notice the Dmskrnl.exe process spiking when opening the project, this is the reason. I have a SQL script that will temporarily solve the problem but the real solution is to clean up the project and remove the circular references.
    If you don't think the issue mentioned above is the case, I'd want to review the verbose logging from a client machine and the server. Below are the steps for turning up the logs.
    Training/Learning
    Training Videos: learn.bentley.com/.../ViewLearningPathDetails
    ProjectWise and Civil 3D FAQ: communities.bentley.com/.../download.aspx
    ProjectWise and Civil 3D Green Book: communities.bentley.com/.../greenbook-_2D00_-projectwise-civil-3d-advanced-integration.pdf

    Implementation Files
    Civil 3D AppInfo XML: communities.bentley.com/.../download.aspx
    Civil 3D DS Proj MIME Mapping: communities.bentley.com/.../download.aspx

    To turn up logging on the Gateway/Caching/Integration Server
    1. On the server go to C:\Program Files\Bentley\ProjectWise\bin and open dmskrnl.log.xml in notepad
    2. Select ctrl+h to find and replace. In the "Find What" field enter "warn" (with the quotes). In the "replace with" field enter "all" (with the quotes). Select "Replace All"
    3. Close the find and replace dialog
    4. Example:
    <category name="pwise.system"> <priority value="all"/>
    5. Save the file and exit
    6. The log file will be written to:
    Windows 2003: C:\Documents and Settings\All Users\Application Data\Bentley\Logs\dmskrnl.log
    Windows 2008: C:\Users\Public\Bentley\Logs

    To turn up logging for ProjectWise Explorer
    1. Go to C:\Program Files\Bentley\ProjectWise\bin and open pwc.log.xml in notepad
    2.
    o Also repeat these steps under C:\Program Files (x86) if this is a 64 bit machine
    3. Select ctrl+h to find and replace. In the "Find What" field enter "warn" (with the quotes). In the "replace with" field enter "all" (with the quotes). Select "Replace All"
    4. Close the find and replace dialog
    5. Select ctrl+f to find. In the "find what" field, enter "hook" (without the quotes). This should take you to the line that looks like this:
    <category name="pwise.hook"> <priority value="all"/></category>
    5. Change the priority value to warn. We want to turn up the log levels to all for everything except pwise.hook.
    6. Save the file and close it.
    7. The log file will be written to:
    Win 7 - C:\Users\<Current User>\AppData\Local\Bentley\Logs\pwc.log

    To turn up logging for the Integration Application issues:
    1. Go to C:\Program files\Bentley\ProjectWise\bin and open odma.log.xml in notepad.
    2. Select ctrl+h to find and replace. In the "Find What" field enter "warn" (with the quotes). In the "replace with" field enter "all" (with the quotes). Select "Replace All"
    3. Close the find and replace dialog
    4. Select ctrl+f to find. In the "find what" field, enter "hook" (without the quotes). This should take you to the line that looks like this:
    <category name="pwise.hook"> <priority value="all"/></category>
    5. Change the priority value to warn. We want to turn up the log levels to all for everything except pwise.hook.
    6. Save the file and close it.
    7. The log file will be written to
    Win XP - C:\Documents and Settings\user.name\Application Data\Bentley\Logs\odma.log.
    Win 7 - C:\Users\<Current User>\AppData\Local\Bentley\Logs\odma.log
Children
No Data
Communities
Support and Services
Training and Learning
Social Media