tag:blogger.com,1999:blog-90541469204507334502024-09-11T14:23:57.459+12:00This blog is a collection of my experiences and findings in the Lync world. It is intended to document my experiences, and at times frustrations, with Microsoft's Lync and surrounding technologies. And more importantly...offers a central database for quick reference. This blog is separate from LyncSorted and thus runs its own subscriber feeds. Unknownnoreply@blogger.comBlogger55125tag:blogger.com,1999:blog-9054146920450733450.post-65838762439799678862014-08-07T07:19:00.000+12:002014-08-07T07:19:00.784+12:00

Issue The issue was seen when installing the latest CU. When installing the SQL part of a cumulative update you get the error:- Install-CsDatabase : Command execution failed: Cannot find any suitable disks for database files. You must manually specify database paths. Solution The "suitable disks" error is triggered by the installer checks. The requirement is that a minimum of 16 GB of

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-9054146920450733450.post-88708863157270254492014-07-25T11:07:00.001+12:002014-07-25T11:08:17.620+12:00

Issue After following the basic install procedure I attempt to look at the Office Web Apps Farm configuration with the PS command Get-OfficeWebAppsFarm. The following error is thrown.. Although many blogs explain that this issue is related to installing on a different drive than C, or that its specific to Windows Server 2008 or 2012 Solution I found that (IMHO) the issues was unrelated

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-9054146920450733450.post-53017520427760992612014-07-15T11:37:00.000+12:002014-07-15T11:37:57.158+12:00

There are some really good resources available on how to setup SIP trunking between Lync and Microsoft Certified gateways (such as Sonus and Audio codes). One of my favorite resources is from Iain Smith at NorthernLync found here Problem Unable to set the port to 5061 when adding a PSTN gateway in Lync Topology builder.   Notice how finish is grayed out and we have an

Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-9054146920450733450.post-87416937412276691962014-07-15T10:00:00.000+12:002014-10-01T20:48:07.728+13:00

Problem I came across an interesting issue yesterday..opening the Lync Management Shell I was presented with a blank shell window (nothing unusual there, just wait a few seconds, right?). However it just stayed right there, no connecting. The environment is really a 4 site deployment with a total of 4 2013 front ends all running on Windows 2012 R2. What was really interesting was that

Unknownnoreply@blogger.com2tag:blogger.com,1999:blog-9054146920450733450.post-8060272468659210192014-06-27T16:48:00.001+12:002014-07-11T12:04:57.062+12:00

Problem The old Lync 2010 Server\Pool was discovered when running ExchUCUtil. The image below depicts the 2 Pools I was expecting to see 1:2 and 1:1 BUT I wasn't expecting 1:4. So when Lync is initially deployed a bunch of references are made in AD, of course if you remove Lync from the environment and don't do so gracefully then a bunch of unwanted references are .

Unknownnoreply@blogger.com3tag:blogger.com,1999:blog-9054146920450733450.post-55413221390935833872014-06-25T07:00:00.002+12:002014-06-25T07:00:31.713+12:00

Problem From time to time you may find that the deployment wizard fails at setting the permissions required to the Lync Share folder. Product Version - Lync 2013 What permissions are required? Solution Usually running the Topology builder as Administrator does the trick Alternatively you could manually set the permissions from the Advanced Sharing button

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-9054146920450733450.post-88200139197870066352014-04-16T22:36:00.000+12:002014-04-16T22:36:19.878+12:00

OK so if you are OCD (and nothing wrong with that) then you may be compelled to make the event warning on your front end reporting on Invalid numbers every morning just after 1:30 am. The Event ID 21034 explains as follows: Its arguably one of the most comprehensive and helpful Cause and Resolution events you may ever see! The Process When Lync collects the user data from Active

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-9054146920450733450.post-31956695778113430432014-03-25T10:38:00.001+13:002014-03-25T10:38:41.413+13:00

After a fresh install of Lync 2013 Standard Edition onto a Windows 2012 server, and its been running for about 2 weeks I may add...I came across the following issue Issue After a reboot of the Lync Standard Edition Server I found that the Lync Server Front End Server (RTCSRV) wouldn't start. It just sat there on "Starting" Further Symptoms Event ID 32174Interestingly the Event ID reports that

