New Data Shortcut Project in ProjectWise

[randyspear6624]

I updated to Civil 3D 2018.3.2 and since then I have not been able to create a DS project in PW. It appears to only create locally. However, if I use the PW's DS import from the ribbon or in their DS editor, it says there's no valid projects. I'm pretty sure it's DS project C3D is creating is corrupt.

I've tried this on PW versions .262, .298, & .334 with no luck.

Has anyone else noticed this?

[Joe-Bouza]

Hi Randy

I assume you are using PW to create the DS project? I have had no issues in the 2017 version and was told the PW for 2018 is leaps and bounds better.

[randyspear6624]

I've used 2018 for quite some time without issues beside the usual civil 3d lag and it not playing nice with my graphics card. I can only assume the 3.2 update is the culprit.

[dave.cumming]

Sorry I'm a year late here... Just came across this. Sounds like you needed to reinstall ProjectWise. Or if you were on an older version, upgrade to a newer version of ProjectWise. Hope you were able to figure it our last year, but if you are still having trouble, let me know. 

[randyspear6624]

We've reinstalled everything and kept up to date with PW versions with no luck.

I have a work around that isn't terrible.... I created an empty DS project in my Civil 3D Projects on my C drive. I had to select "from disk" when creating opposed letting PW attempt  to create a project  (even though it still creates a local one in the dms folders). Now when I use PW's DS import tool, it recognizes the DS project created locally.

Hopefully we can move away from Civil 3D 2018 soon... the "end of life bugs" are causing me a ton of downtime.

[denis.erlich.hatch]

Joseph, good afernoon.

I have exactly same issue, reinstalled 3 times both C3D and PW with ACAD Integration ( I have C3D 2022.1.2 and PW 10.00.03.453;

issue being: I am logged in PW in C3D and have file open in C3D from projectwise with all the integration prompts while opening the file from PW;  have ProjectWise integration installed and enabled; able to open datashortcut project from integration menu and otherwise from just simple "Set Working Folder" interface- that opens PW folder (not local); and once i click on "New Datashortcuts Project Folder" command, the only place it creates the DSFolder is in my dms C drive location. no prompts for checkin the *.proj file into Projectwise. 

I also used Uninstall tool and removed autodesk C3D this way;

I even used custom registry and file removal patches that have been developed by our Automation team:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\AutoCAD\R20.1\ACAD-F001:409\Applications\ProjectWise]
"LOADER"="C:\\Program Files\\Autodesk\\ApplicationPlugins\\ProjectWiseIntegrationAddIn\\idacad20_1odma.arx"
"LOADCTRLS"=dword:00000002

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\AutoCAD\R20.1\ACAD-F001:409\Applications\ProjectWiseMgd]
"LOADER"="C:\\Program Files\\Autodesk\\ApplicationPlugins\\ProjectWiseIntegrationAddIn\\idodma20_1mgd.dll"
"LOADCTRLS"=dword:00000004
"MANAGED"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Autodesk\AutoCAD\R20.1\ACAD-F001:409\Applications\ProjectWiseMgd\Commands]
"sfm"="sfm"
"DMSSESSIONFILEMANAGER"="DMSSESSIONFILEMANAGER"
"DMSPLACEONSHEET"="DMSPLACEONSHEET"

also replaced these files:

..\Program Files\Autodesk\ApplicationPlugins\ProjectWiseIntegrationAddIn\

idacad20_1civil.arx

idacad20_1odma.arx

idacad20_1tb.arx

idodma20_1mgd.dll

Interop.ACSMCOMPONENTS20Lib.dll

..\ProgramData\Bentley\ProjectWise\10.00\AutoCAD\support\en\

idacad20_1menu.cuix

idacad20_1menu.dll

idacad20_1menu.mnr

idacad20_1menu_light.mnr

Mind you, that is is not a problem for colleague of mine, that happily installed his C3D and Integration on his machine from first try and does have ability to create new datashortcut project folder ( PW asks in a prompt for it to be created, and we see this project being created in the PW within several seconds)

[dave.cumming]

Hi Denis,

There are a few things that come to mind, but let’s start by double checking your workflow…

Before we jump into that, note that the Registry hacks you posted are all R20.1 which is related to AutoCAD 2016. AutoCAD 2022 would use R24.1

Workflow Sanity Check:

Straight out of the box, ProjectWise-Integrated Civil 3D will look like this when you try to create a New Data Shortcut Project Folder

So the first thing you need to do is Set Working Folder

This should result in a prompt for ProjectWise Datasource Log In

Once you have logged into your ProjectWise datasource, you will be asked to choose a folder which will become your Civil 3D Working Folder. This is where the New Data Shortcut Project Folder will be created. Note that once it is created, the name that you give it will become the name of a file with a .CivilDSProj file extension.

