Zimbra Server Version: X-Mailer: Zimbra 6.0.3_GA_1915.UBUNTU8 (ZimbraWebClient - SAF3 (Linux)/6.0.3_GA_1915.UBUNTU8)
Clients: Outlook 2003 SP3, Windows XP Pro (fully patched).
Zimbra Outlook Connector Version: ZimbraOlkConnector-6.0.3_GA_1912_6.0.5737.3
On a fresh Outlook 2003 SP3 (and also with no prior profile), I install the Zimbra Outlook Connector version indicated above. The installation appears to run through normally. Once the install is complete, I am instructed by the installer to startup Outlook. I startup Outlook and immediately get the error as indicated in the attachment. The error is associated with LSLIB32.DLL (see attachment image).
I close that message, startup Outlook again, get asked to start in Safe Mode and I click No and then I continue into Outlook. Once in Outlook, the Zimbra connector seems to work ok as far as sending and receiving email, etc.
***So far I have installed the connector on the first 12 machines in our Windows 2003 network (XP clients) and ALL get this error message. In fact, even in my test VM environments (again XP), I get this error message. What is particularly interesting is the clients have Admin rights when I do the installs of the connector and this error happens for users on the network and also for test systems that are both on and off the network.***
Even though most things are working well, I am very concerned that everything could stop working in the future. I do not know how serious the LSLIB32.DLL file failure on installation is to Outlook and/or Zimbra. Can somebody explain that to me? Is my whole implementation going to fail and come crashing down in the near future because of this issue?
"Outlook.pst cannot be accessed - 0x80040116" error usually gets resolved using Inbox Repair tool (Scanpst.exe). Running only Inbox Repair tool doesn't fix Outlook problem though it shows that no errors were found. Reason being index of the .PST file is damaged. For resolving this issue, firstly run the "2 GB Truncation" tool, then run the Inbox Repair tool, and then open the repaired PST file.
Running 2 GB Truncation tool
"2 GB Truncation" tool known as Pst2gb.exe can be downloaded from the Microsoft Download Center. After download, you can see the other files with its exe, which are Msstdfmt.dll, Msvbvm60.dll, Pst2gb.exe, Readme.rtf, and Readme.txt.
(http://www.microsoft.com/downloads/details.aspx?familyid=B33B1DFF-6F50-411D-BBDF-82019DDA602E&displaylang=en)
Now follow the given steps:
1.Click Start, and then click Search.
2.Under What do you want to search for? click All files and folders.
3.In the All or part of the file name box, type *.pst.
4.In the Look in list, click Local Hard Drives (C:), and then click Search.
5.Note the path to the .pst file that you want to repair. By default, this file is named Outlook.pst.
6.Click Start, click Run, type pathpst2gb.exe -s, and then click OK.
7.Click Continue, and then click Browse.
8.Click the .pst file that you want to repair, and then click Open. By default, this file is named Outlook.pst.
9.Click Create, type a new unique file name for the .pst file such as Outlook-2 in the File name box, and then click Save.
10.In the Oversized PST Recovery Tool dialog box, click Start.
11.After you run the tool, click OK, and then click Close.
Running Inbox Repair tool to fix Outlook PST
1.Double-click scanpst.exe file.
2.Click Browse, and then open the folder that contains the new .PST file that you created by using the "2 GB Truncation" tool.
3.Click the new .PST file that you created and then Open.
4.In the Inbox Repair Tool dialog box, click Start.
5.When the file has been scanned, click Repair to repair the errors in the file.
6.When you receive the "Repair complete" message, click OK.
7.Restart the computer.
Now open the new created .PST file with Outlook. During the whole process there are chances of Outlook email data getting corrupt. But you can now fix Outlook PST easily with Outlook recovery software. This software recovers and restores emails and other email stuff from damaged Outlook PST files.
Error 0×80040154 isn’t as obscure or as difficult to repair as its name might suggest. Usually, this error signifies one of two problems.
Error 0×80040154
Sometimes, this just represents a problem that your computer may have connecting to Microsoft Outlook Express. In such a case, it will probably show up as a send and receive error.
One of the most frustrating things about error 0×80040154 in relation to Outlook is its lack of documentation by Microsoft. Its information about this error pertains almost entirely to other applications.
Fortunately, for you and other users with this same problem, it is relatively easy to fix. Running a “Detect and Repair” on Outlook will often fix the problem. If it doesn’t, go ahead and reinstall Microsoft Outlook. This will take care of the situation nine times out of ten.
The “0×80040154 (Class Not Registered)” Error
This can happen when you install an ATL server for use with Visual Studio. It could be that this error pops up after an update for Visual Studio.
If you use Visual Studio 6.0, make sure your computer uses the runtime ATL.dll for this process, instead of the later-edition Visual Studio .NET version.
If you’re not sure how to do this, it’s best to find a tool that can help. If you attempt to change this on your own and switch the wrong files, you may permanently damage your Visual Studio and/or your Windows operating system.
Repair 0×80040154 and the Other Problems it May Have Caused
One problem with this and any other computer error is that without the right kind of computer maintenance, the error’s repercussions may affect your windows operating system long after you have fixed the problem.
It is very possible this error has altered the Windows registry–and not for the better. Since the registry makes note of all your files’ and programs’ interrelationships and uses them for future reference, an error today can keep Microsoft Windows in error for many months to come. Repair Error 0×80040154 with a free registry scan.
Re-Tweet This Post RSS
Source:http://ezinearticles.com/?Fix-Stop-Error-0x00000024-With-a-Registry-Cleaner&id=2884563
No comments:
Post a Comment