Cannot open .project file

b I have a Turnkey installation of ES 801. It is running in a VM.
When I login to Workbench, the eclipse log records this exception (only the first few lines are listed, followed by the 'Caused by' line is listed below):
!ENTRY com.adobe.ide.singlesignon 4 4 2007-11-08 05:45:56.281
!MESSAGE login notification failed
!STACK 0
java.lang.IllegalStateException
at com.adobe.ide.singlesignon.IDESession.getProject(Unknown Source)
at com.adobe.ide.singlesignon.IDESession.getProject(Unknown Source)
Caused by: org.eclipse.core.internal.resources.ResourceException: The project description file (.project) for es801-trnkey-a 87.128 is missing. This file contains important information about the project. The project will not function properly until this file is restored.
b I also get this message when I attempt to access the repository. This is when I am browsing for a Tempplate URL when a new xfaForm process variable is being specified. Again only the first few lines of trace and the 'Caused by' line are listed.
!ENTRY com.adobe.workflow.editor 4 4 2007-11-08 06:14:10.531
!MESSAGE Failed to open repository picker dialog
!STACK 0
java.lang.IllegalStateException
Caused by: org.eclipse.core.internal.resources.ResourceException: The project description file (.project) for es801-trnkey-a 87.128 is missing. This file contains important information about the project. The project will not function properly until this file is restored.

Thank you Jasmin. The deletion of the workbench connection config and re-creation fixed the problem.
Are you aware of WorkBench documentation that is better then Creating First LiveCycle ES Application or WorkBench ES help?
I would like details relating to properties on the various actions one puts on the process design pallet for instance.
Thanks again!
Peter Bourke

Similar Messages

Cannot open project file with write access...

I have seen that this problem has been reported before but have yet to find a solution.
I have my project file in an external hard drive. When I plug the hard drive to another computer and want to save it I get this message:
"Cannot open project file with write access. The file may be locked or you don't have permission to write to this location. Select Save As..."
I don't want to Save As because other projects make reference to this file and also my Encore file will be messed up.
FYI both computers use Windows 7.
Any solutions?

Right click on the folder in Question and select properties. Then select the security tab. Make sure you add everyone to the user list. You do that by selecting edit and then add. Type in everyone in the object section and hit ok. Then select the everyone user and checkmark the Full control. Hit Apply and it will adjust the permissions for the folder and subfolders and files.
Eric
ADK

LV RTE cannot open project files that have .lvlib references in Dependencies

