|
 Posted 2/13/2007 10:49:02 AM |
| | We get the following error message:
Server Error in '/dCRM' Application.
--------------------------------------------------------------------------------
The underlying connection was closed: The remote name could not be resolved.
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.ComponentModel.LicenseException: The underlying connection was closed: The remote name could not be resolved.
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.
Stack Trace:
[LicenseException: The underlying connection was closed: The remote name could not be resolved.]
c360.Toolkit.Licensing.c360LicenseProvider.ᜀ(LicenseContext A_0, Type A_1, Object A_2, Boolean A_3) +1091
c360.Toolkit.Licensing.c360LicenseProvider.GetLicense(LicenseContext context, Type type, Object instance, Boolean allowExceptions) +18
System.ComponentModel.LicenseManager.ValidateInternalRecursive(LicenseContext context, Type type, Object instance, Boolean allowExceptions, License& license, String& licenseKey) +326
System.ComponentModel.LicenseManager.ValidateInternal(Type type, Object instance, Boolean allowExceptions, License& license) +44
System.ComponentModel.LicenseManager.Validate(Type type, Object instance) +31
c360.Toolkit.SDK.Pages.AreaPage..ctor() +29
dCRM.FullHistory..ctor() in c:\inetpub\wwwroot\dCrm\ActivityReport\FullHistory.aspx.cs:25
_ASP.FullHistory_aspx..ctor() +6
[TargetInvocationException: Exception has been thrown by the target of an invocation.]
System.RuntimeType.CreateInstanceImpl(Boolean publicOnly) +0
System.Activator.CreateInstance(Type type, Boolean nonPublic) +66
System.Web.UI.TemplateControlParser.GetCompiledInstance(String virtualPath, String inputFile, HttpContext context) +164
[HttpException (0x80004005): Failed to create page of type '_ASP.FullHistory_aspx'.]
System.Web.UI.TemplateControlParser.GetCompiledInstance(String virtualPath, String inputFile, HttpContext context) +340
System.Web.UI.PageParser.GetCompiledPageInstanceInternal(String virtualPath, String inputFile, HttpContext context) +43
System.Web.UI.PageHandlerFactory.GetHandler(HttpContext context, String requestType, String url, String path) +44
System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, String path, String pathTranslated, Boolean useAppConfig) +698
System.Web.MapHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() +95
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +173
|
| | Posted 2/13/2007 7:10:22 PM |
| | The remote name could not be resolved. The most likely reason for this problem is that the web service URL is misconfigured. Please review the step by step installation instructions: http://www.c360.com/Forums/Topic693-40-1.aspx and pay attention to step number 7.
|
| | Posted 2/15/2007 1:10:14 PM |
| | | In reply on behalf of markm: Double checked the web service urls and they are correct. Anything else that can cause this? |
| | Posted 2/15/2007 3:06:14 PM |
| | The error says that the "remote name could not be resolved" which leads me to believe that you should try using the IP address instead of the server name.
|
| | Posted 2/16/2007 11:27:23 AM |
| | | No, we are using the server name. The SQL server is on a seperate box from the CRM web server so that could be a factor. What will it be trying to resolve? |
| | Posted 2/16/2007 11:38:37 AM |
| | I know you are using the server name. that's why I suggested your should use the IP address instead. This would eliminate any need to "resolve" the server name.
|
| | Posted 2/20/2007 11:02:17 AM |
| | Digiterre (2/16/2007)
No, we are using the server name. The SQL server is on a seperate box from the CRM web server so that could be a factor.
What will it be trying to resolve?
Have this issues sometimes with a development server with crm on it and using an alias in the DNS to connect to it.
Sometimes. usually after or during a heavy load on that crm server, the name DNS name resolving simply takes too long...
And windows seems to cache (locally) even dns names it can not reach...
See here:
http://www.speedguide.net/read_articles.php?id=158
Have not tried to find the problem exactly, but an wrong configuration in DNS might be the problem...
For me the resolution for this one of the following:
1) ipconfig /flushdns
2) reboot server with crm on it(!)
3) waving the voodoo chicken 
|
| |
|