Thursday, January 30, 2014

SQL 2012 and Scale-out-file-server. Unable to Attach a Database

Working with a client with an installation of a Clustered SQL 2012 R2 servers with a Clustered File Server providing SMB3 shares to a Scale-Out-File-Server, we discovered that we could not attach an existing Database file.

The error message is:
Cannot access the specified path or file on the server. Verify that you have the necessary security privileges and that the path or file exists.

As a test, we can create a new database, verify that it exists, detach it, and then immediately try to re-attach it, and we get the error.

We of course have verified that the Administrative User, the SQL Service Account, and the Computers all have full rights to this data directory.

We opened a case with Microsoft, and after 4 hours on the phone, were told that this appears to be a bug when using a UNC, presumably on a Scale-out-file-Server, for our data.

The workaround is to use a SQL command to attach the database instead.



Create database OldData On
              (Filename = '\\sqlserver-1\SQLServer-Data\SQLdata-1\Data\OldData.mdf'),
              (Filename ='\\sqlserver-1\SQLServer-Data\SQLdata-1\Logs\OldData_log.ldf')
for ATTACH

Friday, January 10, 2014

Internet Explorer 11 (Windows 8.1) "Google Bug". Back Button hangs IE

I discovered this week that there is a bug in Google's web page that causes Internet Explorer 11 to hang when you click the back button.

The specific scenario is that when you start on Google's web page, and go to a link of some sort, it can trigger this bug when you click back to return to google. 

This is fairly well documented on some forums, in that it has been like this for a while, and Google seems unwilling, or unable, to modify their code to not trigger this bug. I do not consider it a IE11 bug as much as I consider it a problem with Google.  Microsoft should of course fix their issue, but also you would think that Google might take this seriously. 

To trigger the issue, Go to google.com and search for something that takes you to a Microsoft page.  Example: "Exchange edge server".  Click on the first link and then click on any link on that Microsoft page.  Then click back twice.  The first "back" will work fine because it takes you to the original Microsoft page.  Now click Back again.  IE will eventually display (Not responding) on the status line, and you will need to force a closure of the browser.

I do not know of any workaround, other than to always open any link on the Google web page with a right-click and "Open new tab", or even easier is to use another browse such as Firefox.

Before anyone flames me, I did do all of the standard things such as:

SMTP and Spamhaus blocking. What I learned today.

I was setting up a new client with an Exchange Server, and we discovered that we could not send email to any Microsoft Hosted email addresses.  Basically, to a subdomain of Outlook.com.

All office 365 hosted email domain are subdomains of this address. 

The issue was discovered when we tried to send an email manually using a text based email tool.
The dialog looks like this (note that the unique data has been modified for privacy):

blat.exe -body "this is a test" -to someone@o365hosted.ca -server o365hosted.mail.protection.outlook.com -f me@legit.ca -s "Test of SMTP" -debug
Blat v3.1.1 (build : Feb 27 2013 20:04:23)
32-bit Windows, Full, Unicode

<<6:46 +0000
>>>putline>>> EHLO lab1-exch2013
<<<<... Text removed for clarity

<<Sending stdin.txt to someone@o365hosted.ca
Subject: Test of SMTP
Login name is
Me@legit.ca
>>>putline>>> MAIL FROM:<Me@legit.ca>
<<>>>putline>>> RCPT TO:<someone@o365hosted.ca
>
<<http://www.spamhaus.org/lookup.lasso
*** Warning ***  The SMTP server does not like the name someone@o365hosted.ca.
*** Warning ***  Have you set the 'To:' field correctly, or do you need authorization (-u/-pw) ?
*** Warning ***  The SMTP server response was -> 550 5.7.1 Service unavailable; Client host [123.45.67.89] blocked using Spamhaus; To request removal from this list see
http://www.spamhaus.org/lookup.lasso
>>>putline>>> QUIT
<<


The IP address (not shown) was a static IP assigned to a Telus.Net client.

A quick check at MXToolbox.com revealed that blocked at Spamhaus, and SORBS, but no others.
Next, a check at Spamhaus indicated that the IP Address is listed in the PBL.   What is the PBL you say?  It is a list of addresses that require Authentication or discrete PTR records in order to be trusted.
See https://www.spamhaus.org/lookup/ and enter your IP address for a lookup.
In my case is says:
          

By default, this assumes that the IP is a Dynamically Assigned IP.  In our case of course, from Telus.

There are 2 solutions for our problem of being able to send to any email domain by MX record.
  1. We could go to Telus and request a discrete PTR record, or
  2. we can simple configure the Exchange Send Connector to use the SMTP Smart host of smtp.telus.net.
Update: For Hosted Exchange Hybrid, the above 2 are not options.  Working on a solution..