Let it be known that BES or BPS version 4.1 REQUIRES a certain version of Java. That version is: Java 2, SE v1.5.0_11. You can download it here.
Without this version of Java, you will have many different problems. The problem I was having was with the Blackberry MDS Connection Service not starting. I got the following error: The BlackBerry MDS Connection Service service terminated with the following error:
The system could not find the environment option that was entered.
Today i had an issue where a workstation running XP Home edition would BSOD when you logged in. The BSOD occured sometime while loading the tray icons - normally. After a lot of troubleshooting (which basically just involved disabling services via msconfig until the problem went away) I figured out that the Plug and Play service was the culprit.
I checked the dependencies tab on the services properties to see what services depended on the Plug and Play service to start. I then disabled all the services that were dependant upon the Plug and Play service and I enabled the Plug and Play service. After a reboot, everything seemed to work fine.
I then started enabling the services which were dependant upon the Plug and Play service. It turns out the Windows Audio service was the culprit. I’m guessing that either a sfc /scannow or a remove and reinstall of the sound card drivers would have resolved the problem, but I didn’t get a chance to try because the client said, “Oh well, we don’t want sound on that computer anyway.” He asked me to leave it as is, so that was that.
Hope this saves someone else some time!
Luke
So while trying to install a printer this week, I was getting this error message on SBS 2003: “Unable to install printer. Operation could not complete.”
The printer was an HP OfficeJet 8000 (not my idea). I stay away from HP printers due to their total incompetence to make good drivers for their lower end printers. I’ve spent to much time fixing their problems.
I had all the latest print drivers, and I was installing it using a TCP/IP port (network printer).
I tried several times… Deleted drivers, etc each time. The fix? Restart the print spooler and try again. Go to services.msc, find the print spooler, and right click and hit “restart.” Did the trick for me!
Ok, I’m still on my kick of eliminating ANY errors from my SBS 2008 server. Here’s another one, and it’s fix:
Log: Application
Type: Warning
Event: 2442
Agent Time: 11:30:18 pm 8-Apr-09
Event Time: 3:30:18 am 9-Apr-09 UTC
Source: Windows SharePoint Services 3 Search
Category: Gatherer
Username: N/A
Computer: ICS-S01.ics.local
Description: The index was paused.
Context: Application 'Search', Catalog 'index file on the search server Search'
The fix: Read on at
http://msmvps.com/blogs/cgross/archive/2009/03/29/sharepoint-search-amp-event-id-2436-errors-in-sbs-2008.aspx
Ok, so I’m getting this error in my event logs now (on my SBS 2008 Server):
Log: Application
Type: Warning
Event: 2003
Agent Time: 3:17:42 am 6-Apr-09
Event Time: 7:17:42 am 6-Apr-09 UTC
Source: Microsoft-Windows-Perflib
Category: None
Username: N/A
Computer: ICS-S01.ics.local
Description: The configuration information of the performance library “C:\Windows\system32\sqlctr90.dll” for the “MSSQL$ICSAPPS” service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted.
The fix? Following the solution as suggested in this KB: http://support.microsoft.com/kb/928384
This should be run from an elevated command prompt (right click on command prompt and click “Run as administrator”).
Here is what mine looked like:
C:\Windows\system32>unlodctr MSSQL$ICSAPPS
Removing counter names and explain text for MSSQL$ICSAPPS
Updating text for language 009
C:\Windows\system32>lodctr “C:\Program Files (x86)\Microsoft SQL Server\MSSQL.2\MSSQL\Binn\perf-ICSAPPSsqlctr.ini”
I was getting this error message on my SBS 2008 Server:
Log: Security
Type: Failure Audit
Event: 4625
Agent Time: 11:26:36 am 4-Apr-09
Event Time: 3:26:36 pm 4-Apr-09 UTC
Source: Microsoft Windows security auditing.
Category: Logon
Username: N/A
Computer: ICS-S01.ics.local
Description: An account failed to log on.
Subject:
Security ID: S-1-5-18
Account Name: ICS-S01$
Account Domain: ICS
Logon ID: 0x3e7
Logon Type: 3
Account For Which Logon Failed:
Security ID: S-1-0-0
Account Name: ICS-S01$
Account Domain:
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc0000064
Process Information:
Caller Process ID: 0xc88
Caller Process Name: C:\Program Files\Microsoft\Exchange Server\Bin\Microsoft.Exchange.Search.ExSearch.exe
Network Information:
Workstation Name: ICS-S01
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
The fix? Install Exchange Update Rollup 7 for Exchange 2007 (http://www.microsoft.com/downloads/details.aspx?familyid=086A2A13-A1DE-4B1D-BD12-B148BFD2DAFA&displaylang=en)
You will probably have to download this and run it from an elevated command prompt - otherwise you will get errors.