For this example, I’ve chosen _L00_CivilDSProj as my Working Folder

Now that the Civil 3D Working Folder has been selected from a location in ProjectWise, you should be able to create the New Data Shortcut Project in that location.

Right-click again on the Data Shortcuts node from the Prospector and this time when the New Data Shortcut Folder dialog box pops up, the Working Folder should be pointing at the location that you selected in the previous step.

It should be apparent that it is integrated with ProjectWise because the directory path will begin with pw:\\

Be sure that you are not using special characters in your naming convention, and keep the name short.

Civil 3D doesn't like long directory paths so the shorter you keep your Data Shortcut and Data Shortcut Project names, the better. 

If you are following this same workflow and it does not yield the same result, let me know. 

[dave.cumming]

Hi Randy, 

I'm sorry I'm confused by your workflow and your workaround. 

I've posted the correct workflow that you should be using to create a new (ProjectWise-Integrated) Data Shortcut Project. Please let me know if that helps. 

The Import Data Shortcut Project feature on the ProjectWise Ribbon is a tool that is designed to migrate an existing Civil 3D DSP into ProjectWise. Running it will involve pointing it at a the C3D Working Folder that is on your network drive. It will also prompt you to import all of the source drawings being used for that DSP. 

I'm not really sure if (or how) your Data Shortcut Project is integrated with ProjectWise. Do you have a .CivilDSProj file in ProjectWise? If you open it with the ProjectWise Data Shortcut Project Editor, does it contain a record of all your data shortcuts? 

[denis.erlich.hatch]

Dave, thank you for quick reply.
Yes I followed the procedure exactly.
after "New Datashortcuts Project Folder" step the folder just being created in dms, but not propagated into ProjectWise. same step on my colleague's machine generates prompt to put .proj file to Projectwise and generates it there ( in addition to dms folder)

[dave.cumming]

OK Denis, Thanks for double checking that. Let's have a call and get this sorted. 

Please DM me so we can set up a time to do a screen share. 

We can circle back around to this forum and provide an update to the C3D community after we investigate further. 

dave.cumming@bentley.com

[randyspear6624]

Hey Dave, my workaround is essentially that... a workaround. I agree, what you posted in your screenshots is how the process is supposed to work but like others on here, something is broken and reinstalling/updating isn't fixing it.

It's been awhile so just to reiterate, the issue is creating the initial civilDSproj file... it doesn't.

Yes, the import data shortcut tool is for existing DS projects. I have a blank one set up locally. When I use the import tool, it doesn't import any dwgs because there aren't any assoicated with it yet. Once imported, the civilDSproj file is created and I'm able to work integrated in PW as usual.

We are on 2018. Moving to 2022 soon. Hopefully things get better then.

[dave.cumming]

After working with a user having very similar issues, I finally had a chance to do some testing in the native ProjectWise environment where this issue was occurring.

Long story short, the issue was with the number of characters in the ProjectWise folder path that was used to define the C3D Working Folder (the folder that contains the .CivilDSProj file). 

To be clear, I do not mean the ProjectWise Working Directory ("dms") folder location. 

When you set the Civil 3D Working Folder, you should be navigating the ProjectWise folder tree, and when you select the folder that contains (or that will contain) your .CivilDSProj file, that location is set with the ProjectWise path which looks like this  pw:\\<server name>\<datasource name>\<path>

It should not be pointing at your local (Windows) directory. 

You can see examples of this in my earlier post that outlines the entire workflow. 

If the ProjectWise Working Folder location is too long (presumably >255 characters) then Civil 3D will revert to the local "dms" folder location. 

Credit to the user that I was working with. He actually noticed this. I just tested his theory 🙂

Hope it helps you guys. And if not, let me know. 

[frank.cortesWRCXM]

Hi Dave,

I have a very similar issue with ProjectWise integration, the data shortcut is only created in local disk but the .CivilDSProj is not update. Actually each time a designer want to create a new shortcut has to create a new working folder ‘’ DSProj because this file can not actually not be updated.  it seems impossible to associate more than one source drawing to a single DSProj. File. Any advice?

Frank

[dave.cumming]

Hi Frank, I just sent you a private message on this forum. Please DM me at the e-mail address that I provided, and I can help you with this.

Thanks. 

[dave.cumming]

Frank, I took a look at some recently created .CivilDSProj files in your datasource and the issue is that the full file path exceeds the maximum character count threshold that Civil 3D can handle. 

For a fully detailed explanation, please scroll up and take a look at Messages #7 (04-01-2022) and #12 (06-17-2022)