I am using TFS server 2018 Update 1. I have used it long time and it works well. Now I tried to restore the backup through TFS its shows that BackupSettings.xml file is missing. But In my backup folder BackupSets.xml file.
Old days BackupSettings.xml is created inside the backup folder. Now its replace with this BackupSets.xml file.
BackupSets.xml file is not recognized from the TFS server. I tried to rename the file but not working. If you have an idea for this issue please help me.
BackupSettings.xml file is not replaced with BackupSets.xml file, they are two different files, and they are supposed to exist together in the backup folder.
You can go to Administration Console -- Logs to check the backup logs to see whether there is any error. And go to Scheduled Backups to take another full backup.
Related
Symptom: Unable to start PlasticSCM.
Error: Root element is missing.
Full text of error: "the client configuration file "client.conf""
Actions:
I tried reinstalling. I have also tried running the configure command.
What to do?
You can try to delete client.conf with all GUIs closed so it rebuilds next start, its located in the hidden folder Users/youruser/.plastic4 (Mac) or Users/youruser/appdata/local/plastic4 (windows).
If the problem persists you can contact PlasticSCM support at support#codicesoftware.com
Solution:
Delete "client.conf" under "C:\Users\youruser\AppData\Local\plastic4"
Rerun the "cm configure" command and/or reinstall.
Those files are not deleted under reinstallation to not break the configuration between upgrades. Thus they have to be deleted manually.
I am getting this error while am publishing the project to local system
Copying file obj\Debug\build.force to
obj\Release\Package\PackageTmp\obj\Debug\build.force failed. Could not
find file 'obj\Debug\build.force'
I am not able to find the proper solution.
Tried Restarting VS
Deleted Bin Folder and rebuild the project again
you just delete that whole folder(obj\Debug) from the solution(don't delete it from the directory) and try to publish it will definitely work.
There's a problem with TFS everywhere plugin for Eclipse if I try to revert or restore a file under a source control and if the folder/file is mapped to a different volume than the actual project.
When I try to restore or revert it, I get an error:
java.io.IOException: Failed to rename /Users/*/*/*/*/.tf1/8/d54f18aa-bdce-4ab7-958a-01eaaf0c36c1.tmp to /Volumes/macOSData/*/*/*/*/*/some_file.cs. Check the file and directory permissions.
Log has additional line:
2018-07-31 12:44:39,814 WARN [ModalContext] (com.microsoft.tfs.util.FileHelpers) Main rename failed (source permissions problem?), trying to rename temp file back
There's no problem while I get specific version of the project, even with overriding existing files, so there permissions are fine, at least for getting files. Also, this does not happen when the file is on the same volume as the local TFS mapping.
Setting all permissions to 777 does fix the problem, but this marks all files with +x making them all "changed", making this solution unacceptable.
I tried mapping the base folder to a second drive (i.e. force creating a .tf folder on a second drive), but this doesn't help. The error will appear when I try to revert stuff on the main volume.
I tried using symlinks so the mapping stays within the same volume, but still no luck.
Is there any way to solve this? Or everything should be on the same volume?
After a whole day of digging around and poking with jshell, this appears to be a bug with File.renameTo() in Java on macOS. renameTo function silently fails without any exception even though there's no permission issue to write to the destination. This happens only when writing to a different volume.
I have submitted a pull request into TFS Everywhere repo on github with a workaround for this issue.
Anyone interested can compile plugin with this changes to get things working:
https://github.com/Microsoft/team-explorer-everywhere/pull/276
I am running neo4j v.3.0.1 and I want to restore an old backup (of another version of neo4j) by moving the old graph.db directory.
In my neo4j.conf I have:
# Paths of directories in the installation.
dbms.directories.data=/var/lib/neo4j/data
# Enable this to be able to upgrade a store from an older version.
dbms.allow_format_migration=true
If copy graph.db in /var/lib/neo4j/data, the restore does not work, but a new folder called graph.db is automatically created in /var/lib/neo4j/databases after I start the service.
If I copy the backup folder directly in /var/lib/neo4j/data/databases, the restore is successful. I do not understand why, since I set dbms.directories.data=/var/lib/neo4j/data
Am I doing something wrong?
The databases is implicitly appended to the dbms.directories.data path. That is a change in 3.0.
I know this has been asked many times before. But I am getting a:
The mbstring extension is missing. Please check your PHP configuration.
First off I am using WanmpServer3.0.0 64 on a Win7 64 VM.
-I tried editing the php.ini file to give an absolute path to no avail
-made sure that the extension=phpmbstring.dll is uncommented
Another problem is that i noticed that whenever i load a php page it has fatal errors for my mysql commands.
When I use the wampmanager from the tray to open the php.ini file instead of through windows explorer I get:
Cannot find the C:\wamp64\bin\apache\apache2.4.17\bin\php.ini file. Do you want to create a new file?
So now I'm thinking something has gone drastically wrong and would like to uninstall/reinstall Wamp. I attempt to use the mysql console to save my databases before deleting the wamp directory. However when I run a mysqldump -all-databases > all_database.sql it just drops down to an empty line and nothing happens.
mysql console screenshot
If I browse around in the C:\wamp64 directory i find the "data" directory within \bin\mysql where it seems all of my databases reside but not in readable form.
Is there anyway to save my databases??
BTW: This whole setup was working fine previously, so I'm not sure what caused the crash and burn.
Was able to figure it out.
I opened the php.ini file from the PHP bin folder and copied all of the contents into a new php.ini file to reside in the apache bin file.
Now everything works again.
I'm not sure this is how wampserver is supposed to work or what changed to start the problem but it's pseudo-resolved now.