Unsolved
This post is more than 5 years old
2 Posts
0
86263
August 27th, 2010 03:00
Trying to update broadcom 5709C firmware "BMAPI Error"
I have been trying to update my boradcom 5709c firware, or more acurrately trying to install the Broadcom Network Device firmware, family version 5.2.7 from the drivers page for my PowerEdge T110 running Server 2008 R2 Enterprise x64. Once the package extract and starts running, I am getting an error that simply says "BMAPI Error", and the program bails out. I really need to update this firmware, and have been looking for manual steps and other ways to get it done and have come up short.
Has anyone seen this error before, or have any ideas on any ohter ways to get the firmware to update.
Thanks
Gayle Reid
No Events found!
fast_laptop
1 Message
0
September 3rd, 2010 14:00
I have the same problem with my M6500.
I did find a post online in an IBM forum that broadcom firmware package has trouble id'ing the hardware on win 7 64 bit.
I've found nothing else, still have issue.
rob
MatthewMcD
1 Message
0
March 4th, 2011 05:00
Same here, any word from Dell on a resolution? M6500 w/ Windows 7 64.
DNeffGES
1 Message
0
August 5th, 2011 10:00
I'll join the BMAPI ERROR club on this one. PowerEdge R300 with the same issue. No solution, many attempts, including trying it in safe mode.
Trying to update the firmware because OpenManage 6.5 kills my network card after each reboot. You can remove OM, or, set the DSM SA Data Manager service to disabled and it will stabilize the NIC but OM becomes usless.
ElectronicThing1
1 Message
0
November 23rd, 2011 12:00
Hi,
I just had this BMAPI error on some R515s. It appears that it may have been other RDP sessions that people had not properly logged off. Once I cleared these sessions, the update ran fine.
Thanks.
bvjens31
25 Posts
0
May 9th, 2012 09:00
Same exact issue with OMSA killing network!! Even after installing the latest OMSA 7.0.0. You would THINK that Dell would have this figured out by now. I have several clients with 2008 servers that are affected by this. As soon as server boots up, and while the DSM Data Manager service is in the "starting" state, the network never comes up. But, after the service does come up, so does network but with limited connectivity. I have to manually disable/enable the Network Connection in order to bring it back up. This problem makes remote management of servers an extreme pain and a deal-breaker for OMSA in my opinion!!!
I had read in a few places that upgrading NIC firmware would solve this issue, and in one case it has. However, last week when trying to upgrade the BCOM NIC firmware in a PE2900, I would get a BMAPI ERROR when trying to install it. I'm thinking that I may want to try some earlier firmware versions first. I don't think this particular NIC's firmware has been upgraded since it's been out of the box, probably 3-4 years ago.
The other server's NIC firmware upgraded OK, but when I open up OMSA I get a page cannot be displayed error. LOL. Needless to say, this particular client is not too thrilled with OMSA at this point.