SharePoint Database Error Event ID 5586

Posted: 31/08/2011 | Author: | Filed under: SQL Server | Tags: | Leave a comment »

This basically means you’ve run out of disk space for the transaction log (.ldf) on your database server. Use the SHRINKFILE command to reduce it’s size, or better yet increase your disk space if possible. How to reduce the size of the database?

Execute the following command on the relevant database:

COMMAND

EXAMPLE

ALTER DATABASE <databasename>
SET RECOVERY SIMPLE;
GO

USE <databasename>
GO
DBCC SHRINKFILE (<databaselog>,5);
GO

ALTER DATABASE <databasename>
SET RECOVERY FULL
GO

ALTER DATABASE SP_Content_DB
SET RECOVERY SIMPLE;
GO

USE SP_Content_DB
GO
DBCC SHRINKFILE (WSS_Content_log,5);
GO

ALTER DATABASE SP_Content_DB
SET RECOVERY FULL
GO

 

Important! Set your Recovery mode to SAMPLE prior to SHRINKFILE and remember to set it back to FULL post SHRINKFILE.

Important! Notice in the example above, that my database log is name differently from the database? That’s the logical name, and that’s the name that should be used. You can get the logical by executing the following command on the relevant database.

SELECT name FROM sys.database_files WHERE type = 1

SQL Error–Cannot show requested dialog, nColIndex

Posted: 04/10/2010 | Author: | Filed under: SQL Server | Tags: , | 3 Comments »

 

I got this error trying to attach a database in SQL Server 2008 (see image below). After googling binging around with no success, I decided, just by fluke, to try this operation using a different account.

So I logged into SQL Management Studio with another account and tried this again, and voila!, it worked and I got into the database attach dialog with no problems and completed the database attach operation successfully.

I only wish I had more time to commit and look into the cause of this abnormality, but unfortunately I didn’t. An interesting point to note though, is that both the accounts have the same database roles and permissions.

attachdb_Console_error

Web Service Identity Error

Posted: 10/06/2010 | Author: | Filed under: Uncategorized | Tags: , | Leave a comment »

Configuring Reporting Services as times can be quite painful. If you ever had trouble in getting your Web Service Identity working, you’ll understand what I mean. At times creating a new application pool as opposed to using an existing one will work. But then, at times it will still fail. If this happens, then you would need to manually add in the account in the configuration file. See steps below for this:

  1. Navigate to \Program Files\Microsoft SQL Server\MSSQL.1\Reporting Services\ReportServer
  2. Find the rsreportserver.config file and open it for editing.
  3. Do a search for “WebServiceAccount” and then type in your account. E.g: <WebServiceAccount>myDomain\myAccount</WebServiceAccount> Remember! this account is your Application Pool identity account for Reporting Services.
  4. Save and close the file.
  5. Restart the Reporting Configuration Manager console and apply your Web Service Identity again.
  6. For SharePoint integration, we must ensure that the account has access to the SharePoint Configuration database. And that SharePoint Integration is selected on Database Setup.

Reporting Services SharePoint Add-In Install Failure

Posted: 09/06/2010 | Author: | Filed under: Configuration | Tags: , | 1 Comment »

Twice within this month that I’ve come across this problem. Basically, I’ve had Reporting Services (SSRS) install, had SharePoint installed installed and also got SSRS configured to run in SharePoint Integration mode. The final piece of the puzzle is to install the SSRS Add-In for SharePoint.

Clicking on the .msi file begins the installation. Unfortunately, during the “Removing Backups” stage the install seems to just hang there, after a very long time it eventually rolls back and notifies you that the install has failed. Looking into the Event Logs you’ll notice tons of errors relating to SQL and permissions that it lacks, please note, DO NOT waste your time in attempting to update any permissions within your database.

This is a known issue and occurs with both versions of the install (x86 and x64). To get around this follow the steps below:

  1. Open Command Prompt and navigate to the SSRS Add-In .msi file.
  2. Type and run the following command msiexec /i SharePointRS.msi SKIPCA=1 (or msiexec /i SharePointRS_x64.msi SKIPCA=1 if installing x64 version)
  3. After install has completed, navigate to \Users\<Username>\AppData\Local\
  4. Type and run the following command rscustomaction.exe /i
  5. Allow the install to complete

If you do encounter any issues during or after running the above then go through the following technical article on TechNet. It’s for SQL 2008 but also applies to SQL 2005.

Truncating SQL Log Files (.ldf)

Posted: 09/06/2010 | Author: | Filed under: Uncategorized | Tags: , | 7 Comments »

Firstly, I hope you have planned your SharePoint environment capacity and growth rate way before implementation. Now that I’ve said my piece, if you ever come across an environment that is running low on disk space on SQL server then truncating the Log Files (.ldf) will be something to consider. Maybe even create a maintenance plan, that performs this action weekly. To truncate the logs you can execute the script below, which I found on Pinal Dave’s blog, read more about it here.

USE <DatabaseName>

GO

DBCC SHRINKFILE (<LogName>, 1)

BACKUP LOG <DatabaseName> WITH TRUNCATE_ONLY

