Eclipse PDT .sql always Save As - sql

I have a number of .sql files in my work space, one of them, when I save it always brings up the Save As dialogue, even though it is already saved. The other peculiarness is that there are 3 other files in the same folder that don't have this behaviour, instead they open the systems default editor (GEdit).
When I save the file in question I also get an error message: "Save Failed
org.eclipse.php.internal.ui.editor.RefactorableFileEditorInp ut cannot be cast to org.eclipse.php.internal.ui.editor.input.NonExistingPHPFileE ditorInput "
Can anyone advise where to look for a solution?

After some trial and error: Open with "internal editor" -> text editor solves the problem

Related

Vue.js file error "The file will not be displayed in the editor because it is either binary, very large or uses an unsupported text encoding."

I was working on a Vuejs project. So this morning when I opened the project it wasn't compiling anymore and it was reporting an error in one of the components. When opening the component, this message appeared in the VSCode editor "The file will not be displayed in the editor because it is either binary, very large or uses an unsupported text encoding." Clicking on open anyway appears a lot of code with strange symbols as shown in the image. When I try to open the file in another editor, the same problem also happens, but the symbols change. I would like to know what might have happened and if there is a way to recover my file?
Looks like your file is corrupt. Restore from a backup, or re-pull from git.

Error while trying to open .xls files

I have some information in a .xls file (I downloaded it from SAP) and I need to paste it in a .xlsm file.
I'm trying to open that file like always but I have the following error:
Run-time error ‘-2147221080 (800401a8)’:
The file format and extension of ‘file.xls’ don’t match. The file could be corrupted or unsafe. Unless you trust its source, don’t open it. Do you want to open it anyway?
and two options: End and Debug. If I choose debug, I get the following error:
Run-time error ‘-2147221080 (800401a8)’: Automation error
I couldn't find anything in Google. How can I fix it? It's impossible to have the information in another format that is not .xls
Maybe try to open the file with notepad? Notepad can open almost any file. It could be that the content will show strange characters though.

Not able to edit MsBuilds default template

I am currently working on TFS automated build process and I won't able to edit/create my process template using Default Template. I did all the process required to edit the Default Template, the process is specified in above link, https://msdn.microsoft.com/en-us/library/dd647551.aspx.
When I try to edit the imported file, Encoding message box appears. If I click in "OK" in Encoding box then the template file get encoded in unexpected format and "Invalid Markup" message appears in designer view of WF.
Please suggest on this. I know it's difficult to understand the scenario without Images but I m not able to post an Image because I don't have reputation >10.
So It's really very much appreciating if someone help me on the basis of Info. I have provided.
Thanking you in advance :)
If you're running into encoding issues, you can edit the file directly in notepad after checking it out. Then "Save As..." change the encoding, then save. Then try to reopen it. Sometimes
This appears to have solved someone else's issue:
http://enginecore.blogspot.com/2014/01/invalid-markup-in-xaml-in-visual-studio.html
close all files open in Visual Studio
close Visual Studio
delete the .suo file near the .sln
delete bin and obj folders

Aspell Dictionary can't be opened

