In our 3 user environment, and this has not shown up at either of the other two users.

However, we ran into this issue with my computer, see attached image.
Anyone who might have seen this issue and have any solutions please help.

I have no issues checking parts out
I can edit parts, I just cannot check things back into the vault, nor update the revision level.

Have you done an upgrade recently?
What version/build of Pro/E and Intralink are you runnung?

"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

Intralink 3.4
Pro/E Wildfire 3.0

The software was recently installed on my machine, and we have tried to clean uninstall then re-install without much success.

I am guessing you have a corrupt workspace.
Rename the top level file of your workspace and then restart Intralink to create a new workspace.

"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

Have tried to rename or even delete and make a new work space, but no matter, as it just comes back to the same error.
We tried logging in as a different user, creating his own workspace and still no help. When I log in from his computer, this error does not show up at his computer either.

Is your computer in a different domain on the network from the others?
Do you all have the same IP address for the first 3 number sets?
Can you ping the file server and data server from your workstation?

Have you contacted PTC Tech Support or at least seached the knowledgebase?

"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

Title When Opening the Workspace, the Following Message is Displayed in the Name Column: "The Workspace File LDB has Domain Name/Id Different from those being Assigned is Invalid."
Details Additional Information
Description
-----------------
After logging into the client and activating a workspace, the following message is displayed in the Name Column "The Workspace File LDB has Domain Name/Id Different from those being Assigned is Invalid."

Alternate Technique
-----------------
To workaround this problem, please delete or rename the current .proi-directory and relaunch the client.

Resolution
-----------------
Software is working to specification. LDB (local.ddb, located in the .PROI directory) should correspond to one Commonspace, identified by its Domain ID (CSID). Note that if a CSID is not already configured in the database, it is automatically generated during the upgrade to Pro/INTRALINK 3.3.

Thus, the message will be displayed if trying to use the same .PROI directory after switching between dataservers with different Commonspaces IDs.

"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

^ We got it running, many thanks!