Transfer DSN files from Computer A to Computer B:
1. On Computer A, open the Registry Editor by typing “regedit” in the Windows search box under the Start menu and selecting regedit.exe
2. Navigate to the following registry key :
- For User DSN data sources:
HKEY_CURRENT_USER > Software > ODBC
- For System DSN data sources:
HKEY_LOCAL_MACHINE > Software > ODBC
3. Right-click on the ODBC.INI folder, choose Export, and save the .reg file to the location of your choice
4. Copy the .reg file (or files if you have both User and System DSN data sources) to any location Computer B
5. On Computer B, double click the .reg file(s) to import the DSN data sources to the registry (select “Yes” and “OK” when prompted)
– Windows cannot verify the digital signature for this file. (0xc0000428)
– Windows requires digitally signed driver OR Digitally signed driver is required.
– Digital Signature Not Found.
– Cannot load or install an unsigned driver.
– Cannot run (execute) an unsigned software (program).
– Windows did not find a Microsoft signature associated with the software package you want to install.
Solution: Disable Driver Signature Enforcement in Windows:
Open “Command Prompt” in administrative mode
bcdedit /set testsigning on
Restart your computer.
(Set off to enable)
or e.g.: TASKLIST /FI "IMAGENAME eq cmd.exe"
wmic process list
or e.g.: WMIC /OUTPUT:C:\ProcessList.txt path win32_process get Caption,Processid,Commandline)
select disk X
select partition Y
If you are using the POP3 Connector on Windows SBS 2008, you may encounter this error in the event log:
One or more (5) e-mail messages in the POP3 mailbox account ‘’ on the POP3 server ‘’ have invalid header fields. Because of this, the messages cannot be delivered to the Exchange Server mailbox ‘’ in Windows Small Business Server. The messages are still on the POP3 server. To resolve this issue, connect to the POP3 mailbox account, and then manually retrieve or delete the messages.
By default the POP3 connector will stop processing new messages after 5 protocol errors so once this happens, you will not receive any email.
Increase the MaxProtocolErrors from 5 to something bigger:
Set-ReceiveConnector -identity ($Env:computername + “\Windows SBS Fax Sharepoint Receive ” + $Env:computername) -MaxProtocolErrors 300
Next step: remaining messages to be downloaded, but the messages with invalid headers will still not be downloaded.
To fix this:
Set-ReceiveConnector -Identity ($Env:computername + “\Windows SBS Fax Sharepoint Receive ” + $Env:computername) -DefaultDomain $Env:UserDNSDomain
When starting the software an error message as below may occur: “System.IO.FileNotFoundException: Could not load file or assembly ‘System.Xml.Linq, Version=126.96.36.199, Culture=neutral, PublicKeyToken=b77a5c561934e089’ or one of its dependencies. The system cannot find the file specified.”
A Microsoft .NET Framework 3.5 file System.Xml.Linq.dll or files supporting System.Xml.Linq Namespace are missing or corrupted or you do not have Microsoft .NET Framework 3.5 installed on your computer.
– Check install status .NET Framework 3.5….
– In the Command Prompt, type: “sfc /scannow” (with the quote marks) System File Checker – SFC – will scan your system and (hopefully) fix some of your system files.
– Microsoft provide a .NET Framework Repair Tool which can be downloaded from: http://www.microsoft.com/en-gb/download/details.aspx?id=30135
dnscmd /config /EnableVersionQuery 0