When I try to add a word or to ignore all, Aspell throws the error 'the file "C:/Program Files (x86)/Aspell/en.pws" cannot be opened for writing'. Anyone know what is causing this problem and how to fix it?
Ensure that the security settings of the "C:/Program Files (x86)/Aspell" folder for the current user allow for modifying and writing.
I had the same issue, and this cleared it right up.
Here is some help to the missing en.pws and en.prepl files. I have no idea why the developers failed to provide this simple solution for windows.
Go to the directory of "Aspell", which should have been installed as a sub-directory of NotePad++.
Right click in the main Aspell directory, choose "New" then choose "text document".
Rename the new text document as "en.pws" (without quotes) removing the "txt" extension, press enter key.
Repeat, make another new text document and rename it to "en.prepl".
Open up en.pws in NotePad++
copy and paste the following into en.pws, exactly as below;
personal_ws-1.1 en 2
µÄ
(Note: the µÄ symbols are below, on a new line below personal_ws-1.1 en 2)
Go to the Menu in NotePad++, click "Encoding" and make sure that "Encoding ANSI" is chosen (Dot beside it).
Save file and close file.
Open the en.prepl file in NotePad++
Copy and paste the following into that file;
personal_repl-1.1 en 0
Same, make sure the "Encode ANSI" is chosen.
Save and close file.
Note: you must close each file before using NotePad++ Spell Checker and "learn" button. Else it corrupts the file and you have to redo it.
NotePad++ will now work and you can save words to the ".pws" file.
Possible locations of GNU Aspell custom words file:
%localappdata%\VirtualStore\Program Files\Aspell
%programfiles%\Aspell
For English for example the custom words file is named en.pws (file name = language code) and the very first line must look like:
personal_ws-1.1 en 286
Where "en" is the file name (=language) and 286 are the number of words (lines) in that file. Last line must is always empty. GNU Aspell does not allow words ending with a number (e.g. Beta1). If you have such a word in your pws file Aspell or the application that uses it (e.g. Notepad++) may crash/hang ...
You may have to delete your en.pws file and create a new one (e.g. using Notepad++). File format as described above, otherwise GNU Aspell will fail to work.
I took the read only off of "C:/Program Files/Aspell" folder.
N++ still says
GNU Aspell
Error:
The file "C:/Program Files/Aspell/en.pws can not be opened for writing.
The english .50 dictionary install does not do a proper install into your C:/Program Files/Aspell directories. I had to open the Installer .EXE in WinRAR and copy the folders.
Should I copy the English dictionalry installer into my C:/Program Files/Aspell folder and install from there?
"Ensure that the security settings of the "C:/Program Files (x86)/Aspell" folder for the current user allow for modifying and writing"
"I took the read only off of "C:/Program Files/Aspell" folder. [The error message remains]"
It's not a read-only problem, but permissions. In Security give "Users" "Full control" over the .prepl and .pws files.
The Answer by "sth" and "Mark" is good, but it still has permissions issues in Windows 10. Instead of creating the two files in the Program Files folder for Aspell, create and initialize them on your desktop first; that will give your account full control on the files. (Also, set the encoding before you paste the initializing text.) Then move the two files into the Program Files folder for Aspell, and they will retain the full write permissions of your account without messing with the overall permissions of the Program Files folder for Aspell.

Why does my PDF ask for a password after being retrieved from Visual SourceSafe?

PREFACE: Yes we're moving away from VSS in the next few months.
One of my web projects contains, as one of its files, a PDF. The PDF on our QA site is being pulled from VSS.
A QA tester recently told me he's being prompted for a password when he tries to open it. VSS says the file I have on disk is different than the one it has, so I updated it, but afterwards it's still being shown as different.
So basically VSS is mangling my PDF and the results are so wobbly that Adobe Acrobat Reader is confused and thinks it has a password.
I've tried adding it as Auto-Detect and as Binary. Same results.
Why does my PDF ask for a password after being retrieved from Visual SourceSafe and how can I prevent it?
Do you have the SourceSafe 2005 Update installed?
Handy list of known issues: http://blogs.msdn.com/richardb/archive/2007/06/06/list-of-bugs-fixed-in-sourcesafe-2005-gdr.aspx
The PDF bug was one of the most commonly requested hotfixes: http://support.microsoft.com/kb/925234
I've tried adding it as Auto-Detect and as Binary. Same results.
To be clear, are you adding a version of the file you know is not already corrupted? Even so, there are plenty of other bug fixes on the list above which can cause random file corruption -- try that first.
You can remove PDF password by this tool:
Advanced PDF Password Remover 5.0
Step 1: Import PDF files
Click the "Add File(s)" button, browse your computer to find the PDF files and load them.You can import as many as 200 PDF files into this program for every batch processing.The imported files are listed in the file list window as below.
Step 2: Set output folder
You can customize a folder to save the output files all together. The default folder is My Documents\Advanced PDF Password Removerr. Click "Brows" button to specify a folder on your computer, or you can make a new folder manually in the text box.
Step 3: Remove restrictions
Click "Start" button, and the files are processed one by one.
"SUCCEED" is displayed in the Result column after the removing process is finished.