Highlighted
Wapinoux
1 Nickel

Unhandle Error in the application

Since we discovered manu host (more that 1300), we get the error below very otfen:
A popup appear the errors details:

[HttpWebRequest_WebException_RemoteServer]

Arguments: NotFound

Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=4.0.60531.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer

 

System.ServiceModel.CommunicationException: [HttpWebRequest_WebException_RemoteServer]

This error can appear in all menu at different time...

0 Kudos
9 Replies

Re: Unhandle Error in the application

Thanks for the post.  We've cleaned up some of this since the OpenEval posted.

But let me get a bit of info from you anyway:

1. How much memory on the OME server?

2. OME installed on Physical or VM?

3. How many cores assigned to the OME server?

4. What protocol are you using in discovery?

5. How often are you running discovery?

6. How often are you running statusing?

Also, you may consider dragging the slider back some on the disc/status config settings.

Thanks,

Rob

DELL-Rob C
Social Media Support
#IWork4Dell

0 Kudos
Wapinoux
1 Nickel

Re: Unhandle Error in the application

1. How much memory on the OME server?

=> 6Go

2. OME installed on Physical or VM?

=> Virtual Machine

3. How many cores assigned to the OME server?

=> 4

4. What protocol are you using in discovery?

=> SNMP, WMI and WSMAN

5. How often are you running discovery?

=> Default configuration

6. How often are you running statusing?

=> Default configuration

0 Kudos

Re: Unhandle Error in the application

Right, so we've made some changes in the next release (coming very soon) that should address much of these types of errors.  Although with <1300 devices, you are approaching a larger config setup that would likely benefit from an 8 core / 8 GB resource allocation.

Thanks,

Rob

DELL-Rob C
Social Media Support
#IWork4Dell

0 Kudos

Re: Unhandle Error in the application

Edit: should have said "greater" > 1300 in my previous post 🙂

DELL-Rob C
Social Media Support
#IWork4Dell

0 Kudos
Wapinoux
1 Nickel

Re: Unhandle Error in the application

1397 and we don't have discover all devices...

Theses errors come from performances problems ?

When i check the usage, 2GB are available and cpu is at 10/15%

For the production server, we have installed a news physical server with this configuration:

16GB Ram

2 CPU 4Cores (with Hyperthreading => 16 cores) 2,27GHz

Do you think it will be enought ?

I think we must have 3000 devices to discover

Thanks

0 Kudos

Re: Unhandle Error in the application

The proposed configuration looks good and you should have enough resources to run OME for your servers. As Rob mentioned the upcoming release for OME should address this error.

Regards

Abhijit

0 Kudos
Wapinoux
1 Nickel

Re: Unhandle Error in the application

Ok, do i have to wait the next release before go in production ?

Do you know when it's coming ? Weeks ? Months ?

We are waiting since a long time a product like this, so...

Thanks

0 Kudos
cgillehe
1 Nickel

Re: Unhandle Error in the application

I'm actually getting the same error message, however I have lost the abiliy to connect to the OME instance completely.

We are currently testing OME prior to deployment, and so far we have been unable to find a workaround to this problem, even uninstalling and reinstalling the OME program has failed to resolve the issue.

0 Kudos

Re: Unhandle Error in the application

New OME release 1.0.1 is releasing today 2/28. Look for the forum announcement later in the day. New release should have the fix for this issue. Let us know after you try it out.

0 Kudos