I have a Windows Server 2012 R2 with TFS 2015 Update 2 installed. I configured Scheduled backups in TFS Administration Console.
When I manually take a full backup, everything works and the backupfiles are nicely dropped on a networkshare.
However, the automatic backup (at night) fails.
From the event viewer: Exception Message: Cannot open backup device '\\...\Tfs_Configuration_9859327876866326120F.bak'. Operating system error 0x80090006(Invalid Signature.).
BACKUP DATABASE is terminating abnormally. (type SqlException)
Help is much appreciated!
Mapping the network drive solved the problem!
Related
I have created an Ec2 instance on AWS in eu region. it is a t3 small instance. I have installed apache and laravel on it for some API development.
I have configured visual studio code to connect remotely to the EC2 instance for remote development. When i connect first time then it works. However, if i don't use the visual studio code for some time, the session times out. The next time when i open the visual studio code, it tries to reconnect. That is when the problem starts. It usually tries to reconnect and then asks me to reload the window or reconnect. When I click on either of these, the EC2 instance becomes unresponsive. Even the FTP and HTTP connection stops working.
Today, I tried to debug further and opened the EC2 console in my browser. What i found was the EC2 instance was running but there was an error that said System check failed (1/2)
This i found only today but I have observed this pattern for the third time. I tried to look further in EC2 to see if the memory or CPU became full at some time when the visual studio code reconnected but I did not see any such thing.
Can someone please guide me how to debug this further and fix this?
Syed
We have installed VisualSVN server 3.5 on windows server 2012 r2. When we browsing the repository in the VisualSVN Server Manager, WMI provide host process has started and it uses the very very less cpu usage(4%) even overall CPU usage is less(20%). This means WMI is very slow in background.
we have the script to set the VisualSVN permission using WMI, this WMI query also failed with unknown cause.
Please, describe the issue in detail. It is hard to tell what the root cause is from the current issue summary. Checking VisualSVN Server logs and Windows Application / System / WMI logs can help.
Note that you can always contact support#visualsvn.com for assistance.
we have the script to set the Visual SVN permission using WMI, this
WMI query also failed with unknown cause.
Try the *-SvnAccessRule PowerShell cmdlets such as Get-SvnAccessRule, Add-SvnAccessRule and Set-SvnAccessRule. The access rule management cmdlets help you automate permission management, perform permission modifications in batch and generate permission reports.
IMPORTANT: VisualSVN Server 3.5.x release family is out of support since February 28, 2018. 3.5.x release family does not receive patch updates. Please, plan to upgrade your VisualSVN Server instance to the latest version, VisualSVN Server 3.9. Read the article KB138: Upgrading to VisualSVN Server 3.9 before beginning the upgrade. For the complete list of changes between version 3.5 and 3.9, take a look at the changelog.
I am getting below error when trying to login into my AWS EC2 instance. Last login was around 2 weeks back and everything was working fine so the password I am using is correct. No other information is available on the error message.
Is there a way I can see any logs through management console ?
Appreciate any help on this.
Remote Desktop Connection
An authentication error has occurred.The function requested is not supported
It seems like you are facing this issue.
Bottemline, This is caused by a Microsoft Security Patch. The Microsoft Security patch issued on Tuesday, May 8th 2018 triggered the problem by setting and requiring remote connections at the highest level.
Simply adjust the Remote Desktop settings on the host machine to a lower security level. From File Explorer, choose Computer, right-click and select Properties, then click Change Settings, and go to the Remote tab.
From Windows 10, uncheck the option to “Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)”
From Windows 7, it’s setting the option to the Less Secure option rather than More Secure
Once these are set, users can remote to the machine again.
If you don't have any other way into the machine except Remote Desktop, I'm afraid the machine is lost.
For anyone facing this issue. Below is response from AWS technical support team:
Looking at the error message you posted, this is due to a recent patch (KB4103727) that Microsoft has released to fix a vulnerability. It is a mandatory requirement from Microsoft that both the client machine (the computer from which you are trying to RDP into your instances) and the remote server (your EC2 instance) has the latest updates installed. If one of these machines has the latest updates installed and the other does not, RDP connection would fail.
Note: If you see your Windows is up to date and you do not see the KB4103727 installed, it could be a different KB article which applied the KB4103727 as a cumulative update. If this is the case, please uninstall all KBs that were installed recently before the RDP connection was broken.
For more information about this hotfix, please refer to the Microsoft documentation below:
https://blogs.technet.microsoft.com/yongrhee/2018/05/09/after-may-2018-security-update-rdp-an-authentication-error-occurred-this-could-be-due-to-credssp-encryption-oracle-remediation/
https://support.microsoft.com/en-us/help/4093492/credssp-updates-for-cve-2018-0886-march-13-2018
There are multiple workarounds for this issue:
Option 1: If the update is installed on your client (workstation) and is not installed on your EC2 instance.
Uninstall KB4103727 from your client machine. After you uninstall the KB and gain RDP access to the EC2 instance, you can patch the instance with latest updates first and then update your client machine with the KB by running Windows Update again.
Alternately, you can keep your client machine updated and you can install latest Windows updates on your EC2 instance remotely using SSM Run Command. For detailed instructions on how to configure your instance to use SSM Run Command, please refer to the below documentation:
SSM Prerequisites: https://docs.aws.amazon.com/systems-manager/latest/userguide/systems-manager-prereqs.html
Run Command Tutorial: https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/tutorial_run_command.html#rc-tutorial-ui
After you configure your instance to use SSM Run Command, you can execute the Run Command document "AWS-InstallWindowsUpdates" remotely on your instance.
Option 2: If the KB is installed on your EC2 instance and is not installed on your client machine
Run Windows Update on your client machine and install latest software updates. Once the latest updates are installed on both your instance and the client machine, you should be able to RDP into the instance.
Alternately, if you have a backup AMI or an EBS snapshot created before the patch was installed on your EC2 instance, you may consider restoring your instance from the backup to roll back the installed software updates.
Option 3: There is a workaround suggested by third party websites to disable the check altogether on the unpatched Windows machine and RDP should work normally. On the unpatched machine, open a command prompt with Administrator privileges and run the command mentioned below:
reg add "HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters" /f /v AllowEncryptionOracle /t REG_DWORD /d 2
Please note, you may have to reboot your Windows machine for the changes to take effect after you install/uninstall the KB.
So, finally I had to uninstall mentioned update from client machine(using which I was trying to connect to the aws instance) which allowed me to connect to the instance. Once connect, I updated the instance with windows updates and rebooted it which resolved the issue.
I am trying to create a new VM on ESXI 6.0 using a Windows Server 2012 R2 .iso file.
After selecting all VM options and when finalizing the creation, the process fails with the following extremely informative message:
Failed - Invalid configuration for device '5'.
Any help would be highly appreciated.
My only concern is that ESXI by default does not offer the very specific option of selecting Windows 2012 R2 Server as OS (check attached image) - so I dont' know if this is causing the failure.
(I am selecting just Windows Server 2012, without the R2 since it doesn't exist)
Device 5 stands for IDE controller.
I managed to solve the similar issue by creating the VM without attached HDD and SCSI controller (WinServ 2016 in my case). Then you can try to attach a HDD and Controller lately.
I am trying to remote debug an Asp.Net Core Web Application (with Web API) project deployed as an Azure App Service with Visual Studio 2017 Professional.
Followed the instructions as documented here. Essentially, using the Server Explorer-->App Service-->Attach Debugger
Also, enabled the necessary firewall ports as mentioned. The ones I opened are TCP (4022, 4023) and UDP (3702). Also, ensure remote debugger application is in allowed list of apps in Windows Firewall. Documentation for the firewall steps.
Despite all the settings, I am getting following error
System.Runtime.InteropServices.COMException (0x89710023): Unable to connect to the Microsoft Visual Studio Remote Debugger named 'essamplepoc2.azurewebsites.net'. The Visual Studio 2017 Remote Debugger (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because a firewall is preventing communication to the remote computer. Please see Help for assistance on configuring remote debugging.
at Microsoft.VisualStudio.Debugger.Interop.Internal.IDebuggerInternal120.ConnectToServer(String szServerName, VsDebugRemoteConnectOptions[] pConnectOptions, CONNECT_REASON ConnectReason, Int32 fIncrementUsageCount, IDebugCoreServer3& ppServer)
at Microsoft.VisualStudio.Web.Azure.MicrosoftWeb.Operations.RemoteDiagnosticsSessionBase.ConnectToServer(String site, String user, String password)
Any suggestion would be helpful.
The issue is resolved. We had to open outbound ports 4024 for VS 2019, 4022 for VS 2017 and 4020 for VS 2015 on corporate firewall.
For more info check these out:
https://learn.microsoft.com/en-us/visualstudio/debugger/remote-debugger-port-assignments?view=vs-2019
https://learn.microsoft.com/en-us/visualstudio/debugger/configure-the-windows-firewall-for-remote-debugging?view=vs-2019
I also had this problem. I solved it by changing the Platform from 32-bit to 64-bit in Application Settings as I am trying to debug from 64-bit machine.
It seems remote debugging is not turned on for your App Service.
Open your App Service in the Azure portal and go to Application Settings. Then turn Remote Debugging to On and select Visual Studio Version to 2017.
It should look like this:
Screenshot source
I hope this helps.
First, what did NOT work. Opening the port in my Firewall did not work for me. Restarting my local machine did not work, neither did restarting the app in Azure, nor updating VS2019 with the installer. I kept getting:
System.Runtime.InteropServices.COMException (0x89710023): Unable to connect to the Microsoft Visual Studio Remote Debugger named 'empirepipedriveapi-newversion.azurewebsites.net'. The connection with the remote endpoint was terminated.
Finally, what DID work, I deleted the deployment slot and then added it again, I deleted the publish profile in Visual Studio 2019 and recreated it again, a published the app (without even recompiling it) and then WAS able to connect (I did refresh the available slots in the Cloud Explorer first just to be overly careful). I believe, and this is the 2nd time in about a year, that, on rare occasion, the deployment slot can become corrupted. I noticed this time when I published the app, it took longer and it seemed much more activity took place, leading me to believe that there was code in the old slot that was is not refreshed on each and every publish and it must have become corrupted.