Microsoft’s Office 365 has built-in features that provide physical, logical, and data security for organizations large and small. While in San Francisco, I sat down with Liam Cleary [Blog – Twitter], Microsoft MVP and popular technology speaker to discuss implications of the impending GDPR legislation, as well as Office 365 security overall. 02:06 GDPR changes now affect any organization that works with any European organization 02:28 Office 365 requirements 02:59 Missing answers 03:01 When it comes to content, Microsoft [has] all the tools that you need 03:33 If haven’t implemented those tools…. 04:38 GDPR dashboard 04:49 PNP dashboard – LINK 06:04 Security Compliance Center 07:31 The onus is still on…
-
-
SharePoint Install – Cannot connect to database master
This morning I encountered an error I hadn’t seen in a while, so I thought I would share the resolution with everyone (and keep a record for myself the next time it happens). When configuring SharePoint using PowerShell after the initial install, you may encounter the error shown below. [New-SPConfigurationDatabase: Cannot connect to database master at SQL server at ServerName. The database might not exist, or the current user does not have permission to connect to it.] The error is misleading, as it implies that either there is no Master database on the SQL server or the current user doesn’t have the correct permissions. I did check the user’s permissions in SQL:…
-
Error Connecting to Database Server
I recently setup yet another SharePoint farm (this time using virtual machines) and ran into a problem that happens all too often. The scenario is this: I setup MS SQL server in preparation for getting SharePoint installed on a separate server. After setting up your service accounts in Active Directory and installing MS SQL on Server1, I set off installing SharePoint on Server2. When I got to the screen in the Specify Configuration Database Settings within the SharePoint configuration wizard, I received the following error: Cannot connect to database master at SQL server at ServerName. The database might not exist, or the current user does not have permission to connect…
-
Intermittent forbidden errors (403)
After applying a new master page and related theme components, we have been receiving reports that users were being presented with 403 ‘forbidden’ errors when trying to load our intranet site. After refreshing the screen four (4) times, the page would finally load. I checked the web server’s Application log and found that every time a user received a 403 error, there was an “Information” Web Event message logged with a source of ASP.NET and an ID of ID 1314. The body of the event included, among other information: Event code: 4011 Event message: An unhandled access exception has occurred. After doing research and knowing this was most likely a…