This solved my problem perfectly, thank you!

You saved my day, Joe. There was no indication in the logs where to search for this error.

Hi! Thank you, i had the same Problem, you saved my day too!

I got this exact error, but in my case the Standard Edition pool name already was the server name.

THE PROBLEM for me was that on my Lync server, the FQDN (e.g.: lync.mydomain.local) was resolving to the ipv4 adres, where as the hostname (lync) was resolving to the ipv6 adres. So, browsing to the Lync file store share from the same Lync server using the FQDN (e.g.: \\lync.mydomain.local\share) popped up a credentials screen, instead of opening the share as I would've expected and as was the case when browsing to the share using just the hostname (e.g.: \\lync\Share). So the credentials for the FQDN were not known yet to the Lync server.

I SOLVED this by going the computer/domain/workgroup etc settings (right-click computer -> Properties -> Change Settings -> Change -> More and set the 'Primary DNS Suffix for this computer' to the primary domain (e.g.: mydomain.local) and checked 'Change Primary DNS suffix....'

After a reboot, the FQDN of the Lync server was resolving to the ipv6 adres and thus browsing to the Lync file store share worked without having to provide credentials and I was able to build the Lync Topology successfully!

Not sure why the DNS suffix entry was missing though, but either way...it now works! ;)

Thank you Joe, problem solved.

You absolute star. That had me stumped until I found this post.

Thanks that was exactly the problem I had too.

Thanks, this was our problem too!

Thanks for the post. Your a star

Hi Joe, you are the man!! You save my job and my Project, thank you so much.

Thanks Joe.. Awesome information, that did the trick..

Thank you very much, "Name"

Thank you, thank you !!!!!!!!!! so much !!!!!!!!!!!!!!!!!!!!!!