I have been using MySQL workbench for years. Recently the previous version 8.0.nnn stopped launching. I decided to try to repair the installation by upgrading. It worked for a few days and now it hangs again.
Uninstalling and reinstalling is not helping.
There are no notifications in event viewer. There is a task (process) in Task Viewer, but the process does not progress to showing a window.
I can connect to, and query, the server on the command line or via the API (not that it is required for launching Workbench).
Any ideas about origin of this rather perplexing problem?
I discovered that the user data (User\AppData\Roaming\MysSQL\Workbench) contained corrupted files.
The error message popup (window) remains hidden, but can be seen when using Alt-Tab to rotate between applications. One cannot bring focus on the error window, but one can see the message among the choices in the Alt-Tab interface. I could see something about corrupt file and that it was in the profile's Roaming.
Deletion of the single file that was indicated (wb_state.xml) was insufficient to get WorkBench to display. Deletion of all files in the Workbench directory restored Workbench.
Hope this is of some use to others.
I have a SQL Server 2008 Job that backs up a database, then zips that backup and moves the zipped file. My job runs fine until it gets to the step that calls WinZip, which executes:
c:\program files (x86)\winzip v19.5\winzip32.exe
-m \\RemoteShare\RestrictedFolder\dbBack.zip
x:\SQLInstanceFolder\BackupFolders\dbBack.bak
The job neither completes nor fails; it just stops moving forward. It will generate the dbBack.bak file and create the dbBack.zip file in the remote location, but it won't proceed past there. It seems to be behaving like it is waiting on a pop-up confirmation, but I don't see one when I log in to the console or run the zip from the command line.
I've tried adding -ybc flag to automatically confirm or skip any prompts, but it didn't seem to do anything. The process still didn't complete. I've even tried to > pipe output of the process, but it won't even write my log file.
This is a secured system and infrastructure, but I'm fairly certain I'm not being blocked by a permission. My SQL Server service account that runs the job has access to the folders it needs and it can run the winzip32.exe process. This process ran fine, but we had to upgrade WinZip this past weekend (19.5), and that's when it stopped working properly. We aren't able to roll back to the previous version (10).
Does anyone have any idea on what could be stopping my process or how to make it proceed?
I think I discovered the problem. It turns out, we are using the GUI version of WinZip and calling the executable from the command line. Even though we can't see the GUI, it's still there. So, the prompt to confirm our compression is still there in the program's workflow, we just can't see it and thus can't confirm it. And the confirm flags don't work with the GUI version.
My workaround involved logging in to my SQL server as our service account and running a WinZip operation. When it completed and gave me the Add Complete prompt, I checked Do not display this dialog in the future and clicked OK. This will suppress that prompt when the service account runs its Job.
If someone changes the service account, we'll have to do this again, so our ultimate solution will be to install the WinZip Commmand Line Plugin. Hopefully, when that's done, we won't have to worry about this.
But it works now. :-)
Few days ago I had installed Access Database Engine 32-bit on my 64-bit machine since we are using 32-bit MS software. However this led to some problems and I had to uninstall them again. After this incident Spotfire 7.0.1 refuses to open accdb files. When I go to Add data tables -> File, the file ending *.accdb is simply missing.
I also had a problem with access not finding the correct .dll files. Somebody suggested to manually edit the registry with follow code:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\TypeLib\{00025E01-0000-0000-C000-000000000046}\5.0\0\win32]
#=hex(2):25,00,43,00,6f,00,6d,00,6d,00,6f,00,6e,00,50,00,72,00,6f,00,67,00,72,\
00,61,00,6d,00,46,00,69,00,6c,00,65,00,73,00,28,00,78,00,38,00,36,00,29,00,\
25,00,5c,00,4d,00,69,00,63,00,72,00,6f,00,73,00,6f,00,66,00,74,00,20,00,53,\
00,68,00,61,00,72,00,65,00,64,00,5c,00,44,00,41,00,4f,00,5c,00,64,00,61,00,\
6f,00,33,00,36,00,30,00,2e,00,64,00,6c,00,6c,00,00,00
[HKEY_CLASSES_ROOT\TypeLib\{4AC9E1DA-5BAD-4AC7-86E3-24F4CDCECA28}\c.0\0\win32]
#="C:\\Program Files (x86)\\Common Files\\Microsoft Shared\\OFFICE14\\ACEDAO.DLL"
Maybe I messed up with the file type association?
This is too long for a comment so...
Editing the registry should be done with GREAT precaution, and generally speaking, is the last thing you should do. You can really screw a lot of things up doing that. The best thing to do is restore your server from a backup or snapshot if it's in a virtual environment. You should always backup / create restore points or or snapshot (if virtual) your sever before making any big changes.
Judging by your post, your problem is contained to Access. Can you add other types of data files / connections to Spotfire? If so, i'd create a backup immediately while you uninstall / reinstall access, or do what ever else you are going to try.
This morning, I got this error
Error accessing file. Network connection may be lost
no matter what I was doing on any form. So I opened a blank database and imported everything. Some error occurred but it said that the import was successful. I was able to open my form again. Then I went back the old copy and then I got this error when I try to open the database
The database cannot be opened because the VBA project contained in it cannot be read
Even the backup I did before the first error is saying that now.
and I tried to import again and I got the error while it was importing.
I'm getting abit nervous now, plz tell me there's a way to fix this
thank you
You can try decompile when Access complains it can't read the VBA project code. See the two answers to this SO question for detailed instructions: HOW TO decompile and recompile.
If decompile is unable to restore your application to good working order, the quickest solution is probably to revert to your last good backup copy.
If you're willing to put in extra effort to recover module changes since the last backup, check whether you can still access the module source code. If the source code is readable, you can use the undocumented SaveAsText method to dump the code to a text file:
Application.SaveAsText acModule, "Module1", "C:\SomeFolder\Module1.txt"
Then later load it into a new db file with the LoadFromText method.
Application.LoadFromText acModule, "Module1", "C:\SomeFolder\Module1.txt"
For those still having this issue, here's an update. This issue occurs when the .accde is compiled on a version of Access that is newer than that of the affected computer. It turns out that some machines were being updated with windows update and some weren't. After getting all installations of Office to the same version number by installing SP2 and then a February, 2016 update, the executable now runs on all my machines.
Here's the Link to SP2 (make sure you download the correct file.)
https://www.microsoft.com/en-us/download/details.aspx?id=39667
Here the February, 2016 update:
https://support.microsoft.com/en-us/kb/3114750
HTH,
Patrick
I've been trying to install SQL Server 2008 R2 with tools.
I've downloaded thisn version and it just won't work!
I've had some problems installing Visual Studio SP1 due to silverlight4 being already installed, so I figured i needed to uninstall everything that had something to do with sql server, so I did.
Still the errors show up.
These 2 errors show up at the beginning of the installation during "Setup support files".
(I can't post more than 2 url's yet, so Ive put all the screenshots in 1 image, sorry)
Here
The first error is the top left one, and retry fails, and when I hit cancel a few secs later the second error pops up and the installation terminates.
My OS is W7 x64 with all updates installed.
I don't really know how to go on actually. I've searched for hours yesterday without any results.
Anybody got a clue? Before I reinstall every .net-related programs.
Thanks in advance!
Edit:
So far I've tried:
I checked if the first file shown in error 1 is actually there, and it is.
Tried to run the setup explicitly as administrator
I checked if the second file/folder was present, and it was not. So I manually created the folder and file, which then causes the
first error to say the same, but then it says can't create
\SqlSupport_Cpu64_1_ComponentUpdate_1.log, then I tried
to create an empty file with that name and extention. This makes the installer
append the filename with "_1". If I create that file too, it just
appends with a higher count.
Uninstalled every sql server related program (e.g sql server compact)
Reset all the permissions on the e: disk and formatted it.
I found the cause of the problem. Recently I'd set my default program files folder to my hdd, because my C: is a 60 GB SSD. The key is located in the register at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion. The keys "ProgramFilesDir" and "ProgramFilesDir (x86)" are the ones that need to be default ("C:\Program Files" and "C:\Program Files (x86)") in order for it to work.