UNSOLVED

Maurotb76

updated

11 years ago

M

Maurotb76

4 Posts

0

95844

November 6th, 2014 13:00

OME2 Cannot delete discovery range

Hi,

in my ome 2, i can add range, but i can't delete discovery range.

if i delete from web gui,all seem work, bur discovery range remain,

if i delete from powershell, i have a tiimeout.

This issue is for all discovery range, no task are active.

Can you help me?

Thanks

PS C:\Program Files\Dell\SysMgt\Essentials\Tools\CLI> Remove-DiscoveryRange -ran
ge test
Remove-DiscoveryRange -range test
Range is test
Remove-DiscoveryRange : The request channel timed out while waiting for a
reply after 00:01:30. Increase the timeout value passed to the call to Request
or increase the SendTimeout value on the Binding. The time allotted to this
operation may have been a portion of a longer timeout.
At line:1 char:1
+ Remove-DiscoveryRange -range test
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Remove-DiscoveryRange], Timeo
   utException
    + FullyQualifiedErrorId : System.TimeoutException,Dell.OME.CLI.CLI_RemoveD
   iscovery

  • DELL-Rob C

    4 Apprentice

    •

    2843 Posts

    1113

    0

    Posted November 6th, 2014 14:00

    Hi and thanks for the post.

    Can you confirm the OME version and build number in the About Box?

    Thanks,

    Rob

    delltechcenter.com/ome

  • Maurotb76

    4 Posts

    1113

    0

    Posted November 7th, 2014 02:00

    OME 2.0.0.1926

  • DELL-Pupul M

    2 Intern

    •

    1004 Posts

    1113

    0

    Posted November 10th, 2014 02:00

    Hi,

    Can you try restarting the DA service (DSM Essentials DA service) from services.msc and then check again?

  • Maurotb76

    4 Posts

    1113

    0

    Posted November 10th, 2014 02:00

    Same problem after restart service...

    I rebooted the server also, same problem

  • DELL-Rob C

    4 Apprentice

    •

    2843 Posts

    1113

    0

    Posted November 10th, 2014 07:00

    I think it is the DiscoveryConfiguration table...

  • DELL-Rob C

    4 Apprentice

    •

    2843 Posts

    1113

    0

    Posted November 10th, 2014 07:00

    Hmm, ok, thanks for the update.  We'd seen this in an earlier release, but I was thinking it was fixed in 2.0, so surprised to see this.  Is this a fresh 2.0 install or upgrade from 1.3?

    For 1.3, folks would use SQL Server manager to delete the range from the database, but they had to disable triggers first.  You might open a ticket so we can get a closer look at this issue on your system (800-945-3355).

    Thanks,

    Rob

    delltechcenter.com/ome

  • Maurotb76

    4 Posts

    1113

    0

    Posted November 10th, 2014 07:00

    It's a fresh install,

    until a few months ago it worked, but now I have this problem and I have not done any modification...

    In which table I need to delete the record?

    Thanks

  • kelemvor33

    2 Intern

    •

    374 Posts

    1113

    0

    Posted November 26th, 2014 06:00

    I have this exact same problem.  I installed OME 2 and told it to use a local SQL instance on my PC.  Where do I go to find whatever I'd need to delete?  Any help would be great.

  • DELL-Pupul M

    2 Intern

    •

    1004 Posts

    1113

    0

    Posted November 27th, 2014 22:00

    The table name is dbo.DiscoveryConfiguration table. You can find it under the OpenManageEssentials database but like Rob mentioned you will have to disable the triggers first. It will be better to open a support ticket.

    Though you can try to stop all the OME services, then delete the data from this table. Don't forget to take a back up of the OpenManageEssentials database before you try this,.

  • DELL-Rob C

    4 Apprentice

    •

    2843 Posts

    530

    0

    Posted December 1st, 2014 11:00

    We'd love to have support get a copy of the database if anyone wants to open a ticket.

    But if you workaround it by deleting it from the database directly, as Pupul mentions...be sure to shut down OME and stop the 3 OME services in services.msc.

    Thx

    Rob