Thursday, 13 February 2020

unable to share files through skype for business 2015 between internal and external users

Hi,
on the front end servers of Skype for business 2015, i was getting Errors/informaitons, with event IDs:  41024,41025, 41026
Event: 41024
No connectivity with one of the Web Conferencing Edge Servers.
Edge Server Machine FQDN: server1.domain.com, Port:8057
If the problem persists this event will be logged again after 20 minutes
Cause: Service may be unavailable or Network connectivity may have been compromised.



Event ID: 41025
Connection to the Web Conferencing Edge Server has succeeded
Edge Server Machine FQDN: server1.domain.com, Port:8057
Event ID: 41026
No connectivity with any of Web Conferencing Edge Servers. External Skype for Business clients cannot use Web Conferencing modality.
Cause: Service may be unavailable or Network connectivity may have been compromised.
Resolution:
Verify all Web Conferencing Edge Services in the topology are running, and network connectivity is available.

Errors:
No connectivity with one of the Web Conferencing Edge Servers.
Edge Server Machine FQDN: server1.domain.com, Port:8057
If the problem persists this event will be logged again after 20 minutes
Cause: Service may be unavailable or Network connectivity may have been compromised.

Solution:
add the following key to resolve this issue.
reg add HKLM\SOFTWARE\Microsoft\.NETFramework\v4.0.30319\System.Net.ServicePointManager.RequireCertificateEKUs /v “C:\Program Files\Skype for Business Server 2015\Web Conferencing\DataMCUSvc.exe” /t REG_DWORD /d 0 /f


After adding the above key on the front end servers and restarting the "Skype for Business server web conferencing" service, the above errors were not appearing any more and the issue of file shares etc. was resolved.

https://support.microsoft.com/en-in/help/4023993/ls-data-mcu-41026-41025-and-41024-after-may-2017-net-framework-update

Tuesday, 8 October 2019

How to find that from which Windows update server (WSUS) your client machine getting updates


Just go to the following path in the registry key and you will have the name of the server.

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

WUStatusServer: http://servername.dom.com:8530

Thursday, 26 September 2019

There has been some issue identified and fixed with LDM. Please uninstall the LDM through control panel and click here to install the latest version.

I was getting the following error while trying to download any file from Microsoft site (https://learningdownloadcenter.microsoft.com/Home/DownloadQueue).

Error
""ALERT: There has been some issue identified and fixed with LDM. Please uninstall the LDM through control panel and click here to install the latest version. Apologies for the inconvenience. The later versions of LDM should be able to update through automatic update prompts and would not require the manual uninstall step. "


My issue was resolved in this way.
 1: Download the latest LDM from Microsoft official site
 2: Once the download complete then RUN the installation
 3: In installation it detected the old install LDM so it ask for Repair and uninstall of old LDM
 4: Select Uninstall the old LDM
 5: then re-RUN the installation of latest LDM
 6: after successful installation, my issue was resolved. 

Friday, 12 July 2019

Lync Server Access Edge was unable to start



Error in system logs in event viewer
"The Lync Server Access Edge service terminated with service-specific error %%-2146762487."

Reason:
The root CA who issued certificate for lync edge server, certificate was not in the intermediated certificate store of edge server.
after importing the CA certificate in intermediate store, the Lync Server Access Edge service was started normally and the above error from the event viewer was also removed.

Monday, 29 April 2019

Resolved: 451 4.7.0 Temporary server error. Please try again later.

I have Exchange server 2013 environment with 3 mailbox and 2 Edge servers. I got mail flow issue that email coming from Edge servers to Mailbox servers were stuck in Queue. after looking into the Queue and got the error "451 4.7.0 Temporary server error. Please try again later." on both Edge servers.
after look into the Mailbox servers I found heavy load on the mailbox Servers. CPU and memory were reaching to 100%. So after decreasing the load on the all three servers by moving some DBs to DR site and restarting the Microsoft exchange Transport services on the mailbox servers, the load become decreased, then restart the same services on the EDGE servers as well, the Queue become on decreasing.
So the mail Queues were on both Edge servers were due to load on the all 3 mailboxes Servers on PR site not any issue with Edge Servers.

Friday, 22 March 2019

GPresult /r does not show computer settings

Today i have to test a new GPO settings, for testing on client machine i ran the GPResult /r command but found that there were no computer settings in the result of GPResult /r command i which i was more interested as the GPO was applied on computer Object.
So i was trying different way, and one was to open the Command prompt with Administrator rights.
So after start the command prompt with Administrator rights and running the GPResult /r i got the required computer settings in the result/output.

 

Wednesday, 13 March 2019

Windows updates failing with error 80072ee2 on Windows Server 2008 R2


Today i faced an issue that i was unable to install windows updates on windows server 2008 R2.  was getting this "80072ee2" error code in windows updates error. 


ERROR Code:     80072ee2

Description:       above error was generated during windows updates

Solution:             Re-register WU DLLs - Run the following commands on elevated cmd.exe and re-register Windows update DLLs.

                                regsvr32 oleaut32.dll

                                regsvr32 jscript.dll

                                regsvr32 vbscript.dll

                                regsvr32 softpub.dll

                                regsvr32 msxml.dll

                                regsvr32 wintrust.dll

                                regsvr32  initpki.dll

                                regsvr32 cryptdlg.dll

P.S: My issue was resolved after registering above *. dll . please note that there may be some other solutions as well and should be resolved accordingly.