While I was upgrading from TFS2008 to TFS2012 I received an error stating:
Upgrade Failure: "The installation and configuration of Team
Foundation Server succeeded, however upgrading the data was
unsuccessful"
I then found that you can not rerun the upgrade wizard. How can you rerun the update?
First and foremost BACK UP YOUR DATABASES! REALLY!
At this point I turned to the tfsconfig import command. (http://msdn.microsoft.com/en-us/library/vstudio/ff407080.aspx)
I specifically ran:
TFSConfig Import /SQLInstance:TFS01 (my server name)
/CollectionName:(Anything you want) /confirmed
But I then got this error message:
Errors:1 Error Message: TF255235: Database TfsVersionControl on TFS01
does not exist but the current operation requires an existing
database.
So not only did the original upgrade not work, it also killed one of my DBs. That's fine because I have a backup. So open up SSMS and kill whatever database is pointing to the "TfsVersionControl.mdf" file. Then kill the actual mdf and ldf files.
Next, restore TfsVersionControl again from the database. At this point, we are reset back to pre-upgrade...
Now for the work around. It is an easy but ugly one. In SSMS make the user that is running TFS (in my case tfsService a sysadmin). That's it.
Go back into the command window and rerun the import. About 20 minutes later viola it worked perfectly.
Make sure that you remove the sysadmin permission from the user after everything is working perfectly.
I hope this helps someone.
Related
I'm trying to remotely back up my Neo4J database for already 2 days and nothing works.
I run
sudo neo4j-admin backup --backup-dir=backup --name=graph.db-backup --from=1.1.1.1:1111 --timeout=50m
The files start to get saved and then simply erased after a while and there's no backup.
I tried setting up --pagecache=16M and HEAP_SIZE but it has no effect. Sometime it just stalls sometimes I get an error like this:
unexpected error: java.io.IOException: org.neo4j.com.ComException: Channel has been closed
The DB I'm backing up is Enterprise 3.3.3 and the one I'm backing up with is 3.5.14
Thank you for any help.
Is this the normal Neo4J behavior?
Using Visual Studio 2019 to publish an update to an existing windows store application. This worked a week ago.
Our solution builds without error. When I go to create the setup package I get an error "Failed to sign 'D:\dev\MeyerMusic\MeyerTablet\TabletDistribution\bin\AnyCPU\Release\MeyerMusicTabletSetup_2.6.6.0_AnyCPU.msix'."
We are distributing the application as a Microsoft Store app under the existing app name.
Last week on this same development computer I built version 2.6.5 as well as many packages before that.
The error number is blank or missing. I do not have a reason for the failure. I only see one fact in the error message and that points to line 4574 in the file: C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets
That line is this:
<SignAppxPackage Condition="'$(AppxPackageSigningEnabled)' == 'true'"
AppxPackageToSign="$(AppxMainPackageOutput)"
CertificateThumbprint="$(PackageCertificateThumbprint)"
CertificateFile="$(PackageCertificateKeyFile)"
CertificatePassword="$(PackageCertificatePassword)"
HashAlgorithmId="$(AppxHashAlgorithmId)"
EnableSigningChecks="$(EnableSigningChecks)"
SignAppxPackageExeFullPath="$(SignAppxPackageExeFullPath)"
TempCertificateFilePath="$(TempCertificateFilePath)"
VsTelemetrySession="$(VsTelemetrySession)"
SigningTimestampServerUrl="$(AppxPackageSigningTimestampServerUrl)"
SigningTimestampDigestAlgorithm="$(AppxPackageSigningTimestampDigestAlgorithm)"
/>
Troubleshooting steps:
Attempted to build a side load package. Results in same error
Successfully built a side load package that was not signed
I have restarted Visual Studio
I have rebooted the machine
I have deleted OBJ, BIN for the entire solution
I have looked for errors in the event log but none have been found so far.
After uninstalling KB4535996 the problem was resolved.
I found this via a tip from the following post: https://developercommunity.visualstudio.com/content/problem/934967/uwp-error-failed-to-sign.html
Using a few months old database copy of our production instrance running on TFS 2018.3 i tried to upgrade it to 2019.1.
During the upgrade of the collections, one of the collections failed on step 729.
Before i go back on load a fresh database, i would like to understand the error message and make sure we prevent it in the future.
Has anyone seen this error before and know how to fix it in my upgrade ? as well as make sure this does not happen for a future upgrade ?
[15:02:03.047] +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[15:02:03.047] ++ Executing - Operation: DistributedTaskOrchestrationToDev17M141Collection, Group: DistributedTaskOrchestrationToDev17M141Collection
[15:02:03.047] +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[15:02:03.047] Executing step: Start Queued Plans in PlanQueue
[15:02:03.047] Executing step: 'Start Queued Plans in PlanQueue' DistributedTaskOrchestration.StartThrottledPlans (729 of 858)
[15:02:03.313] [Error] VS402939: Release with ID 625 does not exist. Specify a valid ID and try again.
[15:02:03.327] Microsoft.VisualStudio.Services.ReleaseManagement.WebApi.Exceptions.ReleaseNotFoundException: VS402939: Release with ID 625 does not exist. Specify a valid ID and try again.
According to the error info
Executing step: 'Start Queued Plans in PlanQueue'
......
Microsoft.VisualStudio.Services.ReleaseManagement.WebApi.Exceptions.ReleaseNotFoundException:
VS402939: Release with ID xxx does not exist. Specify a valid ID and try again.......
It may caused by a release stuck processing in the pipeline queues.
There are few scenarios:
Requests are busy in the pipeline queue a Pipelines.They do not have
a 1:1 relationship with the agents. Looks like there are more
releases with environments in progress than the available licenses.
Clearing out requests that are in the queue: To clear out invalid
requests, the most recommended way is to cancel any in progress
deployments. Refer to
https://www.visualstudio.com/en-us/docs/build/actions/view-manage-releases#release-summary
Simply refresh the release using the refresh button and try again
which may also do the trick
Before you do the fresh database upgrade, kindly check if there are some releases hang in the queue for your collections. Check Pipelines--Agent Pools--Running Jobs. This may avoid the same issue which does not happen for a future upgrade.
We reported this same issue on the Microsoft Developer Community.
https://developercommunity.visualstudio.com/content/problem/720729/upgrade-to-tfs-20191-failed-with-error-vs402939.html
In our scenario, we created a production copy around May 2019 using TFS 2018.3, left it running until now and tried to upgrade this production copy into a TFS 2019.1. This failed.
It seems this issue was caused by our "outdated" production copy we left running which we later tried to upgrade to TFS 2019.
The upgrade failed because Releases have been in the queue for longer than 30 days, which caused parts to be deleted by the retention policy.
For production environment, its advisable to cancel any stuck
deployments before upgrade.
I will keep this in mind, but it would be good for Microsoft to make sure the upgrade process does not fail in case there is a stuck deployment somewhere.
In the project installer i am creating a custom event log. But when my service starts my all logs are going to the "Application" instead of my cuustom log. Below is the code which i have added to installer.
// Create Event Source and Event Log
EventLogInstaller logInstaller = new EventLogInstaller();
logInstaller.Source = "MyServices";
logInstaller.Log = "MyService Events";
Installers.Add(logInstaller);
Furthurmore the name of service is MyService.exe.
When I uninstall and re-install the service, i installation fail with the following install log;
Running a transacted installation.
Beginning the Install phase of the installation. See the contents of
the log file for the D:\MyService\MyService\bin\Release\MyService.exe
assembly's progress. The file is located at
D:\MyService\MyService\bin\Release\MyService.InstallLog.
An exception occurred during the Install phase.
System.ArgumentException: Source MyServices already exists on the
local computer.
The Rollback phase of the installation is beginning. See the contents
of the log file for the
D:\MyService\MyService\bin\Release\MyService.exe assembly's progress.
The file is located at
D:\MyService\MyService\bin\Release\MyService.InstallLog.
The Rollback phase completed successfully.
The transacted install has completed.
And this is how i write log entry;
EventLog.WriteEntry("MyServices", logMessage, logType);
Can someone please help me what wrong i am doing.
I had a similar problem and solved it by:
Stop current service.
Close task manager, service manage tool and windows event viewer.
Use intallutil.exe /u to uninstall current service.
delete event log registry key of current service.(This is important!)
(\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\yourCurrentLogName)
You can find your current log and you can confirm your deletion under windows event viewer.
Use installutil.exe to install service again.
Restart Windows.(This is important, too!)
I'm not sure whether it is necessary or not. But I kept getting errors even I logged out.
Everything got fine since I restart windows.
(Maybe AWS cached something?)
Need to create a EventSource in this way:
if (!EventLog.SourceExists(source))
{
var eventSourceData = new EventSourceCreationData(source, logName);
EventLog.CreateEventSource(eventSourceData);
}
source - "MyServices"
logName - some of your program name.
Insert the data need in this way:
log = new EventLog();
log.Source = "MyServices";
log.WriteEntry(message, entryType);
I'm running sqlpackage.exe as park of an automated deployment script creation process, however we have synonyms in the database, which are different depending on the environment (Dev/Test/Live). The problem is that the database project has the synonyms as they are in the Dev environment, but when I run sqlpackage to compare against Test or Live, the synonyms are different and so they get scripted to be dropped and re-added to point to Dev.
I've seen on http://blogs.msdn.com/b/ssdt/archive/2015/02/23/new-advanced-publish-options-to-specify-object-types-to-exclude-or-not-drop.aspx that apparently there's a new parameter "ExcludeObjectType", but when I try running it using that parameter it gives me an error 'ExcludeObjectType' is not a valid argument for the 'Script' action (and I have the latest version of sqlpackage.exe).
Any ideas on what I can do here?
After downloading the latest SSDT for Visual Studio I still had the same issue. Next I downloaded Data-Tier Application Framework (May 2015) and used the new SqlPackage installed at C:\Program Files\Microsoft SQL Server\120\DAC\bin\sqlpackage.exe and the error went away and worked as expected.
Thank you sir! When I created the deployment script in VS, no change detected but when I tried to deploy using sqlpackage I got the error:
* The object [x] already exists in database with a different definition and will not be altered.
After adding the ExcludeObjectTypes switch I got the following error:
* 'ExcludeObjectTypes' is not a valid argument for the 'Publish' action.
But after downloading and installing latest Data-Tier App framework all works as expected with no errors.