One of the Windows SBS 2003 servers I administer had a BSOD and after bringing it back up the Exchange store wouldn't mount. It gave the error "The database files in this store are inconsistent."
I used the Eseutil.exe utility to check the consistency of the store.
"c:\Program Files\Exchsrvr\bin\eseutil.exe" /mh "c:\Program Files\Exchsrvr\MDBDATA\priv1.edb"
From the output I noticed 2 things. The state was set to dirty shutdown and one of the logs was missing or corrupt.
State: Dirty Shutdown
Log Required: 16655-16655 (0x410f-0x410f)
I tried running Eseutil.exe /r but received an error. I then proceeded to run Eseutil.exe /p which repairs the database. Once that was complete I ran an offline defrag, Eseutil.exe /d, and lastly isinteg.exe -s servernsmr-fix -test alltests which checks for integrity weaknesses.
I was then able to mount the store and users were able to access their mailboxes. A word of caution Eseutil.exe /p is usually a last resort and can cause some data loss. Microsoft recommends restoring from a clean backup rather then doing a repair. I'll leave that decision up to you.
By default SharePoint uses a white icon for PDF documents. It's rather plain. To use a PDF icon follow these steps...
Download the PDF icon to your SharePoint server.
Navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\IMAGES
Place the image in the IMAGES folder and name it icpdf.gif
Edit C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\XML\DocIcon.xml
Insert <Mapping Key=”pdf” Value=”icpdf.gif”/> between the following lines...
<Mapping Key="onetoc2" Value="icont.png" EditText="Microsoft OneNote" OpenControl="SharePoint.OpenDocuments"/>
<Mapping Key=”pdf” Value=”icpdf.gif”/>
<Mapping Key="png" Value="icpng.gif"/>
Save the file and restart IIS.
Update: Make sure the quotes are correct when you paste the text into the configuration file. Compare them with the rest of the quotes in the document.
Recently a client of mine got some spyware. I cleaned it up with Malware Bytes as I usually do but she was still experiencing popups in Internet Explorer. I reset IE and ran additional scans but the PC kept getting popups. I downloaded and ran ESET's Online Scanner and it caught all the spyware Malware Bytes missed.
I had a user that was getting the following error message in Outlook 2007...
There is a problem with the selected printer. You might need to reinstall this printer. Try again, or use a different printer.
To fix this I removed the Microsoft KB2509470 update. Remember to blacklist the update so it does not re install itself later.
To find out your version of SQL download/install/open Microsoft SQL Server Management Studio Express then click New Query
Paste the below code in the query pane on the right
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
and click Execute
In the results window it will display the version, Service Pack, and edition.
For older versions refer to the command and chart on the Microsoft KB 321185.
If you have a subfolder that you'd like to migrate from one repository to another SVN has some built in tools that allow you to do that.
- Open a command prompt and point it to the directory SVN is installed. For Windows that is C:\Program Files\VisualSVN Server\bin. The default Repository directory is C:\Repositories.
- Type: svnadmin dump "path to Repository" > repoDumpFile.dmp
- You'll then to filter out everything but the sub directory you want to migrate.
Type: svndumpfilter include "Path to Subfolder" < repoDumpFile.dmp > Filtered-repoDumpFile.dmp
- The above command will include all revisions even those not relevant to the subfolder you are migrating. If you'd like to remove the non relevant revisions and/or re number them you can use the below command instead of the above.
Type: svndumpfilter include "Path to Subfolder" --drop-empty-revs --renumber-revs < repoDumpFile.dmp > Filtered-repoDumpFile.dmp
- Let's create the new Repository.
Type: svnadmin create "Path to Repositories\New Repository Name"
- Now we import the file.
Type: svnadmin load --ignore-uuid "Path to Repositories\New Repository Name" < Filtered-repoDumpFile.dmp
A client of mine mentioned he wasn't able to access his mapped drives over the VPN. I remotely connected to his PC and noticed if I pinged hostname.domain.local it resolves to 184.108.40.206. I confirmed he was connected to the VPN and I could ping the IP of the PC directly. I did a quick lookup of that IP address and it turns out its owned by Comcast. Comcast's DNS Helper service was to blame. They were resolving all failed hostnames to their IP address rather then letting it fail and allowing his companies DNS server to resolve it correctly.
To fix this you have 2 options:
- Opt-Out of Comcast's DNS Helper service
- Switch to a public DNS service like OpenDNS or Google's DNS servers
Right now Comcast has this enabled by default for all customers with dynamically assigned IP addresses. Business customers are not affected.
Below is an article on the topic that is a great read.
A client of mine is using Quickbooks 2009 and has been having issues with accessing Quickbook files hosted on the Quickbooks database server. All firewall ports are open, the database server is running and the Quickbooks Connection Diagnostic Tool says everything passes. They access the files from a mapped drive to the server. It's never ran or performed as well as I think it should on a gigabit network with fairly new machines.
After doing some research I tried accessing the Quickbooks files over a UNC path rather then a mapped drive. The performance difference was night and day. The files opened nearly instantly and it ran as if the QBW files were locally stored.
From Intuit's website...
Note: In prior versions of QuickBooks, Intuit recommended that a mapped network drive be used to access QuickBooks company files. With QuickBooks 2006, the UNC path, or direct path to the company file will work better than a mapped drive.
A client of mine was having the error 0x8004010F in Outlook 2010. I repaired the PST and it fixed 30 or so errors but I was still having the issue. I ended up creating a new Outlook profile using the following link...
After creating the new profile I could not open or export the previous PST. I realized she had checked the option Run this program in compatibility mode for: Windows XP checked. Once I unchecked that Outlook 2010 could open & export the previous PST.
If Outlook 2010 is prompting for UAC everytime you open it check to make sure you don't have Run this program in compatibility mode for: or Run this program as an administrator checked.