When I want to start Team Dashboard I get an error message (see below). This started two weeks ago. I never had problems accessing this project before. When I use a Windows Explorer to look at this directory everything seems to be there.
Kind regards, Pascal
---snip---
Team Data Directory Missing
The team planning tools need access to the team data directory for this project. According to your current project settings, that directory is
\xxx\yyy\zzz\ProcessDashboard\data\i2yiu31s
Unfortunately, this directory does not appear to exist. Check to make certain that the directory is accessible and try again.
---snip---
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Try highlighting the path it's complaining about, copying to the clipboard, and pasting into the location field of Windows Explorer. Chances are, there is some subtle difference in the directory names that is hard to spot (for example, a space between the words "Process" and "Dashboard"). If you find such a problem, correct the path on the Team Project Parameters and Settings page.
Alternatively, it's possible that network permissions are misbehaving; sometimes a Windows network credential can become stale. Logging out and logging back in might help.
Also, I can't tell from what you've shown above whether the team directory path is specified with a drive letter or a UNC path. The format shown above is neither, and is technically an invalid/ambiguous path. If the directory is on the network, a UNC path is best; UNC paths start with two backslashes (e.g. \\xxx\yyy\zzz\etc). If the directory is mapped as a drive, you should be specifying the drive letter in the path (e.g. T:\xxx\yyy\zzz\etc.) What you've shown above is neither, but I can't guess whether that's an artifact of having edited the text to replace words with "xxx".
Last edit: David Tuma 2015-03-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I copy the path to Windows Explorer and get the corresponding directory.
Log out/in did not improve the behavior.
Sure, I should state that I have a UNC path. In fact there are three projects:
\ComputerName\SharedFolder\ProcessDashboard\data\ResourceWorksFine
\ComputerName\SharedFolder\ProcessDashboard\data\ResourceWorksFine
\ComputerName\SharedFolder\ProcessDashboard\data\ResourceProducesErrorMessage
Two of them can be accessed, the third one cannot.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If two of the directories are working fine and the third is not, then it is almost certainly an issue with filesystem permissions. Examine the permissions on the three directories in question, and see how the problematic directory differs from the others. For example, the directory may be owned by a different individual and/or access may be granted differently to different groups.
Adjust the ACLs on the problematic directory so they match the directories that are working; also make certain to apply these changes recursively to all files and subfolders; and make certain to arrange that newly created objects will inherit these permissions.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No, a missing team-data.pdash file will not be the cause of any problem. It could possibly be a symptom of your underlying filesystem problem.
Check ALL of the filesystem permissions: on the abcd1234 directory that is causing the problem; on the files within that directory; and on the "backup" and "disseminate" subdirectories. Or you could just perform a recursive apply as I suggested in my last post.
And as I mentioned before, make certain you configure these permissions to be inherited by new objects. This is a very common reason people see problems. Their permissions are not inheriting for some reason, then a person other than you opens the WBS and saves changes, and all the files they write get a bad set of permissions because the permissions aren't inheriting properly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
He leader of project should to use any computer for access to the WBS and perform them changes relevant, without be limited, that happens if is should change of PC? that can happen if is works in MAC OS, Linux? : O so create a folder for fault projects addressing UNC (\servidor\directorio) or /Volumes/directorio. If is are storing the data of TSP and PSP local and the project is in another directory external (server: port) them data them stores local and is complex that another machine external them see, NETBIOS is great if only is are in MS Windows. Please consider all this and think that there are people and startup that can use your tool. Thanks for all your help.
El lider de proyecto debe poder utilizar cualquier computadora para acceder a la WBS y realizar los cambios pertinentes, sin estar limitado , que pasa si se debe cambiar de PC? que pasa si se trabaja en MAC OS, Linux? :O así se cree una carpeta para los proyectos falla el direccionamiento por UNC (\servidor\directorio\ ) o /Volumes/directorio/. si se están almacenando los datos de TSP y PSP local y el proyecto esta en otro directorio externos (servidor:puerto) los datos los almacena locales y es complejo que otra maquina externa los vea, NETBIOS es genial si solo se estan en MS Windows. Por favor considerar todo esto y pensar que hay personas y startup que pueden usar su herramienta. Gracias por toda su colaboración.
The team files can be stored on either a Windows server or a Mac/Unix/Linux server. But you must configure the server directory properly, to ensure that team members have permission to alter the files. This is explained in the help in http://www.processdash.com/static/teamhelp/frame.html?TeamConfigDir
This approach was created because a shared network directory is a simple service that can be made available in virtually any organization.
If you are having trouble with the shared directory approach, you might consider the Process Dashboard Enterprise Server. I created it to help organizations that are having the exact types of problems you're struggling with. You can read about it here: http://www.processdash.com/pdes-team
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I want to start Team Dashboard I get an error message (see below). This started two weeks ago. I never had problems accessing this project before. When I use a Windows Explorer to look at this directory everything seems to be there.
Kind regards, Pascal
---snip---
Team Data Directory Missing
The team planning tools need access to the team data directory for this project. According to your current project settings, that directory is
\xxx\yyy\zzz\ProcessDashboard\data\i2yiu31s
Unfortunately, this directory does not appear to exist. Check to make certain that the directory is accessible and try again.
---snip---
Try highlighting the path it's complaining about, copying to the clipboard, and pasting into the location field of Windows Explorer. Chances are, there is some subtle difference in the directory names that is hard to spot (for example, a space between the words "Process" and "Dashboard"). If you find such a problem, correct the path on the Team Project Parameters and Settings page.
Alternatively, it's possible that network permissions are misbehaving; sometimes a Windows network credential can become stale. Logging out and logging back in might help.
Also, I can't tell from what you've shown above whether the team directory path is specified with a drive letter or a UNC path. The format shown above is neither, and is technically an invalid/ambiguous path. If the directory is on the network, a UNC path is best; UNC paths start with two backslashes (e.g.
\\xxx\yyy\zzz\etc). If the directory is mapped as a drive, you should be specifying the drive letter in the path (e.g. T:\xxx\yyy\zzz\etc.) What you've shown above is neither, but I can't guess whether that's an artifact of having edited the text to replace words with "xxx".Last edit: David Tuma 2015-03-09
I copy the path to Windows Explorer and get the corresponding directory.
Log out/in did not improve the behavior.
Sure, I should state that I have a UNC path. In fact there are three projects:
\ComputerName\SharedFolder\ProcessDashboard\data\ResourceWorksFine
\ComputerName\SharedFolder\ProcessDashboard\data\ResourceWorksFine
\ComputerName\SharedFolder\ProcessDashboard\data\ResourceProducesErrorMessage
Two of them can be accessed, the third one cannot.
If two of the directories are working fine and the third is not, then it is almost certainly an issue with filesystem permissions. Examine the permissions on the three directories in question, and see how the problematic directory differs from the others. For example, the directory may be owned by a different individual and/or access may be granted differently to different groups.
Adjust the ACLs on the problematic directory so they match the directories that are working; also make certain to apply these changes recursively to all files and subfolders; and make certain to arrange that newly created objects will inherit these permissions.
Filesystem permissions do not show relevant differences.
But I found out that in the problematic directory in subdirectory "disseminate" the file "team-data.pdash" is missing. Could this be the reason?
No, a missing team-data.pdash file will not be the cause of any problem. It could possibly be a symptom of your underlying filesystem problem.
Check ALL of the filesystem permissions: on the abcd1234 directory that is causing the problem; on the files within that directory; and on the "backup" and "disseminate" subdirectories. Or you could just perform a recursive apply as I suggested in my last post.
And as I mentioned before, make certain you configure these permissions to be inherited by new objects. This is a very common reason people see problems. Their permissions are not inheriting for some reason, then a person other than you opens the WBS and saves changes, and all the files they write get a bad set of permissions because the permissions aren't inheriting properly.
He leader of project should to use any computer for access to the WBS and perform them changes relevant, without be limited, that happens if is should change of PC? that can happen if is works in MAC OS, Linux? : O so create a folder for fault projects addressing UNC (\servidor\directorio) or /Volumes/directorio. If is are storing the data of TSP and PSP local and the project is in another directory external (server: port) them data them stores local and is complex that another machine external them see, NETBIOS is great if only is are in MS Windows. Please consider all this and think that there are people and startup that can use your tool. Thanks for all your help.
El lider de proyecto debe poder utilizar cualquier computadora para acceder a la WBS y realizar los cambios pertinentes, sin estar limitado , que pasa si se debe cambiar de PC? que pasa si se trabaja en MAC OS, Linux? :O así se cree una carpeta para los proyectos falla el direccionamiento por UNC (\servidor\directorio\ ) o /Volumes/directorio/. si se están almacenando los datos de TSP y PSP local y el proyecto esta en otro directorio externos (servidor:puerto) los datos los almacena locales y es complejo que otra maquina externa los vea, NETBIOS es genial si solo se estan en MS Windows. Por favor considerar todo esto y pensar que hay personas y startup que pueden usar su herramienta. Gracias por toda su colaboración.
The team files can be stored on either a Windows server or a Mac/Unix/Linux server. But you must configure the server directory properly, to ensure that team members have permission to alter the files. This is explained in the help in http://www.processdash.com/static/teamhelp/frame.html?TeamConfigDir
This approach was created because a shared network directory is a simple service that can be made available in virtually any organization.
If you are having trouble with the shared directory approach, you might consider the Process Dashboard Enterprise Server. I created it to help organizations that are having the exact types of problems you're struggling with. You can read about it here: http://www.processdash.com/pdes-team