DBCC SHRINKFILE (<LogName>, 1)

GO

If you need to find your <LogName> and it’s size, you can execute the following script prior to truncating the log.

USE <DatabaseName>

exec sp_helpfile

 

Warning: Please see comments related to this post prior to proceeding with this action. Special thanks to all for their clarification and insight into this.

Moving Configdb, a four step process.

Posted: 21/03/2010 | Author: | Filed under: Configuration, SharePoint, SQL Server | Tags: , | Leave a comment »

Note: It is strongly recommended that you read the available literature on TechNet regarding moving SharePoint database prior to performing the move.

Step 1: From the Central Administration interface, remove the SharePoint server. Run psconfig with the disconnect switch.

Step 2: Copy  the database .mdf and .ldf files to the new database.

Step 3: Run psconfig with the connect switch.

Step 4: Run SharePoint Config wizard.

All done :)

Error Database Event ID: 5586

Posted: 21/12/2008 | Author: | Filed under: SharePoint | Tags: | Leave a comment »
error

Ever got this error? Describing that an unknown SQL Exception 10054 has occurred, and as the description states some communication/connection seems to be the problem.

After poking around a little, I found a suggestion indicating that an update in account credentials would help. The surprising thing is, I’ve not changed any accounts nor passwords. Nevertheless, I gave it a shot using the stsadm.exe utility (see command below).

stsadm -o updatefarmcredentials -userlogin <domain>\<account> -password <password>

Voila! all works fine again.

Security Hardening your SQL 2005 Server

Posted: 15/12/2008 | Author: | Filed under: SQL Server | Tags: , | Leave a comment »

Microsoft’s White Paper recommends:

  • Blocking UDP port 1434 completely.
  • Configure SQL Server named instances to listen on a nonstandard port.
  • Block then reassign TCP port 1433 (database installed on default instance).
  • Configure client aliases.

Basically it comes down to ensuring that only authorised computers can communicate with the SQL Server.

Block then reassign TC Port 1433

1) Click Start –> All Programs –> Microsoft SQL Server 2005 –> Configuration Tools –> SQL Server Configuration Manager.

2) On SQL Server Configuration Manager, on the left pane expand SQL Server 2005 Network Configuration. Under SQL Server 2005 Network Configuration, click on the corresponding entry (default instance will be Protocols for MSSQLSERVER).

sql

3) On the right pane, right-click TCP/IP and click Properties. Click and select the IP Addresses tab. Every IP address listed for SQL Server will be listed as an entry.

sql01

4) Clear all the values for TCP Port and TCP Dynamic Ports.

sql02

5) Under IPALL, clear the TCP Dynamic Ports value. And in the TCP Port field, enter a port value for the instance of SQL Server to listen on. Eg: 22000

sql03

6) Click OK, and click OK again for the message box stating that changes made will not take effect until SQL Server Service is restarted.

7) Open up Service Console (RUN services.msc). Restart the SQL Server service.

sql04

8) Open up Event Viewer (RUN eventvwr). Under Application you will see a log describing your new setting.

sql05

9) Open up Windows Firewall from Control Panel. On the Exceptions tab click Add Port. Type in the name and port number to block the default TCP port (Eg: TCP 1433). Also ensure that the scope is set to Any Computer (including those on the Internet).

sql06
sql07
sql08

10) Select the port just created and ensure that it is unticked (closed).

sql09

11) Repeat the above 2 steps for UDP port 1434.

Configuring Client Alias

1) Open SQL Server Configuration Manager.

2) In the left pane, click SQL Native Client Configuration. On the right pane, right-click Aliases and click New Alias.

sql010
sql11

3) On the Alias box, enter a name for the new alias (Eg: sharepoint). Enter in the port number configured earlier (Eg: 22000). Also ensure that the protocol is set to TCP/IP and that the server name is filled in as well. Once done click on OK.

sql012

4) We can test the new Alias by opening up SQL Server Management Studio. On the login box, under server name, enter in the new Alias and click Connect. If successful you will be connected through with the proper objects all available.

sql013
sql014

Uninstalling Windows Internal Database (WID)

Posted: 10/09/2008 | Author: | Filed under: SharePoint | Tags: | Leave a comment »

If you’re curious, then from command prompt run this command:

msiexec /x {CEB5780F-1A70-44A9-850F-DE6C4F6AA8FB} CALLERID=ocsetup.exe

And then follow the Uninstall process.

If you’re running a 64bit Windows 2003 Server then run this command:

msiexec /x {BDD79957-5801-4A2D-B09E-852E7FA64D01} CALLERID=ocsetup.exe

Note: The WID does not appear under Add/Remove programs, so don’t waste your time searching there.

Device activation error 42000

Posted: 10/09/2008 | Author: | Filed under: SharePoint | Tags: | Leave a comment »

Got this error while doing an SQL 2000 restore (.bak) for a SharePoint site. Realised that under options the .ldf log file was on a different path to the .mdf file. Change the path to match the .mdf path, and the restore process went through fantastic.

Follow

Get every new post delivered to your Inbox.