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 ...
Posts
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 ...
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>>...