Unsolved
This post is more than 5 years old
4 Posts
0
2161
June 6th, 2017 07:00
OME - Application Launch not working?
Hello Dell community.
I installed OME 2.2.0.2056 on a Windows 10 Pro machine (latest updates). OME discovers my DELL MD Storage in the network just fine. Now I want to get mails, when HDD errors on the storage occur. I tried to install IDRAC, but that doesn't run on Windows 10 Pro.
So I created a batch script under C:\OME\ which opens a .ps1 script. With this, PowerShell sends a generic mail to me, stating that something is wrong with the storage.
sendmail.bat --> sendmail.ps1
I then went to Manage -> Alerts -> Application Launch in the OME web interface and created an entry for sendmail.bat.
When I click on "Test Action...", for several seconds nothing happens and then the systems says the test failed. However, when I test the scripts manually, without OME, just out of the Windows file system, everything works fine.
What do I have to do, that OME can call this script properly?
DELL-Arun Mo
116 Posts
0
June 6th, 2017 22:00
Hi,
Thanks for your query.
OME itself has email alert action. If you configure your SMTP server, you should be able to send the email based on the incoming trap. There is no need to create a batch file for that reason.
To answer your question, try using "cmd.exe /C sendmail.bat"
Let us know if it helps.
lokozar
4 Posts
0
June 7th, 2017 02:00
Thank you for the quick reply.
Yes, I saw that OME has an Email section right beneath "Application Launch". That was the first thing I tested, alas to no avail. Clicking on "Test Action..." also resulted in a message stating the test could not be completed. I know for certain that I provided the right credentials.
I read up on the internet and somewhere there was the hint that this is only an additional graphical overlay which needs IDRAC to run in the background. Since I cannot install IDRAC on Windows 10 Pro, I quickly canned this option.
Back to the scripts. I did as you asked.
After I clicked on "Test Action..." it's the same as before. Button goes grey for several minutes and then the system reports the test couldn't be completed. It seems OME is unable to execute the batch file.
Here is the message:
lokozar
4 Posts
0
June 9th, 2017 03:00
Sorry for the double post, but I have taken a look into the Windows Event Viewer. The section Dell OpenManage shows errors like this:
Unable to send TestAction "cmd.exe /C sendmail.bat": Dell.ManagementEssentials.Exceptions.ItaDataAccessorException: Message ID "TestAction" too long to be processed by the DA Service. ---> System.TimeoutException: Unable to confirm that the memory message was sent before the timeout expired.
at A.c8830eb6471e20c17408e4edc56dbee61.c53375e2a24b6e8ee6fc903b09597527f(String ceb48334b78e0e764e3e7892f6114d323, Nullable`1 c8cd7d5a7cd9e9d83621f88c9fd6d0074, Mutex c4d2dacddde69f04884e9002bffc31beb, Boolean cc4979a75f8b842360aa6e162c8a4c029)
at A.c8830eb6471e20c17408e4edc56dbee61.c53375e2a24b6e8ee6fc903b09597527f(String ceb48334b78e0e764e3e7892f6114d323, Nullable`1 c8cd7d5a7cd9e9d83621f88c9fd6d0074)
at A.c9e327a3ca308300e52f0cba9f5fa8ec4.ca1f65ba4cfd871d549320016a2de19ba(String c0140dff06d5e3a38c275a5a862226722, c41a5570612cc8f74915e5f9b6d5b003f c85929ce61371a8e5457e41219eb87be5, TimeSpan c2a3639b8236ceae1f06072c208d9a307)
--- End of inner exception stack trace ---
at A.c9e327a3ca308300e52f0cba9f5fa8ec4.ca1f65ba4cfd871d549320016a2de19ba(String c0140dff06d5e3a38c275a5a862226722, c41a5570612cc8f74915e5f9b6d5b003f c85929ce61371a8e5457e41219eb87be5, TimeSpan c2a3639b8236ceae1f06072c208d9a307)
at A.c9e327a3ca308300e52f0cba9f5fa8ec4.ca1f65ba4cfd871d549320016a2de19ba(c576ef8bc46e19392bed2822c9ca966a3 c0140dff06d5e3a38c275a5a862226722, TimeSpan c2a3639b8236ceae1f06072c208d9a307)
at A.c576ef8bc46e19392bed2822c9ca966a3.ce10aa38053a7d43544c579bdd5554b6a()
at Dell.ManagementEssentials.Services.AlertService.TestAction(EventStoredActionObj eventAction)
at SmartConsole.Service.DataService.TestAction(String cmd, String cmdArgs, Int32 actionType)
lokozar
4 Posts
0
June 16th, 2017 05:00
Besides my script I also activated the build in mail function. Still no luck with testing the settings though. I am guessing there is no fix?