If you getting the below error when trying open an excel from a sharepoint library, the the issue might be because you don have the Sharepoint OpenDocument class as you add-on. These can be caused by either you are using 64bit version of the IE or the add-on is not there.
Solution – just use 32bit version of IE or repair your outlook. If your share point is running on version 2010, it is better to install a Microsoft Office 2010 for better experience. 😉
The document could not be opened for editing. A Microsoft SharePoint Foundation compatible application could not be found to edit the document
Just want to share with you some problem I faced with running DHCP on a RODC.
When you install a DHPC role on a server, it will create a local group name “DHCP Administrators” and also “DHCP Users”.
RODC is a new & exciting features on Windows Server 2008. (http://technet.microsoft.com/en-us/library/cc753223(WS.10).aspx) Now, we don’t have to bother what the local admin are doing in our server at the site. 🙂
Now, I have a problem when installing a DHCP on RODC. As mentioned earlier, when you installed a DHCP on a server, it will create a local DHCP group(DHCP Administrators & DHCP Users). Since, RODC is pretty much a DC, there is no local group on the server and since it’s also a READ-ONLY DC, it cannot create the account itself.
You will notice that when your DHCP service is stopped when you install it on RODC and when you check the event log, you’ll notice error 1035 and 1036. This error shows, there exist a authentication problem.
So what shall we do in order to resolve this?
Easy! Just create the DHCP groups in DC 😉
Here’s the step
- Login to any RWDC
- Open Active Directory User & Computers (ADUC)
- Under the Users OU > Create group name “DHCP Administartors” & “DHCP Users” with the group scope is set to “Domain Local”
- Let the replication kicks in
- Voila! Your DHCP service is now automatically started 😉
When MS DTC fails to start and you get an error like:
“The Distributed Transaction Coordinator service terminated with service-specific error 3221229584 (0xC0001010).”
You know you are in trouble. Fortunately there is a simple solution.
You can find the actual error from Event Viewer:
“MS DTC log file not found. After ensuring that all Resource Managers coordinated by MS DTC have no indoubt transactions, please run msdtc -resetlog to create the log file.”
That is pretty much what you do. After restarting the machine type in cmd / command prompt:
Now start the service again and it will start without a problem.
I’ve been using Microsoft Exchange 2003 and playing with it for almost 4 years and during these 4 years, I have encounter many kind of issues involving this product. And the father of all this “issues” is exchange database “Dirty Shutdown”. This is by far the worst and most common issues that I’ve heard or experience.
So what is exchange “Dirty Shutdown”?
As the name suggest, “Dirty Shutdown” is when the MS Exchange shutdown dirtily, whatever that means. All jokes aside, it’s actually really bad even disastrous. A “Dirty Shutdown” happens whenever the Information Stores have not been closed in a properly manner. This might be due to power outage or power surges or any other action that might caused the server to be inproperly shutdown.
Most people usually think of dirty shutdown as the indication of damaged database. But that’s not the case at all. It’s just that Exchange database has not been shut normally and therefore it becomes our area of concern as it leads to corruptions in Exchange database .EDB and .STM files.
A Dirty Shutdown state does not indicate the database is corrupted or damaged. A Dirty Shutdown state indicates only that the database files were not detached from the log stream correctly. Therefore, before you can start the database again, you must first recover the database files.
The next time that the database is mounted, this recovery is run automatically. If automatic recovery fails, you can use the Microsoft Exchange Server Disaster Recovery Analyzer Tool to analyze the reasons for failure. After analysis, the Exchange Server Disaster Recovery Analyzer will provide recommendations for manually recovering the database files.
So how to check for Dirty Shutdown?
Login to you Exchange Server that you want to run the check and follow these steps.
- Click Start, and then click Run.
- In the Open box, type CMD, and then click OK.
- Switch to the C:\Program Files\ExchSrvr\Bin folder, type one of the following commands (as appropriate to your situation), and then press ENTER:
- type in eseutil /mh <My_Database_Name.edb>
eseutil /mh "c:\program files\exchsrvr\mdbdata\priv1.edb"
Find State: when you have “Dirty Shutdown” it will say “State:Dirty Shutdown”.
It’s the event that I have been this year. The biggest and coolest product ever. MS Exchange 2010 and Windows 7. wooohhooooo!!! I’m going to collect all the tshirts and freebies. hehe
Join your peers at the largest Microsoft product launch of the year!
Celebrate the launch of Windows® 7, Windows Server® 2008 R2 and Microsoft®Exchange Server 2010 on 24 November 2009 and discover how these new tools can help you meet the challenges of efficiency head-on.
You’ll also get to meet Microsoft experts and partners, network with your peers and get some hands-on time with our new range of products that offer the following benefits:
• Get more from existing systems with interoperable solutions that work together.
• Simplify IT infrastructure management to lower costs and manage compliance demands.
• Build on existing skills, with new innovations based on familiar Microsoft processes and interfaces.
• Connect people to information using products with advanced features.
Time is running out so REGISTER NOW. We’ve got netbooks to give away to the lucky 3,777th, 4,777th & 5,777th registrant*!
More great reasons to attend this event:
||Four exciting afternoon tracks including Windows 7, Windows Server 2008 R2, Unified Communications, Developer Tools
||FREE Hands-On Labs!
||Limited edition Windows 7 t-shirts* for every 77th registrant
||Evaluation copies of Windows 7, limited evaluation copies of Windows Server 2008 R2 and Microsoft Exchange Server 2010 (Release Candidate) will be handed out on a first come, first serve basis
||Exchange 2010 t-shirts for lucky track session participants
||Participate in our onsite contests and stand a chance to win more netbooks & other great prizes
*Winners of the netbooks & t-shirts will be contacted individually through email and will need to be present at The New Efficiency Launch to collect their prizes.
Who should come
IT Professionals, Developers and Technology Decision Makers.
Click here for registration
As a good system admin, I start my day by doing all the routine checks on all of my server and being a system admin in a Windows/Microsoft environment, it is natural to use the admin tools that were available out of the box.
As usual, I’ll open all the admin tools to start my daily checkups and to my surprise, I was prompted “Access is denied for dsa.msc”. I tried to open other admins tools and as expected, I get the same message. I’ve checked my system drive permission and my access level and it seems ok for me. So back to basic, I googled and found a solution to the problem from some forum (sorry can’t remember it but I’ll post the link once I found it).
So here are the steps to gain back the access to your admin tools
1 – go to Start > Run and type in “RegSvr32 MSXML.DLL” and press ok. Repeat the step but replace with “RegSvr32 MSXML2.DLL” and “RegSvr32 MSXML3.DLL”
*Note: Should you get any error during this step, try install Microsoft Core XML Services (MSXML)
2 – Navigate to %SystemRoot%\System32 and look for the files with the .msc extension.
3 – Right click on any of the files and select Properties
4 – Change the open with by clicking on the Change button and browse to %SystermRoot%\system32\mmc.exe and click OK.
5 – Open any of the admin tools to make sure its working
I’m still investigating this issue. It might be a virus but that just my assumption. Will post later if I found something.