Using Drobo Dashboard (with a Drobo S and Win XP), I encountered an error for the first time, when clicking the “Shutdown” command.
I recieved an error screen that said "DDService has encountered a problem and needs to close". got the following error and warning messages in the Win XP - System Event and Application Logs, as follows:
Event Type: Error
Event Source: Service Control Manager
Event ID: 7031
Description:
The Drobo Dashboard Service service terminated unexpectedly.
Event Type: Warning
Event Source: PlugPlayManager
Event ID: 257
Description:
Timed out sending notification of target device change to window of "TransportManager Device Monitor
Although, I got the above errors, Drobo S did shutdown properly, in response to the dashboard shutdown command.
Note: I have used the Dashboard many times before without ever getting the above error, until now. BTW, I rebooted and re-tested the dashboard shutdown command and it worked perfectly with no error messages at all.
Just can’t figure why this error had occurred.
…As anyone encountered this error ? If so, Why does it happen and how to resolve ?
Seems like a timing error to me. The two were having a conversation and one walked away before the other was finished talking, so the talker got pissed off.
I was just searching your Knowledge Base and it lists the message I got on the error screen that popped up om my windows desktop, namily DDService has encountered a problem and needs to close".
Contents of Knowledge Base Article:
Dashboard Error: “DDService has encountered a problem and needs to close”
Operating Systems:
Windows (All)
Problem Description:
Users may sometimes encounter this error: “DDService has encountered a problem and needs to close”
Resolution(s):
Please download and install the latest version of Drobo Dashboard
Jennifer,
So, it sounds like this is the same bug ? What do you think ?
… Could it be fixed in the latest version, where as I am running the older version of DashBoard Vers. 168 ?
FYI, … Just to let you know, I re-tested sevreal times, across days, and the problem does not occur anymore. So, I guess I will just have to chalk it up as a fluke, unless it re-occurs in the future.