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)
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
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
We have a classic ASP application we just migrated from Windows 2008 R2 to Windows 2012 R2 Core.
Apparently Core versions of windows don't include cdosys or cdonts and thus our application can no longer send email.
Most of the advice I can find suggests using system.net.mail for sending email which of course is a .NET technology and we're using classic ASP.
We do have .NET on our system but I'm not sure if classic ASP could talk to a .NET page for sending email?
Besides using a 3rd party COM utility like Persits ASPEmail are there any native ways of working around this?
We do NOT want to convert the server core instance to the full version of windows. That's killing an ant with a bazooka. This is only impacting two places in our code and everything else works just fine on core.
Unfortunately, CDONTS was superseded by CDOSYS some time ago. When migrating from Windows Server 2008 to Windows Server 2012 I had this exact same issue, but managed to find a fix.
It involves taking a copy of the cdonts.dll file from the Windows Server 2008 Server and adding it to the Windows Server 2012 server then registering it with the relevant COM subsystem without any need to change code or install a 3rd Party library.
Hopefully the same method will work with Core but I haven't tested it.
I have a Com Add-in for Office 07,2010 created in VS 2008 , .net 2.0. implementing IDExensibility2 and IRibbonExtensibility.
Com Shim dll - C++
Rest all code -C#
I need to upgrade this project to Office 2013, i have read online that it doesn't require any change, the same com add-in should work properly for Office 2013.
I created solution files for office 2013 with office15 object library. The build was successful.
But when i deploy dll's and register the Com Add-in , it shows in active Add-ins but there is no log at all. (meaning Office is not even taking it up).
Not even Onconnection() is called.
Is there anything i am missing? Pls help
Can both clients be installed and used at the same time ?
The purpose of using both is based needs to develop for Lync 2010 while still using Communicator 2007 in a corporate environment. Or would a developer be forced to have two different machines/VMs/boot environments ?
No - you can't run both side-by-side. Installing Lync will uninstall Communicator.
However, you can use a registry hack (unsupported, unfortunately) to enable your copy of Lync to run against your OCS infrastructure. This works for R2, not 100% sure about R1.
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator]"DisableServerCheck"=dword:00000001
If you're serious about Lync development, the best solution is to build a server environment specifically for developing against.