After I installed a Microft Office 2016 on ** a SharePoint Server 2016 (Win 2016), the central admin had error **503 Service Unavailable. I opened Windows Service and saw that only one a SharePoint Administrator Service was started and I tried to start SharePoint Timer Service but it didn't start (Error 1053: "The service did not respond in a timely fashion"). Please help me.
Many thanks
To fix this issue, Install Office 2016 updates and then Repair the Microsoft SharePoint Server 2016 from Control Panel --> Programs and Features
Looks like we faced the same issue after installing MS Office 2016 64bit on SharePoint 2016 application server.
The fix was found in this article: SharePoint 2016 Forgets Where It’s Installed After Update.
If it looks like everything on a SharePoint server suddenly stops working, make sure the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\16.0\Location points to the right place.
In our case the value of that key was empty.
I believe simply repairing SharePoint server installation also would help.
Make sure All application pool are running in IIS. Sometimes this can happen. If application pool is down you get 503 error message.
I checked that and all applications are started. Everything is ok untill i install office 2016
Related
One of our client wants to move from TFS 2013 to TFS 2018. We don't have much information about the current TFS setup at client's end.
Can anyone please guide with what questions we need to ask to client to get the information regarding the current TFS system setup before we start with upgrade process.
Also share if there is any process document regarding upgrading the TFS 2013 to TFS 2018.
Thanks in advance.
You need to confirm the real requirements first, need to upgrade or migrate?
Check if the current device, OS and software match the Requirements and compatibility for the upgrade/migration :
Client operating systems:
TFS 2018 Windows 10 (Professional,Enterprise) Version 1607 or greater
TFS 2013 Windows 8.1 (Basic, Professional, Enterprise) Windows 7
(minimum SP1) (Home Premium, Professional, Enterprise, Ultimate)
SQL Server:
TFS 2013 Update 4 - SQL Server 2014 or SQL Server 2012 (minimum SP1)
TFS 2018 - SQL Server 2017 or SQL Server 2016 (minimum SP1)
Upgrade is a full data transfer. You will have all data in the previous TFS.
As TFS 2018 only supports SQL Server 2017 and SQL Server 2016 (minimum SP1), upgrade SQL Server is necessary.
You need to go through article Upgrade your deployment to the latest version of TFS before doing upgrade. And follow the steps in article Upgrade scenario walkthrough for Team Foundation Server to upgrade your TFS. Summarize the steps here:
Prepare your environment. The first step is to check the system
requirements for TFS 2018. Upgrade SQL Server is necessary for your
scenario. Including SQL Server, you also need to check other system
requirements and prepare the environment.
Expect the best, prepare for the worst. You must have a complete and
consistent set of database backups in case something goes wrong.
Do the upgrade. Once the preparation is done, you'll need to install
the new version of TFS to get new binaries, and then run through the
upgrade wizard to upgrade your databases.
Configure new features. Depending on what version you upgraded from,
you may need to configure each team project to gain access to some
of the new features made available.
Below threads for your reference:
https://blogs.msdn.microsoft.com/rob/2016/12/22/upgrading-from-tfs-2013-to-tfs-2017/
TFS 2012 to TFS 2018 Migration/Upgrade Path
On my development machine Lync 2013 client and Skype for Business both applications are installed. When attempting to call LyncClient.GetClient() compiled using the Lync 2013 SDK against Skype for Business the following exception is raised.
Generic COM Exception. Code is 0x80080005.
If I uninstalled the Lync 2013 client then it works perfectly.
For the Lync 2013 client development I have also used Lync 2013 SDK at that time I didn't get any exception.
Can anyone tell me that why this exception is raised when both applications are installed?
What do you mean by "Skype for Business"?
AFAIK the clients can't be installed at the same time (which is most likely the reason for problems I think). So you can only have one client installed at any one time.
Also the clients are confusing as well.
There are:
Lync Basic Client (with windows updated to Skype for Business 2015 UI)
Lync (full) Client as part of Office Professional Plus 2013 (with windows updated to Skype for Business 2015 UI)
Skype for Business Standalone (Office 2016 post install)
Hello I have installed management studio 2005(x64) alse I have microsoft sql server 2012 in my pc. But cant connect server due to dont know server name. (if sql server 2008 express were in my pc, default servername would be "./sqlexpress")
How can I connect server in my own pc ? And also I wanted to know;
Should I use another management studio ? can there be a problem use ms2005 with sqlserver 2012 ? Do you recemmond other studio ? (with exp. reason please)
Thank you anyone who just feel to help.
At least one of them must be a named instance. So, open the SQL Server 2012 version of SQL Server Configuration Manager, and see what the services say (and make sure the one you want to connect to is started - you can right-click to do so). Mine are all named instances:
So, if I wanted to connect to the SQL Server 2008 SP3 instance, I would use any of the following to connect:
.\SQL2008SP3
LOCALHOST\SQL2008SP3
(local)\SQL2008SP3
YOURMACHINENAME\SQL2008SP3
127.0.0.1\SQL2008SP3
The exception is if the subtext has (MSSQLSERVER) - this is a default instance rather than a named instance. In that case you would just connect to YOURMACHINENAME or ..
Also, no, you should not use Management Studio 2005 to manage SQL Server 2012 instances. In fact I think the above Configuration Manager won't show your 2012 instance. So before you do anything, you should uninstall the 2005 version of Management Studio, and go get the 2012 SP2 version here:
http://www.microsoft.com/en-us/download/details.aspx?id=43351
Click Download, the file you want is SQLManagementStudio_x64_ENU.exe. The nice thing about this version in 2012 SP1 is that it's the first version of SSMS Express that is actually fully functional and license free. Previously you had to live with limitations like no SQL Server Agent management, well those restrictions are now all gone.
(When you instal the client tools, this should also give you a new version of Configuration Manager, if your previous installation of SQL Server 2012 did not provide that for some reason.)
When eclipse tries to reconnect to TFS (username.visualstudio.com) the 'authentication window' is replaced by a window that seems to describe available services and the authentication process stops here.
The content of this window is as follows:
LocationWebService
The following operations are supported. For a formal definition, please review the Service Description.
ConfigureAccessMapping
Connect
QueryServices
RemoveAccessMapping
RemoveServiceDefinitions
SaveServiceDefinitions
SetDefaultAccessMapping
With VS2010 I can still connect to TFS without problems.
Also, both with eclipse and VS2010 I can connect to codeplex (tfs).
Clearing cookies and/or cache from IE or Chrome doesn't help.
Everything is fresh installed, so I assume it's up to date.
How can I resolve this issue with Eclipse - TFS - username.visualstudio.com?
I had to reinstall the 2013 version (https://www.microsoft.com/en-us/download/details.aspx?id=40785) and everything started working. It's either a bug in an older version or mismatch with the server version being connected to.
I have this issue too. It only happens when I try to connect myuser.visualstudio.com, with my domain TFS it can authenticate without any problem.
I see that you are running Windows 7, in my case the eclipse TFS stop working with Windows 8.
I have Windows 7 64bit. I had Sql Server 2008 R2 Express installed. I unistalled it and then I tried to install Sql Server 2008 R2 Web. Unfortunatelly on the Setup Support Rules page for 'Consistency validation for SQL Server registry keys' I got 'Failed'. I spent half of a day trying to solve it, but then I assumed that there must be realy something wrong with registry keys and it will be faster just to reinstall Windows.
After formatting the disk and reinstalling Windows 7, rebooting dozen of times I installed all Windows upadtes as well. I also did install some programs like Skype, Thundirbird etc. which has no influence on Sql Server setup.
And then I tried again to install Sql Server 2008 R2 Web. And again an error. A bit different one. Now when the setup is on the Setup Support Rules page I get an error message box with the title "FixSqlRegistryKey_x86 - Application Error" and content: The application was unable to start correctly (0xc000007b). Click OK to close the application. 'Consistency validation for SQL Server registry keys' gets 'Failed' status as well.
My team mate has exactly the same machine as mine. He had no problem with installation (he didnt even need to reinstall Windows).
I run the setup as administrator, from a local folder. I even tried to use the setup files copied from my team mate, for a case if my copy is corrupted. In the setup options I have chosen the 'x64' version.
Any ideas what can be the reason of the problem?
Problem solved.
Someone suggested to me that Web edition should not be installed on Win 7 (just on Windows Server). So perhaps installing a different version would work. My team mate perhaps succeeded acidentially - due to having sql server installed already in express edition... but it is just a guess.
Before I tried to install another edition of SqlServer, I downloaded 2008 Express version and I started the install. From the temporary folder created by the express edition I copied FixSqlRegistryKey_x86.exe file and I had overwritten the problematic file in the Web setup with this file.
I started the setup again. It passed the verification this time. But has crashed on a later point - setup unpacks the installation files to C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2 and runs from it. So I needed to again overwrite the problematic file in this location. Now the installation succeeded.