Blackberry Enterprise Server 5.0 fails to properly load all services at reboot.
Some of the Blackberry Enterprise Services for BES 5.0 repeatedly fail to start after our weekly scheduled reboot. Here is a simple batch script to properly shutdown all of the services and reload them in the proper order.
REM Stop BES services in proper order
net stop "BlackBerry MailStore Service"
net stop "BlackBerry MDS Connection Service"
net stop "BlackBerry Dispatcher"
net stop "BlackBerry Attachment Service"
net stop "BlackBerry Controller"
net stop "BlackBerry Router"
net stop "BlackBerry Policy Service"
net stop "BlackBerry Synchronization Service"
net stop "BlackBerry Alert"
REM Restart Services
net start "BlackBerry Router"
net start "BlackBerry Attachment Service"
net start "BlackBerry Dispatcher"
net start "BlackBerry MDS Connection Service"
net start "BlackBerry Alert"
net start "BlackBerry Controller"
After creating the above batch script you can either run it manually as necessary or set it as a scheduled task to run after any periodically scheduled reboots. Also on a side note if you choose to restart the services by hand then be sure and follow the order above.
References: Correct order to start and stop BlackBerry services
Popularity: 10% [?]
We run a fairly large network of DSL connections. In the past, when we move a store from one place to another we would put a new phone line in the new location and run DSL on it. When the store finished the move, we would make this new phone number part of the “hunt” group (rollover line) for their primary phone number. Doing this allowed us to eventually drop the old rollover line at the old location and complete the move without really adding any cost for phone lines.
To make a long story short, I was just told that we can no longer do this. At our most recently moved location, we now have a line that is being used for nothing but DSL. What a waste! This line has a wall mounted DSL filter installed on it to keep the DSL and dial tone separate, but we cannot make use of the dial tone now…although we are paying for it. It may sound petty, but the extra monthly charges could really add up over hundreds of locations.
When I asked our AT&T rep what the reasoning behind this was, I got this REALLY informative response (and I quote):
I do not have a good answer for you, but there are rules for DSL that have to be followed.
With our next two store moves on the horizon, I’m going to push for a little more information in hopes I can continue doing things the cheaper, more efficient way. To me, this whole fiasco smells pretty fishy. I think it may be another way for AT&T to further pad their pockets. I will post a follow-up to this as soon as I get past “Bob” in AT&T support and dig my way to the bottom of the mess.
Signed,
Ben Tover
Popularity: 4% [?]
We have all been there. It’s the day after Microsoft has pushed out a ton of patches and your system keeps interrupting you with this simple, solitary, and frustrating message.
We have two choices:
- Restart Now – Yeah, you could get it over with and stop everything that you are
doing, save everything, and reboot (really who wants to do that).
- Restart Later – Sounds good, oh wait later only means 10 minutes later. The
Automatic Updates window will popup every 10 minutes, take focus away from the application
you are using, and generally bug the hell out of you until you finally restart.
So there we are with two choices, two horrible choices…. There has to be a better way.
Luckily there is.
Stop WUAUSERV the Automatic Update Service
Since the popup is part of the WUAUSERV system used to update your computer if you stop
this service the popup itself will stop as well. Below I will walk you through
stopping this service by using both the Graphical User Interface (GUI) and Command Line
Interface (CLI).
GUI:
- Go to the Services snapin by typing “services.msc” at the run prompt or by navigating to
Control Panel > Administrative Tools > Services.
- Find the service labeled Automatic Updates, right click it, and choose Stop.
CLI:
- Enter the following command in either the run dialog box or a command prompt: net stop wuauserv
- If wuauserv is a little hard to remember this command will produce the same results: net stop “automatic updates”
Once the service has been stopped the popup will go away and not return, which will allow you to restart at your own convenience.
Popularity: unranked [?]
As I sat at my desk a few days ago, I noticed that the annoying hum of server fans had taken on a brand new sound. Instead of the low humming noise I am used to, the sound was more of a high-pitched scream. Those of you in the IT field know this is NOT a good thing!
I gathered the nerve to approach the server room door. After hearing the door screech open, I was greeted with 80 degree air and an even louder noise. Sure enough, we had another cooling problem! After a couple of phone calls, I had a heat & air technician en-route. The technician wasted no time telling me that the problem was due to our landscaping crew using a blower in the area. It seems the blowers kick up a ton of debris, which gets sucked into the air conditioning units, rendering them useless.
The part of this that surprised me is that we have redundant cooling in our server room. A few years back, we had similar issues, and we went without air conditioning in our server room for weeks on end. Vowing to never let this happen again, we worked with the local heat & air company to design a redundant system with multiple compressors and air handlers. The thought process behind this was that if one unit were to go out, the other unit could still maintain the correct temperature while allowing us to get the broken unit serviced. We had tested this, and it worked!!!
But not this time. It seems our company has grown so much over the past few years that we have had to add numerous new servers, switches, and etc. No one ever took into account the extra heat being generated by these units. Now, if one air conditioning unit goes out, the room temperature slowly climbs and climbs and climbs. In a nutshell, having a cool server room now REQUIRES that both A/C units be functioning properly. Another fine mess we’ve gotten ourselves into.
I can’t wait to talk to the purseholders of the company and tell them about our little underestimation. I can only imagine the numbers that will be thrown our way when we get quotes on larger A/C units.
A word to the wise: cooling is an often overlooked, yet critical area in the IT field. Small changes in the makeup of your server room over a period of time can add up to big problems down the road. It’s best to build a little extra capacity in on the front end of an installation, but you also have to factor in anticipated growth rates. With a little extra planning and attention to detail, you can rest assured that your servers won’t endure the additional wear and tear of extreme temperatures. As an added benefit, you won’t have to go back to the big dogs asking for more money.
Wish me luck!!!
Popularity: 4% [?]
February 9, 2010
|
|
Misc
This is the very first post at BrainBlurb.com. We are still in the process of getting everything sorted out.
Please stop back by and check us out.
Popularity: 4% [?]
