Cornerstone "An error occurred and the operation could not be completed" at startup, what to do?
I'm getting a window with "An error occurred and the operation could not be completed". When I proceed it "unexpectedly quits". I already reinstalled the software, but the error keeps coming. What to do?
Here's part of the report:
"Process: Cornerstone [846]
Path: /Applications/Cornerstone.app/Contents/MacOS/Cornerstone
Identifier: com.zennaware.Cornerstone
Version: 2.7.17 (2.7.17)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Cornerstone [846]
User ID: 501
Date/Time: 2015-05-20 10:32:13.913 +0200
OS Version: Mac OS X 10.10.3 (14D131)
Report Version: 11
Anonymous UUID: 3865FC3A-AB3C-183E-A260-CB2C4EB5D747
Time Awake Since Boot: 3600 seconds
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'NSConcreteAttributedString initWithString:: nil value'
abort() called
terminating with uncaught exception of type NSException"
I have the same problem . Just to solve. Open your finder->yourusername->Library->Application Support->Cornerstone,and remove everything in there.
But after that you need to reset Cornerstone setting..
I've just experienced this too, and the answer above was helpful. However, I couldn't afford to lose all of my data and start again so I decided to dig a little deeper.
The problem appears to be some corruption in the file ~/Library/Application Support/Cornerstone/Registration Databases/WorkingCopies.db - you can actually leave ~/Library/Application Support/Cornerstone/Registration Databases/Repositories.db as is, and not lose any of the repositories. I've found that both of the files are XML files and WorkingCopies.db, for example, can be edited so that most of the information can be saved (the structure is relatively simple but you'd want to get an idea of the relationships between folders and working copies - and back-up, of course.).
This is too late for the OP, but it may help someone else.
Edit: It is in fact possible to recovery the entire file.
Shut down Cornerstone (Not that you can start it at all! LOL!) and move ~/Library/Application Support/Cornerstone/Registration Databases/WorkingCopies.db somewhere else.
Restart Cornerstone. It should start ok, without any working copies.
Shutdown Cornerstone.
Look in the new ~/Library/Application Support/Cornerstone/Registration Databases/WorkingCopies.db file.
From the old file, copy from <object type="REGISTRYFOLDER" id="z102"> to the last </object> (should be the second last line).
Replace the same in the newly generated file.
You may need to make sure that the value in <nextObjectID>102</nextObjectID> matches the number (and number only) in the id attribute in the first <object type="REGISTRYFOLDER" id="z102"> node.
Save the file and restart Cornerstone.
Cornerstone was updated recently and I suspect that there may have been some formatting change or small bug.
I encountered the same symptoms and also had several dozen working copies I didn't want to reconfigure. Using the ideas from the previous answers, I was able to restore to working order by backing up my WorkingCopies.db file, letting Cornerstone generate a new one, then replacing the new one with my backup:
Rename ~/Library/Application Support/Cornerstone/Registration Databases/WorkingCopies.db to WorkingCopies.db.bak
Open Cornerstone (should be successful, but without existing working copies)
Quit Cornerstone
Copy WorkingCopies.db.bak to WorkingCopies.db (replacing the new one that was just created when opening Cornerstone)
Open Cornerstone to confirm it has the restored working copies configuration
My conclusion is that the WorkingCopies.db itself isn't corrupted but Cornerstone somehow had a reference to it that did get corrupted. A little reset and all is good.
It could be that your repository and/or working copy registration databases have been corrupted. To verify this:
Quit Cornerstone
In Finder, Select Go->Go to Folder...
Enter:
~/Library/Application Support/Cornerstone/Registration Databases
Click Go.
Move Working Copies.db to the Trash.
Restart Cornerstone
If that does not fix the problem:
Quit Cornerstone
In Finder, Select Go->Go to Folder...
Enter:
~/Library/Application Support/Cornerstone/Registration Databases
Click Go.
Move Repositories.db to the Trash.
Restart Cornerstone
If either of these works you'll end up loosing your working copy and/or repository registrations (not the actual files themselves, just Cornerstone's registrations). In either case, you'll have to re-add them to the application.
Quick workaround to open Cornerstone without losing your repositories:
Go to Terminal. cd ~/Library/Application\ Support/Cornerstone/. Type open . to open the path.
Move Registration Databases and Transcripts to Trash.
Force quit (Command-Option-Esc) Cornerstone, if you haven't already.
Open Cornerstone. You'll see all repos are gone.
Go to Trash and hit undo (Command+Z) or restore Registration Databases and Transcripts by replacing them on the new folders created at Step 1.
You'll get your all repositories back and Cornerstone running.
Related
I have troubles to get snakemake-minimal=7.8.5 to run on Windows 10. I can execute rules, but snakemake terminates due to an error regarding the metadata:
Failed to set marker file for job started ([Errno 2] No such file or directory: 'C:\\test\\project\\.snakemake\\incomplete\\cnVucy9leHBlcmltZW50XzAzL2RmX2ludGVuc2l0aWVzX3Byb3RlaW5Hcm91cHNfbG9uZ18yMDE3XzIwMThfMjAxOV8yMDIwX04wNTAxNV9NMDQ1NDcvUV9FeGFjdGl2ZV9IRl9YX09yYml0cmFwX0V4YWN0aXZlX1Nlcmllc19zbG90XyM2MDcwLzE0X2V4cGVyaW1lbnRfMDNfZGF0YS5pcHluYg=='). Snakemake will work, but cannot ensure that output files are complete in case of a kill signal or power loss. Please ensure write permissions for the directory C:\test\project\.snakemake
I tried to troubleshoot doing the following
change the folders: Documents, User folder, and like the above in the root folder of my c drive
I tried to manipulate the security settings: Controlled folder or RandsomWare Access, see discussion -> it is deactivated
If I erase the .snakemake it is re-creating upon execution, so I assume I have write access. However, some security setting is disallowing the long filename with the hash
I tried the same workflow on a different Windows 10 machine and there I don't get the error, so I assume it is some windows issue.
Did anyone encounter the same error and found a solution?
I agree it is due to the length of the filename. It seems the default max filename length is 260. The file you pasted has a length of 262. You can edit the registry to allow longer filenames. Also consider opening an issue in snakemake to improve the documentation or otherwise address this issue for windows machines.
I have spent time googling but without results. I get following error when creating projects with latest android studio:
Invalid file name: 'con'
New Module was only partially completed.
Your project may not compile.
You may want to Undo to get back to the original state
I have also tried previous version of android studio, but without any result.
What could be the cause of this issue and how can I correct it? I am on Windows 10.
Thank you
I Feel silly now because it was because of con word in package name. The accepted answer helped.
A module name is automatically used as directory name.
As you are on Windows the file-system has several file- and folder-names that are disallowed. con is one such disallowed names (case insensitive).
This means no matter what file-system you use as long as you are running Android Studio on Windows you will never ab able to create a file or a folder named con.
Other disallowed file names are:
CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9. source
Therefore you have two possibilities: Use a different name for the module or use a different OS.
I keep getting this error in the dev environment - 'A SafeHandle or CriticalHandle of type 'System.Data.SqlServerCe.HasSafeHandle' failed to properly release the handle with value ...."
It is in a VS 2012 Winforms application and only seems to happen if a particular piece of code is run at some point. The error shows after the form is closed, but I can't understand why. It only happens in the dev environment and seems to be OK in the compiled version, but I don't want to just ignore it.
The error seems to be caused by this line of code, although weirdly at this point in time I have not opened a connection to the SQL ce database and the directory it is searching in does not have the SQL ce database in it. It is mearly reading in txt files that match a pattern
string[] fileNames = Directory.GetFiles(importDirectory, "BucketHistory*.txt")
I'll do some more digging tomorrow, it's late now, and I have no idea what is causing it.
Any pointers ??!
Turns out I was having a bit of brain fade yesterday. Been working too long hours !
For anyone interested, the problem was that I was opening a connection, then copying the file and running a shrink whilst the connection was still open. It had nothing to do with that line of code.
I would have expected the copy to have thrown an exception, but it didn't appear to. Oh, and opening another connection inside the using statement of the first one. Sigh.
Application is unable to load ANY xaml. Nor create empty window "var abc = new Window1();"
Error message is still the same:
An exception of type 'System.IO.IOException' occurred in PresentationFramework.dll but was not handled in user code
Additional information: Cannot locate resource 'wvmlog.xaml'. (for wvmlog.xaml)
Exception occur on InitializeComponent();
These objects are created without error on another PC - so problem is not in Project settings.
Do not help:
reinstall VS
new install of VS
reinstal .net frameworks
undo source from TFS
complete new workspace and load from TFS
visual studio Clean colution
find and delete all cached dll, pbd
remove all obj directories in solution
install and use VS 2010, VS 2012, VS 2013
move VS and solution into another hard drive
Do Help:
Copy of project (help for 1-2 days, then problem appear again without any manipulation with xaml)
Change solution configuration from 'Debug' to 'Release' (help for 1-2 days, then problem appear in Release configuration without any manipulation with xaml)
Problem is at one PC with Win 7, 64-bit.
The problem occur suddenly after some xaml window renaming, but these changes was many times undo-ed, but problem remain.
Maybe some OS damage, or some wpf/.net caches?
Why wpf/.net show such error on project which is compiled without error - so compiler KNOW that these resources does exist?
Any help is appreciated.
I had this very same issue.
What design pattern are you using?
The issue I had was when I changed the output window ie created a new one and deleted the old one.
I am using MVVM so I created the window in the View folder.
If this is your issue, your APP.XAML will look like:
<Application x:Class="dotDiff2013.App"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
StartupUri="MainWindow.xaml">
<Application.Resources>
</Application.Resources>
</Application>
You then change the startURI to wherever your new window is stored. ie in the view folder.
StartupUri="Main/MainWindow.xaml"
This helped for me. Hope it's the solver to your problem.
I have an app that has been running fine on the iPhone simulator for some time. Recently, I decided I wanted to re-use the data model and related classes in another project - so I dragged them from this project window to the other then told Xcode not to copy, just to make references. At first this didn't work so I jumped through a number of hoops to try to fix it (I may be asking more about that in another post). After all this, I re-compiled and tried to run the original app -- and it's not working any more. On further investigation, I discovered that when I re-compile the original app, I end up with a bundle that contains a .momd package but it contains only a Versioninfo.plist file - no .mom file, no .omo file like I'm expecting to see. I don't recall making any changes to the original app. I don't get any warnings. I just get an incomplete .momd package (and, not surprisingly, my app now crashes).
What's going on here?
BTW, the app now crashes with this message:
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '* -[__NSArrayM insertObject:atIndex:]: object cannot be nil'
Which I get when executing this line of code:
self.productRegistry = [[UIManagedDocument alloc] initWithFileURL:self.productRegistryURL];
I figured this out by looking more closely at the file locations in the project directory using Finder. In the Xcode window, everything looks normal but in the actual project directory I found that the .datamodeld package had ended up at the top level of the project directory -- at the same level as the project package itself. Xcode apparently did not like this but unfortunately it did not complain -- it just created a partial build output. Once I moved the .datamodeld package into the same folder as the rest of the project's code, everything worked just fine.
This would appear to be just a quirk. I would expect that Xcode would either see that all is well and build correctly OR it would see that things weren't quite as they should be and fail. In this case, it did not build correctly but was silent about it.
Hope this answer helps someone else someday.