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…
-
Cannot Connect to the Meeting: Live Meeting
Today I experienced some issues with Office Communicator 2007 R2 and Live Meeting 2007. First, Communicator was complaining about not being able to update the address book. Then, when I tried to start a meeting using Live Meeting (via the Meet Now function), I received the following error: When I looked to find some hints to the “Live Meeting cannot connect to the meeting.” message online, all the posts were pointing to issues with trying to connect to an external meeting. I was trying to connect to my internal Office Communications Server. I next tried to do a nslookup on the FQDN for the server and I received a reply…
-
Office Communications Server 2007 R2 and NIC Teaming
I have been trying to install Office Communications Server (OCS) 2007 R2 Standard Edition for a few days now without success. During the server install process (after the schema has been extended), a warning shows up in the activation logs of every role (Standard Edition Server, Web Components Server, Web Conferencing Server, Audio/Video Conferencing Server, Application Sharing Server, and Application Host). The warning on the main Deployment Log states: Warning [0x03EC796D] Wizard was successful, but one or more warnings occurred during execution of the wizard. Please check the log file for more information. The warning within each activation log states: Warning [0x03EC78E4] More than one DNS records are found for…