All posts by npulis

How To: Import PST files into Exchange 2010 with PST Capture

The new FREE application from Microsoft will let you import any PST file into an Exchange 2010 mailbox. This is fairly easy to use and if you want a quick way to import a PST file into an Exchange mailbox here’s how.

First of all download the PST Capture from here.

Secondly you have to have the followin pre-requisits before installing and using this product, which are:

– Outlook 2010 64bit version installed *
– Logged-in user being in the Active Directory group “Organization Management” group
– Logged-in user being in the Active Directory group “Administrators”
– Logged-in user being in the local administrators group

Once you install the product see the list below for the possible problems/solutions:

Error: RPC error from Exchange
You possible have mailbox size restriction and it exceeded during import

Error Openinng Mailbox
You don’t have the Outlook 64bit installed and possible have the 32bit

Error: Outlook installation not found
You Haven’t installed Outlook

(882)

Fix: Cannot run or delete a job in SQL after changing sa password

After changing the password of the SA or the user which is in charge of running jobs on the SQL server, the jobs will not work and you will not be able to delete the jobs with the error ‘Login failed for user SA‘. This can temporary solved by changing the SA or the user used password back to it’s original state and delete the job, but still you will not be able to run the job.

To solve this permanently you have to open the ‘Management Studio’, right-click on the job and select ‘Modify’. Click on the ‘Manage Connections’ and replace the username and password on each connection if you have more than the default one using the new password that you have recently changed.

This modification you have to do it for every-time you change the password of the ‘sa’ or user you use to run the jobs in the Manage Connections.

(655)

Fix: Outlook cannot send emails data file cannot be accessed (error 8004010F)

You may notice that all of a sudden you can recieve mails but cannot send. Outlook will popup a message saying ‘Outlook data file cannot be accessed (error 8004010F)‘.

Thou the PST files are there and accessible, the only way to fix this is to re-create your Outlook Profile from the Control Panel by:

Open Control Panel
Open Mail 32-bit
Click on Show Profiles
Select the profile in question
Click Remove

Now open Outlook and reconfigure the account. This should fix the problem

(7363)

How To: Backup databases for SQL 2000 MSDE with SQLMaint.exe

To Backup a database from command-line and using SQL 2000 MSDE version, you must use the SQLMAINT.EXE file situated in the ‘C:\Program Files\Microsoft SQL Server\MSSQL\Binn’

The backup cannot be done for all databases at once and it must be done individually. This can be done by the line below and then just duplicate it for multiple databases.

Create a batch file and run the following:

CD "C:\Program Files\Microsoft SQL Server\MSSQL\Binn"
sqlmaint -D "MyDB" -BkUpDB "X:\Backups\Data" -Rpt "X:\Backups\Reports\MyDB.txt" -BkUpMedia DISK

(1554)

How To: Execute and run files from a stored procedure in SQL Server

Sometimes when you need to automate some stuff from the SQL server you need to create a batch file and run it in the Task Scheduler. This way you can run the jobs you need to do and then run the executable or batch file you need from a Stored Procedure.

Firstly you need to make sure that the XP_CMDSHELL is enabled. This will allow you to execute the files from SQL.

This can be easily done from the Surface Area Configuration tool or by executing the following code:

EXEC master.dbo.sp_configure ‘show advanced options’, 1
RECONFIGURE
EXEC master.dbo.sp_configure ‘xp_cmdshell’, 1
RECONFIGURE

This should enable the XP_CMDSHELL. Now to execute a file you need to add the following SQL code to your present Stored procedure:

DECLARE @myfile varchar(200)
SET @myfile = ‘C:\sysfiles\copytootherserver.bat’
EXEC master..xp_cmdshell @myfile

(8403)

Fix: Getting rid of ‘You have been logged on with a temporary profile’ on Windows

For Windows Vista and 7. This might have happen to most of us. When you log in your profile, you get a popup on the bottom right that says ‘You have been logged on with a temporary profile. You cannot access your files and files created in this profile will be deleted when you log off. This sometimes happens when the username has either been changed or the folder of the profile has been deleted. So Windows will continue to look for it and leave you with a temporary profile. To fix this you need to make the following to restore the folder.

:: Log on the machine as an Administrator
:: Click on Start and type regedit
:: Find the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
:: There are a lot of folders in the key. Find the ones with the .BAK at the end
:: Delete the profiles in question with the .BAK extention (Make sure you take a backup of the registry first)
:: Close Regedit
:: Restart PC

After you log into the computer, the profile folder you are having problems with is re-created.

(8719)

Fix: How to remove hidden or phantom interfaces from Windows

Sometime you will note that some network interfaces would either not work or just give errors. This usually occurs when using images on HyperV but just in case you need to remove hidden or phantom devices like ‘network adapter #5’, here’s how.

:: Open command prompt
:: Type CMD
:: Type set devmgr_show_nonpresent_devices=1
:: From the same window (Do not close the window in this process), type devmgmt.msc

This will load the Device Manager. Now, click on ‘View’ and select ‘Show hidden devices’.

Now you can simply either delete the hidden/phantom interfaces or uninstall the device.

(961)

Fix: Slave server not connecting to master on Yosemite Server Backup

When you install Yosemite Backup solution on a server having multiple network cards, the agents will not work and the server will not be visible by the master server. This is because Yosemite binds itself to a network card. Now, to fix this, simply edit the ytconfig.ini in the Yosemite folder and add the following line under the configuration tab and set it to your the IP address of the network card:

bindTo=10.1.1.1

(819)