Unknownnoreply@blogger.com8tag:blogger.com,1999:blog-9054146920450733450.post-33191791185020848942014-02-05T16:57:00.000+13:002014-02-06T06:24:54.815+13:00

The Problem When Running the Lync Server Deployment Wizard - Install oe Update Lync Server System - Step 2: Setup or Remove Lync Server Components I get an error immediately after Disabling unused roles The Error Input string was not in the correct format at System.Text.StringBuilder.AppendFormat(IFormatProvider provider, String format, Object[] args) at System.String.Format(IFormatProvider

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-9054146920450733450.post-83537327625418680872014-01-29T14:42:00.001+13:002014-01-29T14:42:39.463+13:00

The Problem Lync Phone Edition (in my case Polycom CX500 and CX600) wont sign in to Lync from externally. Internally working fine. The phone goes through the steps of finding the time server, then finding the Lync Server - OK. Then gets stuck on Signing in... Connecting to Lync Server This also happened to the CX600 EVEN when pairing to my desktop over USB for sign in... The 

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-9054146920450733450.post-81538790148623521092014-01-21T13:21:00.001+13:002014-06-18T06:43:31.969+12:00

IssueThe Lync phones (CX500 and CX600) no longer sign in to Lync 2013. Error message states "Please verify that the domain entered is correct"After factory resetting the phone I still got the same error briefly followed by "Sign-in canceled due to internal error.Please try again" I tested to see if the credentials were working with:Test-CsPhoneBootstrap -PhoneOrExt "2705" -PIN "12121"I checked

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-9054146920450733450.post-77780851754410071332013-12-11T15:45:00.000+13:002014-04-06T16:24:13.714+12:00

Issue Unable to call UM Evidence Every time a call is made to the UM server the following error is logged on the Lync server front end:- Log Name:      Lync Server Source:        LS Exchange Unified Messaging RoutingDate:          10/12/2013 09:27:05 PMEvent ID:    &

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-9054146920450733450.post-27083082478589663762013-11-05T21:19:00.000+13:002013-11-06T21:36:27.655+13:00

Just recently I added another 2013 Front End Server to an Enterprise Pool and was subsequently presented with some interesting issues. After adding the new Front End to the Topology and running the setup I moved on to migrating some test users and saw the following error: Distributed Component Object Model (DCOM) operation SetMoveResourceData failed?? I checked the replication and all Lync

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-9054146920450733450.post-50919624587272017002013-11-04T21:32:00.000+13:002013-11-06T21:34:08.904+13:00

Issue Whilst deploying Lync Enterprise Edition with 3 Front End Servers I cam across an interesting issue. FE 1 was fine but when I fired up FE 2 and got to the certificate wizard the OAuth Certificate was missing. One thing you will notice if there is no OAuth certificate is that the Lync Front End Service wont start. OK so where is the cert??? Found a good blog explaining the purpose of

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-9054146920450733450.post-34026127131963167622013-11-01T21:25:00.000+13:002013-11-06T21:26:15.183+13:00

So "Lync Rescue" continues to keep me busy... Issue Got asked to look at why a Lync Edge Server wont replicate. Cause Seems that that the External IP addresses of the Edge server are resolving to Edge Server internal FQDN Resolution Correct DNS, the only DNS entry for the Edge Server should be the internal facing IP address resolving to the Edge Servers FQDN.

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-9054146920450733450.post-53981599661447186072013-10-16T06:45:00.000+13:002013-10-31T06:46:07.783+13:00

Issue Publishing Topology Completed with Errors - Microsoft.Rtc.Applications.TestBot What is Testbot? Testbot is the little fella that runs the Audio Test Service You can see TestBot SIP Address woth the Lync Server Management Shell command: Get-CSAudioTestServiceApplication OwnerUrn: urn:application:testbot SipAddress: sip:RtcApplication-0e0e407a-6283-4c93-99fa-c0e252b8af09@lynclab.local OK

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-9054146920450733450.post-69425559329894265062013-10-10T05:48:00.000+13:002015-05-21T09:35:32.060+12:00

As part of ongoing expansion we recently added another DDI range. Most of the new range would be dormant initially. Of course I wanted to catch all the calls that were unassigned and send them off to a RGS. Here is where the plot thickens... This seemed to work well in Lync 2010, now I find myself on 2013 and see a few interesting new features...like trunk-to-trunk routing. So I ring the

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-9054146920450733450.post-75904479876510301542013-09-30T20:15:00.000+13:002013-10-14T20:16:32.973+13:00

Issue Today I found a Warning that was filling my Lync 2010 Front End event Log. Event ID 31196 every 2 minutes Collaboration platform has failed to provision the data. Collaboration platform has failed to provision the data because of the following exception: Exception: Microsoft.Rtc.Collaboration.ProvisioningFailureException:Cannot read contacts from Active Directory: Active Directory server

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-9054146920450733450.post-88761243327624378762013-09-29T11:07:00.000+13:002013-10-31T05:54:10.445+13:00

Yesterday I was cutting over a SIP Gateway from a 2010 pool to a newly built 2013 pool. Migrating the gateways and Trunk configuration is really simply. What surprised me though is that once I had made the required config changes and published the Topology I was unable to make or recieve calls. Looking at the SBC Gateway I found the error SIP 503 Service Unavailable for each attempted call

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-9054146920450733450.post-33105302101945895062013-08-12T09:38:00.000+12:002013-09-22T08:06:02.776+12:00

Got asked to solve an issue where Voicemail for users in a Lync onprem, UM in cloud environment had mysteriously stopped working. The FE event log had this to say Running Lync Traces showed the following Followed by the Error So as exchange UM is in the O365 cloud and the event says to check that off I went. Steps to check O365 UM configuration with Lync on premise I'll

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-9054146920450733450.post-39053195838466419392013-08-06T10:35:00.000+12:002013-09-22T08:02:14.481+12:00

When publishing our Lync Topology I'm getting the following error on the Enabling Topology step: Error: Found multiple objects with identity "lyncFE01.lynclab.local,McxInternal" in Active Directory. ▼ Details └ Type: ActiveDirectoryException └ ▼ Stack Trace └at Microsoft.Rtc.Management.Deployment.Core.CompatTrustedService.GetTrustedService(ADSession

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-9054146920450733450.post-89586647665501006302013-08-06T08:50:00.004+12:002013-09-22T08:00:20.934+12:00

Issue Change of IP to SIP SBC causes one way speech for outbound calls. SDP shows internal IP on call setup Solution Force the deployment to use fixed addresses in topology, publish. Then remove this (remember to visit the PSTN gateways tab) publish. You should have no IP's set when running  get-csnetworkinterfaces for PSTN

Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-9054146920450733450.post-84660414808881477182013-08-06T08:49:00.003+12:002013-09-22T07:59:58.448+12:00

Problem You get the error message "Lync cannot verify that the server is trusted for your sign-in address" Cause When Lync Communicator discovers the Lync FE to log on to it uses the SRV Record _sipinternaltls._tcp.SIPDOMAIN.com. If the associated server FQDN is resolved to a server that doesnt match the SIP DOMAIN then this error is presented.EG Below record is for DNS zone xxx.co.nz,

Unknownnoreply@blogger.com0tag:blogger.com,1999:blog-9054146920450733450.post-74949853643157311342013-08-06T08:48:00.002+12:002013-09-22T07:59:14.275+12:00

Problem Get a second prompt for credentials when logging in with the following text.. "Type your user name and password to connect for retrieving response groups" Solution The Lync Share needs to have read\write permissions to itself and containing folders. Corrected in the Advanced Sharing tab as below. 

Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-9054146920450733450.post-63965430122190787482013-08-06T08:35:00.003+12:002013-09-22T07:56:05.000+12:00

Problem Can't connect to the Lync Server control Panel directly but https:\\FQDN\cscp works Solution Something I didn't realize is that the Control Panel uses the DNS _sipinternal SRV Record. This is the record in the DNS branch matching the SIP Domain and not necessarily the branch that matches the internal DNS naming.

Unknownnoreply@blogger.com0