Rain Rain PLEASE Come!

The lengthy drought has made me depressed. Looks like the relief is coming. Very excited. Please don't let me down.



 

 

IE9 failed to open after Win7 SP1 installed

Symptom:

1. Got this error at startup. "The ordinal 379 could not be located in the dynamic link library iertutil.dll."
   


2. Checked the update history and found out the 'failed' status in "Windows Internet Explorer 9 for Windows 7". Opened it up and got the "Error Code 355"

I thought this could be a difficult fix or hard-to-find-solutions problem after a quick google search without luck.

Eventually I came cross Microsoft KB 929833, and decided to give a shot by running 'sfc /scannow' command. It took a good 30 minutes and told me to reboot in the command prompt. I did and to my surprise, the IE9 opened up.

SQL Backup Script

To create a simple backup job by using SQL Server Agent in MS SQL Server Management Studio

DECLARE @BackupPath VARCHAR(100)

SET @BackupPath = '\\<UNC Path>\PM_' + CONVERT(VARCHAR, GETDATE(), 112) + '.bak'

BACKUP DATABASE [<database_name>]

TO DISK = @BackupPath
GO

 

Step by Step Site to Site VPN setup

A good video demos the Site-to-site VPN tunnel setup on ASA.

http://www.petenetlive.com/KB/Article/0000072.htm

Incoming email setup on my SharePoint Servers

WSS3.0



 

SharePoint2010

Fun Never Stops Applying Windows Updates

"100 important updates"!!?? Seriously?



 

See these security updates? yuck!

 



 

 

 

 

 

 

Error connecting to WSS database backup files

I was testing Selective Restore Manager for SharePoint from Metalogix on my WSS3.0 server. I had no problem connecting to SharePoint database or SharePoint site, but was not able to connect to any database backup file. Then of course, I could not test the file restore either.

At "Add connection" drop-down, I selected "Connection to SharePoint Database Backup file - ready only' option, pointed to my BAK files location, (both network share and local disk). The SQL server name was automatically populated as "<SERVER_NAME>\MICROSOFT##SSEE", and the Authentication is set to "Use Current Windows user". Once I clicked connect and was returned with the following error: 

I contacted Metalogix and was told it's the permission issue to sql. However, I don't have any other account besides my Windows domain admin account used to set up WSS server. I could not enable the remote connection either because this edition of SQL does not support it.

Then I used SQL server management studio express to back up the content database, then SRM seems to see the backup file but SRM crashed as soon as it started to restore.



 

So maybe this is not the backup solution for me till I found the workaround.