I use AnyLogic PLE v8.76 on mac. It worked fine for a week, but today I got problem launching the software. I keep getting this message:
And this is the error shown:
I tried to download Anylogic again, but I still got the same problem...
I did not download any other softwares or change things on my mac.
Can somebody help me?
Thank you!
Best option, as often advised by the AnyLogic support team, is to clear the workspace.
Try the following:
Make hidden files and folders visible on your Mac - cmd+shit+.
Navigate to your user folder (Either from he side bar, or Macintosh HD -> Users->(yourname)
Find the .AnyLogic... folder, on mine it is called .AnyLogicProffesional
Delete the following two folders workspace8.x and configuiration8.x where the 8.x indicates your version number of the currently installed AnyLogic version.
These files keep settings and the currently loaded models on the disk and will remain even if you download a new version of AnyLogic, which is why downloading a new version does not always solve these kinds of problems.
If the issue still persists contact support, they might ask you to send the error report you got from your Mac (so copy and paste it to a document the next time you get it) as well as some error logs that get stored in these hidden files and folders. (Now you at least know where to find them ;-) )
If my solution did not provide the answer, please add an answer if you manage to find it.
Related
I'm facing an issue with how Windows 10 IoT and user files works. Whenever I try to update the application via AppManager, which seems to be the only current way to update/upgrade an app, the user files are removed.
Does anyone know a work around for this issue? Writing files to any other location seems to be disabled, and I'm faced with Unauthorized exception.
To get the LocalFolder in appData for the installed package Ive used the following:
ApplicationData.Current.LocalFolder.Path
Using version 10.0.10586.
Any help is appreciated!
I couldn't find a solution to my problem, so instead I had to do a workaround. The workaround is to write the settings files, that I want to keep after upgrading/updating the software, to the Videos/Pictures folder of the DefaultUser.
The appmanifest has to be updated with the correct permission, so remember to add Videos or Pictures access as allowed by the app.
Hopefully this can help someone else if they have the same problem as me!
Suddenly I'm getting an odd error popping up every few minutes.
'Periodic workspace save.' has encountered a problem.
Could not write workspace metadata '{workspace}.metadata.plugins\org.eclipse.core.resources.snap'.
I've checked and the file is there. It's not marked "read-only".
Nothing's changed recently. I am on a Citrix VM running Windows 7 and my workspace is on a mapped drive. However, this setup has been running fine for over a year.
Any ideas?
I ended up creating a new workspace and moving my projects over there. Fortunately there weren't many (nor did I have too many snippets) and I could recustomize the way I wanted.
This is not a very good solution, however, and I'd love to see a better way to fix this issue.
I need to maintain an old vbp (vb6) project that uses the purchased videosoft vsFlexGridPro7 ocx (not the free msFlexGrid included in vb6pro).
This was working fine in WinXpPro and even in WinVista.
But my pc has crashed and now the new one runs Win7 64bits.
The original setup.exe from Videosoft (maybe using 16bits) doesn't run, and without running this setup I don't know other way to enter my legal lic code.
Then my vbp shows error (thinking I'm running the unregistered version) when running in vb6IDE or tryng to compile.
So, several related questions...
1.- any way to enter the lic codes without run setup.exe?
2- any way to run setup.exe? (not in an virtual machine....)
These grid don't use DB, "only" the LIGHT version (Vsflex7L.ocx), all code managed.
btw I think videosoft.com is closed, ComponentOne sells an version 8, but is expensive and 1.- not sure if it will be ease the conversion and 2.- if Videosoft is out of business don't appears as a good purchase.
Thanks very much in advance.
I don't think VideoSoft are "out of business". If I remember correctly they merged with another company (APEX) and changed name to ComponentOne, so you may be eligible for an "upgrade version" instead of a full new license.
We also faced exact same problem...our old VB app uses some of very old controls which are developed long time back ( 16 bit setup ). We ended up writing a installer for installing the files ( we ended up using the installsheild to create a setup) we got the list of files from original install locations ( install.txt). As far as license goes you can copy the license.bat file from original install location to c:\windows\system folder. Hope this helps.
I am on Mac OS X 10.6.8 using Xcode 4 with Cocos2D.
The other day, I got an error message out of the blue when trying to run my project:
The document "MainMenuScene.m" could not be saved.
I tried the following, none of which has worked:
replacing the file
creating a new one and renaming it (which I could not rename it. I was told I didn't have permission)
creating a whole new project and reading the files/copy pasting the code in
opening Disk Utilities and running Repair Risk Permissions (which works again once, but then reverts back).
I sometimes get the off chance and the file does save, but reverts back to not saving again.
Anyone have any ideas on what I can do to fix this?
I had this issue with a project on an external ssd. Disconnecting the ssd and reconnecting fixed it for me.
In short:
Have you tried turning it off and on again?
See the full conversation in the comments, but this ended up being solved. Moving what was suggested/asked here for clarity and closure.
Is that the full error? Also, are you saving it on a USB or your HD?
Are you an admin on your computer, etc? Have you tried to move the project completely, or copy and try to work on it from somewhere else? With the currently given information I cant think of anything that would cause that kind of problem. What has changed since you were last able to edit and save without issues?
Glad we got it figured out!
-Karoly
Have you tried just moving the file? That'll probably do it.
For one of my clients, I've developed a small iOS app. I'm a member of their dev team, so I've been using a development certificate to sign my local test builds.
Now the app is almost done and it should go into internal testing on the clients side. I created an archived build of the app which I then sent to my client. They imported it into the organizer and tried to "Share" it to be able to re-sign it using an ad hoc profile.
Creating the .ipa fails with an "no such file or directory" error though. The archive appears to be fine otherwise - the organizer shows all the usual information, the icon, and it will let them export it as another archive. Creating an .ipa without re-signing fails as well, which leads me to believe this is not an issue with ther certs and provisioning profile.
If I try the same thing on my side, writing an .ipa from the very same archive using my development cert, the operation succeeds.
It may be worth mentioning that the same procedure was working fine while we were still using XCode 3.x on earlier projects. This is the first time we've been trying this using XCode 4.
No additional (static) libraries have been used.
Any help greatly appreciated!!
Edit:
Someone at the apple dev forums suggested to me that I should check the system console for xcode error messages while attempting to export the .ipa - none were printed out. We discovered some other, older messages however, which read as follows:
18.04.11 13:54:35 /Developer/Applications/Xcode.app/Contents/MacOS/Xcode[123] /Users/User/Library/Developer/Xcode/Archives/2011-04-15/Foobar.xcarchive/dSYMs/Foobar.app.dSYM/Contents/Info.plist:
set flags (was: 00200000): Operation
not permitted
The timestamp is roughly at the time when my client first imported my archive, but we can't be sure since we didn't watch the console back then.
The message had been printed multiple time, once for every single ressource file contained in the bundle. Does this tell you guys something?
Problem solved.
Following another suggestion on the apple dev forum, we repaired permissions on both systems. Additionally, I built and archived the app again and used a different way to transmit the archive to my client. We did all of this in one try, so I can't quite tell which of these measures actually did the trick. If you stumble across this because you have the same problem, you might want to try all of this, too.
Thanks for listening!
Update:
It happened again - and this time, we tried to solve it step by step. Result: It's all about how the file is being transmitted. I just attached the archive package to a mail to my client, that's what broke it, although I don't know why. Zipping the archive before transmitting it solved the problem, however.
After downloading XCode 4.3 beta with the IOS 5 SDK, the Organizer function to share and archive stopped working with a cryptic error "No such file or directory found".
It turns out that this is related to having two different versions of codesign_allocate . To fix the problem, do the following in a terminal window.
sudo ln -s /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/codesign_allocate /usr/bin
Another hint - try the manual way to create a shared ipa - since it gives you a lot more detail of what went wrong. See http://blog.dmahajan.net
Can you see if this is also linked to your problem?
EasyCoder's answer fixed this issue for me - I have the 5.0 beta SDK and had the same problem.
I ran the following and it was fixed:
ln -s /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/codesign_allocate /usr/bin/codesign_allocate