Dell Control Point Connection Manager Service Error
Hi,
I have an issue with Dell control point connection manager application.
I am getting an error connected to Dell Control Point Connection Manager Service.
"Currently Unable to communicate with Dell Control Point Connection Manager Service. This application will now exit. Please contact your IT department or Dell customer service for further assistance"
I am running the service as an administrtor, so it should not be an permission issue. I have tried to check in eventvwr but was getting below message:
The description for Event ID ( 0 ) in Source ( SMManager ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: SMManager info: 6, SetServiceStatus.
It would be great if some one could help me on this.
Thanks,
Swasu
I have an issue with Dell control point connection manager application.
I am getting an error connected to Dell Control Point Connection Manager Service.
"Currently Unable to communicate with Dell Control Point Connection Manager Service. This application will now exit. Please contact your IT department or Dell customer service for further assistance"
I am running the service as an administrtor, so it should not be an permission issue. I have tried to check in eventvwr but was getting below message:
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
mekaywe
14 years ago
Posted by:
swasu
14 years ago
Hi Mekaywe,
The scneario is different here. The issue you are pointing got resolved once the description to the service is added, but this service has the description present in it but is still throwing the error and even the eventvwr messages are not helpful.
The case is random here, I am not getting the error for the first time and when I log off my machine and log in I am getting the error. Once I say "OK" to the error and relaunch the application I am not getting the error.
This is happening even with the source.
The scneario is different here. The issue you are pointing got resolved once the description to the service is added, but this service has the description present in it but is still throwing the error and even the eventvwr messages are not helpful.
The case is random here, I am not getting the error for the first time and when I log off my machine and log in I am getting the error. Once I say "OK" to the error and relaunch the application I am not getting the error.
This is happening even with the source.
Posted by:
anonymous_9363
14 years ago
Posted by:
pjgeutjens
14 years ago
Posted by:
joseph
14 years ago
Posted by:
swasu
14 years ago
Hi Joseph,
Even I am not clear about /AUXSOURCE=flag..
As per my understanding if a saved eventlog is opened from a different machine, some registries or components may not be available to display the message clearly. In those scenario if we used the option /AUXSOURCE=flag we could get a clear message.
I am not sure if my understanding is correct or not. It would be gr8 if someone who has better knowledge on this explains..
Coming to my scenario, I am checking the message in the same machine where i have instlled my application, but still I am unable to view the message clearly [&:]
Even I am not clear about /AUXSOURCE=flag..
As per my understanding if a saved eventlog is opened from a different machine, some registries or components may not be available to display the message clearly. In those scenario if we used the option /AUXSOURCE=flag we could get a clear message.
I am not sure if my understanding is correct or not. It would be gr8 if someone who has better knowledge on this explains..
Coming to my scenario, I am checking the message in the same machine where i have instlled my application, but still I am unable to view the message clearly [&:]
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.