I'm writing a LabVIEW DLL to inspect LabVIEW project files, and I've noticed that if a project has a .lvlib reference in its Dependencies, then the Run-Time Engine contradicts itself about whether or not it can find the project file:
Project.Open returns error 7 (file not found)
Project.GetFileLVVersion is successful
Here are snippets from my G and C code that exercise this behavior:
int openStatus = StatusSuccess;
char* projectVersion = createStringWithLength(VersionStringLength);
printf("Analyzing %s\n", pathString);
OpenProject(pathString, &openStatus, projectVersion, VersionStringLength);
printf(" Project written in LabVIEW %s\n", projectVersion);
if (openStatus == StatusSuccess)
printf(" Opened project file.\n");
else
printf("Error: Could not find project file, or file was not a project file (error code %i).\n", openStatus);
However, when running in the development environment, both methods succeed.
Is this a bug, and if so, is it fixed in LabVIEW 2014?
Here is how you can reproduce it:
Prerequisites:
LabVIEW 2013 SP1 32-bit
ConEmu for a good console -- https://code.google.com/p/conemu-maximus5/wiki/Downloads
minGW for compiling a program to use the LabVIEW DLL -- http://sourceforge.net/projects/mingw/files
.lvlib reference in Dependencies breaks Project.Open in LV RTE
Unzip the attachment into a temporary directory (eg c:\xtra\temp)
Open "OpenProject.lvproj" in LabVIEW.
Build "Open Project Library".
Using ConEmu with a bash prompt, navigate to the temporary directory.
Type make
$ make
patching file `builds/platdefines.h'
gcc -std=c99 -g OpenProject.c -o OpenProject.exe -lOpenProject -Lbuilds
6. Type OpenProject 'c:\xtra\temp\OpenProject.lvproj'
$ OpenProject 'c:\xtra\temp\OpenProject.lvproj'
Analyzing c:\xtra\temp\OpenProject.lvproj
Project written in LabVIEW 13.0
Opened project file.
7. Notice that both invoke nodes execute correctly.
8. Type OpenProject 'c:\xtra\temp\OpenProjectWithLvlibDep.lvproj'
$ OpenProject 'c:\xtra\temp\OpenProjectWithLvlibDep.lvproj'
Analyzing c:\xtra\temp\OpenProjectWithLvlibDep.lvproj
Project written in LabVIEW 13.0
Error: Could not find project file, or file was not a project file (error code 7).
9. Notice that the version node succeeded while the open one failed.
10. Type diff OpenProject.lvproj OpenProjectWithLvlibDep.lvproj
$ diff -u OpenProject.lvproj OpenProjectWithLvlibDep.lvproj
--- OpenProject.lvproj Tue Nov 4 11:28:28 2014
+++ OpenProjectWithLvlibDep.lvproj Tue Nov 4 11:32:37 2014
@@ -13,7 +13,11 @@
<Property Name="server.vi.propertiesEnabled" Type="Bool">true</Property>
<Property Name="specify.custom.address" Type="Bool">false</Property>
<Item Name="OpenProject.vi" Type="VI" URL="../OpenProject.vi"/>
- <Item Name="Dependencies" Type="Dependencies"/>
+ <Item Name="Dependencies" Type="Dependencies">
+ <Item Name="vi.lib" Type="Folder">
+ <Item Name="NI_MABase.lvlib" Type="Library" URL="/<vilib>/measure/NI_MABase.lvlib"/>
+ </Item>
+ </Item>
<Item Name="Build Specifications" Type="Build">
<Item Name="Open Project Library" Type="DLL">
<Property Name="App_copyErrors" Type="Bool">true</Property>
Here is another way to trigger this behavior, which also shows that LabVIEW only sometimes tidies the Dependencies item:
Open "OpenProject.lvproj" in LabVIEW.
Add a new VI to the project and place the "Application Directory" file path constant its block diagram.
Select "File » Save All (this Project)" and use the default name for the new VI.
Type OpenProject 'c:\xtra\temp\OpenProject.lvproj'
Notice there is an error again, as is expected.
Remove the "Application Directory" file path constant.
Select "File » Save All (this Project)"
Type OpenProject 'c:\xtra\temp\OpenProject.lvproj'
Notice the problem is gone, as is expected.
Re-add the "Application Directory" file path constant to the block diagram.
Select "File » Save All (this Project)"
Type OpenProject 'c:\xtra\temp\OpenProject.lvproj'
Notice there is no problem, which is surprising as there should be an error since the Dependencies item hasn't been tidied.
Close the new VI and remove it from the project.
Select "File » Save All (this Project)"
Open "OpenProject.lvproj" in a text editor.
Notice the Dependencies item has been tidied.
Re-add the VI back to the project.
Select "File » Save All (this Project)"
Type OpenProject 'c:\xtra\temp\OpenProject.lvproj'
Notice there is an error again, as is expected.
Solved!
Go to Solution.
Attachments:
LVRTE_OpenProject.zip ‏10 KB

NInjaneer_wow wrote:
The same behavior occurs in LabVIEW RTE: a new project with an Application Directory constant in a blank vi will return error 7 - file not found, but still return the correct version of LabVIEW in which the project was created.
I've been experimenting with workarounds for this behavior, and I found one.
When I provide the LabVIEW path for libdir in my executable's ini file, the run-time is able to load and inspect the project file.
libdir="C:\Program Files\National Instruments\LabVIEW 2013"
While it's expected that a stand-alone executable may be placed on a system that doesn't have the LabVIEW IDE, it's still surprising to me that the Run-Time Engine cannot find LabVIEW's standard library without some explicit guidance. What other considerations contribute to that behavior?
References:
LabVIEW configuration file/Paths -- http://labviewwiki.org/LabVIEW_configuration_file/Paths

Error: Cannot open project file

Does that error message mean I am trying to open a project file that was created with a version of FCP that is later than what I operate with?
Also, where did the FCP FAQ section go?
PowerMac G4 desky 867MHz 1GB RAM Mac OS X (10.2.x) FCP 3.0.4

Are you trying to open a project created by a later version? (using FCP 4.5 to open a project created in FCP 5 for example)
If so, it can't ge done. The best you can do is export an XML of the cut (only the cut) that the previous version can then import.
#27 Getting a FCP 5 project to open in FCP 4.5
Shane's Stock Answer #27: How do I export my FCP 5 project so that someone can work with it in FCP 4.5?
Final Cut Pro 5 projects are not backwards compatible. What that means is that a project created in FCP 5 cannot be opened by previous versions. The previous version cannot recognize the formatting and code of the newer version. You can go from FCP 4.5 5o 5, but it will reformat your project file, so if you want to have a 4.5 version best to duplicate it and convert the duplicate.
You can, however, export the sequence from FCP 5 so that it will open in FCP 4.5 if you follow these steps:
1) Select all in the Browser
2) Choose File>Export>XML
3) Make sure you choose XML version 1 in the following dialog box
4) Launch FCP4.5 and create a new project
5) With that project's Browser open and active, import the XML
For an in-depth explaination, read this:
http://www.lafcpug.org/Tutorials/basicfcp5_to4.html
Shane

Cannot open project file in Project 2010

Hi,
I have a project created in Project 2010. I can save it without any problems. But some saves are broken and I cannot open them again. When I open saved project an error message is displayed:
There was a problem sending the command to the program and Project freezes. Project 2010 itself starts without any problems. What's strange I can open this file in viewers like MOOS Project Viewer 2.0 but not in Project.
Any tips highly
appreciated.
Lukasz Chomin

Hi Lukasz,
Welcome to this Microsoft Project newsgroup :-)
It sound as though that project has corruption. If you can open it at all, follow the advice given below. If you can’t open it at all, it seems like it’s lost – you do have a backup don’t you?
If you can open it in another program, try copy/paste the data back into a new project.
If you suspect a corrupt file, you could try the suggestions in FAQ Item: 43. Handling project file corruption and/or bloat.
FAQs, companion products and other useful Project information can be seen at this web address:
http://project.mvps.org/faqs.htm
Hope this helps - please let us know how you get on :-)
Mike Glen
Project MVP
See http://tinyurl.com/2xbhc for my free Project Tutorials

Cannot open Project files from previous FCPX versions

Hello,
I'm currently on 10.0.8, and have not upgraded to 10.1.1. Here is my issue:
A documentary project I've been working on since 10.0.1 is not showing up in 10.0.8, and I'm wondering how to "manually" update the Project. I upgraded FCPX versions a few times while working on this Project (I think all the way up to 10.0.4), but then I stopped as I noticed it was negatively affecting parts of my project and making the application run slow (and Apple recommends you don't update versions while in the middle of a project). I finished that project, but now fast forward and I'm in 10.0.8 and I need to revisit that Project to make a few changes, but FCPX won't even recognize it. It successfully updated and recognizes the Events I used for this particular Project, but not the Project itself.
Any help/suggestions would be great.
Thank you!

Thanks Russ. After all this time, I actually solved the problem myself. I forgot that back 6 months ago, I renamed my Project file, from the default "CurrentVersion". I just came across another post that said you're not supposed to do that, so I changed my Project file back to "CurrentVersion" and now FCPX recognizes it. After all that toil, the answer was just too simple!!
Thanks.

Premiere Elements 4 - Cannot open project file with write access

I have most of my video files on a network share drive.
However, I am unable to create the "native" files on the share (and also cannot save to them.
I must generate the new files (.prel) on a local drive (and therefore save new renditions to this location).
Is this a problem with Premiere Elements 4.0?
Should it just be run locally or can it be used on a network share?
Thanks

I do not believe you can use Premiere Elements on a network, Wayne. Especially if network is something other than an XP network.

Photoshop files in FCE - Cannot Open Project

I have a series of Photoshop files (RGB with about 10 layers a piece).
I am able to import a file into FCE HD and move the layers around as tracks - everything works great.
I save the file, and close. When I try to re-open the file, I get the dreaded "Cannot open project file".
I have tried this with an external drive and saving to the desktop. I have also tried importing normal pictures - no problem. It's when I import layers. I have been able to isolate the problem to layered Photoshop files.
Any ideas?
thanks.

Any PS file that has transparency that is imported
into a PAL project will corrupt the file, so
that you cannot open it again. Sorry.
See this (9th post down) which showed that any file created in Photoshop with its type as ".psd", whether with or without transparency, will give this fault. However, a file created in Photoshop with .tif will be safe even if it has transparency.
G5/2.0 GHz Mac OS X (10.3.9) 1 GB RAM, 150 GB HD, Sony DCR-HC96 mini DV, FCE HD 3.0 DVD SP 3

Project 2003 cannot open the file

When I try to open my project, I get this error message: "Project cannot open the file, check that the file name & Path are correct, check that the file format is recognized by project"
It is a .mpp file, and was created with and had all modifications done with project 2003.
I have tried opening this file on other computers and I get the same error message.
Please folks, any help!

Hi,
Based on the error message, please see this KB to troubleshoot it:
https://support.microsoft.com/en-us/kb/274394
Then, this Project MPP file may be corrupted, we may try to repair/recovery Project files, please see the threads about below.
https://social.technet.microsoft.com/Forums/projectserver/en-US/bf98d943-2945-490b-b28d-c6c225376893/recovering-corrupt-ms-project-files
https://social.technet.microsoft.com/Forums/ie/en-US/f4f04d2c-fd6a-491c-b96d-f1be5b6ed1a7/how-to-repair-ms-project-file?f
Hope it's helpful.
Regards,
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Unable to open project file - from one 6.0.2 to another 6.0.3.

Hi
We're at a time-critical stage of finishing our movie, and we need to get the color-corrected sequence from the post-house to our studio so we can make some picture changes and get it back to them. They can open the project file just fine (it was created in 6.0.2, but they since updated their system to 6.0.3), and we have just updated to 6.0.3 also. Quicktime is 7.4.5 (which matches their version). However, they've FTP'd it to us, and we cannot open it here. FCP gives the error "Unable to open project file". It's not the "older version" message which I've seen before, it just ... fails to open it. Almost as if the file were corrupt. However, the post house can re-download the file from FTP and open it there, so this confuses me. I've also tried the file on a FCP 6.0 system (which I can't update because it's an Avid system locked to a certain version of Quicktime) and the same error message.
Would anyone be willing to test the file and see if they can, at least, open it?
Many thanks.
Matt

Have them zip the file... Project files via email often don't open if they aren't zipped..
Jerry

SSIS package "The Microsoft Jet database engine cannot open the file"

Dear all,
I am trying to import data from an excel spreadsheet which is save on application sharing server. When I try to save same file locally (On my desktop) my package has no problem to read it. Problem comes when I change the file path to the share location
I am getting below error message,
"Version 11.0.2100.60 for 32-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 13:26:46 Error: 2014-12-05 13:26:50.30 Code: 0xC0202009 Source: Incremental MasterStyle DL
Connection manager "Excel Connection Manager" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft JET Database
Engine" Hresult: 0x80004005 Description: "The Microsoft Jet database engine cannot open the file ''. It is already opened exclusively by another user, or you need permission to view its data.". End Error Error:
2014-12-05 13:26:50.30 Code: 0xC020801C Source: Data Flow Task 1 Excel Source [36] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection
manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error Error: 2014-12-05 13:26:50.30
Code: 0xC0047017 Source: Data Flow Task 1 SSIS.Pipeline Description: Excel Source failed validation and returned error code 0xC020801C. End Error Error: 2014-12-05 13:26:50.30 Code: 0xC004700C
Source: Data Flow Task 1 SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2014-12-05 13:26:50.30 Code: 0xC0024107 Source: Data Flow Task 1
Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 13:26:46 Finished: 13:26:50 Elapsed: 3.401 seconds. The package execution
failed. The step failed."
I am trying to run this package as an sql server agent job and server is installed on my Machine. I have created proxy account with my own credential to execute it. I have full excess to the spread sheet and can open it in an excel program. Please
suggest what could be the reason why sql job is not able to access this spreadsheet. I can think of below reasons
File is password protected and I am not using its password to unlock it?
My domain account is a part of It Admin group with high previllages
when I installed my SQL server I installed it as a standalone instance of SQL server?
please advise.
regards
JKH

Hi Jahangir,
Based on the error message that "The Microsoft Jet database engine cannot open the file ''. It is already opened exclusively by another user, or you need permission to view its data.", there are two causes:
The account that SQL Agent is using does not have the correct permissions for the file or for the folder that contains the file.
Another process or user has the file open.
The following resolutions correspond to the previous list of causes:
Since you use a network path to the file (UNC), check the account permissions on the share, the file, and the folder.
The "another user" may be Microsoft Visual InterDev. Close any Visual InterDev projects that contain a data connection to the file. Please close all instances of excel file and re-run the package.
Besides, we can use a tool like
SQL Server Profiler to see what is happening when you run the package.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Cannot open project: the folder for this project cannot be found cs4

I am using Encore CS4 and I get the error "cannot open project: the folder for this project cannot be found"
Having searched the forums I can not find a solution for when the project folder has been deleted.
Can someone tell me the solution to this issue.

If you deleted the Encore directory, you cannot fix this. You'll have to start over.
Encore creates this folder structure:
Root or some other Folder
MyProject.ncor (the Encore project FILE)
MyProject (the Encore project directory)
Other Folders for the Encore project (e.g. Cache, Sources)
You can get the "the folder for this project cannot be found" in various ways.
There have been two recent threads in which the user, by accident or on purpose, changed the folder location or name. You can fix this by renaming the folder correctly or moving it back (or moving the Encore project file to the correct relative position).
Folder was renamed. If you name the folder "MyProjectX" Instead of "MyProject," the project file "MyProject.ncor" can't find it.
Encore project file was moved - or Encore directories were moved. If you move "MyProject.ncor" to some other directory or drive (including inside the folder "MyProject"), it can't find the directory - it is looking one directory level below where the project file is located.
If you delete the Encore project directories, the stuff that Encore uses that projects menus, motion, etc, are gone. While many of its instructions are inside the project file itself, many are not. Some of the deleted material might be recreated (e.g. trying to fake Encore into accepting a copy of a menu), but most cannot.

Cannot open cs6 files in cc

Hello,
I recently subscribed to CC after completeing a project on the trial version. However since purchasing CC I have been unable to open any of the CS6 files I had downloaded (I could open them whilst on the trial period). Yesterday I just kept receiving the error message " Cannot open the file **** Adobe Indesign may not support the file format, a plug in that supports the file format may be missing or the file may be open in another application" Today I cannot even click to open any of the files, they are in a faded typeset in the documnents or downloads folders. I can open any indesign files I have created from scratch though? So it seems it is just the files originally created in CS6 that are affected. I am working on a macbook, if that makes any difference.
Many Thanks for your help.

Hi Peter,
Thanks for your help. I am working on the 9.2 version Willi.
I am unable to open the downloaded cs6 files on their own, even from the file menu, as the error message appears, but today they are no longer in faded type in the folder, and I am able to click on them and drop into a new indesign file and resave.
So thank you for your help.

Mac OS X cannot open pdf files from online sites.

Mac OS X cannot open pdf files from online sites.

The problem is definitely between my safari and Adobe.
I can open documents in emails. But not something like this.
Your Folk Project newsletter for the coming month is available for download at:
http://folkproject.org/enl/eNewsletterDownload.shtml
Kathryn Weidener
Storyteller
908 369-7571
[email protected]

Indesign cannot open "old files" CS6.

I was supposed to do a few adjustments in a project, i have opened it before and been working in it alot.. (2 months since last time i was working with this project) When i was supposed to do some minor fixes etc on this project yesterday i cannot open the file. The project it self are only on 8900 kB. What to do???? I can open my recently "newly" made and used projects.... Ive tryed some other projects that was also old, all between 2-6 months.. And it is just randomly witch i can open and witch i "Cannot open"..
This is the error for CS6.
This is the error for CS 5.5.
If you got some suggestions scream out! Will try it all that have worked before.. (If someone have had this same problem atleast!)
Sincerely,
David

First, a tip: Try manually breaking the links to the file by moving that document you want to open to your desktop or another directory or such and then try opening them... (corrupt image previews and/or images can then be largely elminated as a potential cause)
As @Peter mentioned, we (Markzware - link here to how that works) can likely fix this file. Interesting notes from @jongware above. Without having seen this file, our research shows there are various reasons an InDesign file can head south and corrupt or crash on you. Just like a doctor can not always say what caused the problem, there are some basic steps we all should take. For instance, OS up to date, InDesign using the latest update available, enough disk space and scartch disk space for heavy Adobe design operations. Here is a list of some of the most common issues with bad INDD documents:
* Corrupt Font(s) (or corrupt font caches - see below)
* Corrupt Image(s)
* Power Failure
* Placing images via drag-and-drop from an Internet page
* Working on an InDesign file over a network or on a remote server
Here is a video on how to tackle the font caches of InDesign, which is good to do once and a while anyway:
http://www.youtube.com/watch?v=Nf5ZuiaYgus
For checking individual font files (fonts are like mini apps really), we recommend either FontExplorer XPro or Extensis Suitcase Fusion 4, with the later perhaps the more popular of the two.
You can contact me on [email protected] if you need assistance with us trying to recover your bad InDesign CS file further. We also have a PDF to InDesign conversion tool called PDF2DTP if you have a PDF.
Friendly Regards,
David Dilling of Markzware

Cannot open .project file

Similar Messages

Maybe you are looking for