Comments by Member 11303379

Member 11303379 15-Dec-14 7:44am View

Actually we aren't calling any function of the service, only url to it. So, we couldn't identify where it is going to check any index.

And surprisingly same service works on other domain on same server.
You can check below url for same service:
http://eplannerpro.com/app/JSON/UserService.svc

Member 11303379 15-Dec-14 6:32am View

Thanks Nijboer for taking interest in our question.
We have solved the issue by giving reference to the DLL of the bin folder.

Member 11303379 15-Dec-14 0:11am View

Yes, The versions are same. I checked %windir%\assembly there was no "System.DirectoryServices.Protocols" but there was "System.DirectoryServices" which had same version as the DLL.

Member 11303379 12-Dec-14 7:09am View

Yes. Only domain is different.

Member 11303379 11-Dec-14 23:26pm View

Below is the error we are getting :

"Server Error in '/app' Application.

Could not load file or assembly 'System.DirectoryServices.Protocols, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileNotFoundException: Could not load file or assembly 'System.DirectoryServices.Protocols, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Assembly Load Trace: The following information can be helpful to determine why the assembly 'System.DirectoryServices.Protocols, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' could not be loaded.

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]."

Comments by Member 11303379 (Top 5 by date)