
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-16-2010 08:41 AM
Windows 2008 R2 is found as Win 7
and I have a entry "Other". In the Other-list I have Win 2003 R2 and Win 7 entries.
- Labels:
-
Archive

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-16-2010 05:41 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-16-2010 05:36 PM
"Overload resolution failed because no Public 'UrlEncode' can be called with these arguments:
'Public Shared Function UrlEncode(bytes As Byte()) As String':
Argument matching parameter 'bytes' cannot convert from 'DBNull' to 'Byte()'.
'Public Shared Function UrlEncode(str As String) As String':
Argument matching parameter 'str' cannot convert from 'DBNull' to 'String'. "
Is there a way to reverse this?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-16-2010 05:34 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-16-2010 04:26 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-16-2010 04:22 PM
\\localhost:81
WMI output

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-16-2010 03:03 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-16-2010 02:14 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-16-2010 01:26 PM
Overload resolution failed because no Public 'UrlEncode' can be called with these arguments:
'Public Shared Function UrlEncode(bytes As Byte()) As String':
Argument matching parameter 'bytes' cannot convert from 'DBNull' to 'Byte()'.
'Public Shared Function UrlEncode(str As String) As String':
Argument matching parameter 'str' cannot convert from 'DBNull' to 'String'.
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.Reflection.AmbiguousMatchException: Overload resolution failed because no Public 'UrlEncode' can be called with these arguments:
'Public Shared Function UrlEncode(bytes As Byte()) As String':
Argument matching parameter 'bytes' cannot convert from 'DBNull' to 'Byte()'.
'Public Shared Function UrlEncode(str As String) As String':
Argument matching parameter 'str' cannot convert from 'DBNull' to 'String'.
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.
Stack Trace:
[AmbiguousMatchException: Overload resolution failed because no Public 'UrlEncode' can be called with these arguments:
'Public Shared Function UrlEncode(bytes As Byte()) As String':
Argument matching parameter 'bytes' cannot convert from 'DBNull' to 'Byte()'.
'Public Shared Function UrlEncode(str As String) As String':
Argument matching parameter 'str' cannot convert from 'DBNull' to 'String'.]
Microsoft.VisualBasic.CompilerServices.OverloadResolution.ResolveOverloadedCall(String MethodName, List`1 Candidates, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, BindingFlags LookupFlags, Boolean ReportErrors, ResolutionFailure& Failure) +469
Microsoft.VisualBasic.CompilerServices.OverloadResolution.ResolveOverloadedCall(String MethodName, MemberInfo[] Members, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, BindingFlags LookupFlags, Boolean ReportErrors, ResolutionFailure& Failure) +99
Microsoft.VisualBasic.CompilerServices.NewLateBinding.ResolveCall(Container BaseReference, String MethodName, MemberInfo[] Members, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, BindingFlags LookupFlags, Boolean ReportErrors, ResolutionFailure& Failure) +142
Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateGet(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack) +594
ASP.compstats_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer) +790
System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +256
System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +19
System.Web.UI.Page.Render(HtmlTextWriter writer) +29
System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +27
System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +99
System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +25
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1266
--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.3053; ASP.NET Version:2.0.50727.3053

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-16-2010 12:56 PM
I mean that our current 3.5.2 version of Lansweeper is able to get memory information from that server.
The server details has got the memory showing. So if it works on the server with the 3.5.2 do you still want me to test the WMI call?
I'll get the web.conf details soon

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-16-2010 12:22 PM
Memory issue:
The current release of lansweeper does get the correct memory information from the server so the WMI call does work. Do you still want me to test the WMI call?
OS display:
After running the SQL code I get the following error on the front page
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<!-- Web.Config Configuration File -->
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>
