Report Server (MSSQLSERVER) cannot load the SQLPDW extension
I've got the subject error on our 64 bit SQL 2008 R2 box. I've also got the Teradata error and used the steps in the following article to try and avoid it. My questions now are - 1) What is SQLPDW? 2) Can the subject error be avoided using the same method for the Teradata error, i.e. comment out all references to SQLPDW? Thanks, KevinKevin
October 3rd, 2011 5:28pm

Hi MorrisMK, Based on my research, there is an article about SQLDPW, please see: In your case, I cannot reproduce this issue on my test environment. I suggest you that try to use the same way to deal with this issue in the link above. Please backup the RSreportserver.config file before modify it. If you have any more questions, please feel free to let me know. Thanks, Bin LongPlease remember to mark the replies as answers if they help and unmark them if they provide no help.
Free Windows Admin Tool Kit Click here and download it now
October 5th, 2011 9:51am

Is it possible to bring some of that information over to this link? Security allows us to browse MSDN, but the link you provide above is non-accessible. When the error occurs, it generally occurs twice and the second error occurs a few milliseconds after the first. The error appears to recur roughly every other day. R, J
November 16th, 2011 10:55pm

Crakdkorn, I'm not sure which information you're refering to. Here's the solution offered in This error occurs because the Teradata extension is registered in the Reporting Services configuration file by default, but the Teradata assemblies are not shipped with SQL Server 2008 or as part of the .NET Framework. If the error message does not bother you, you can ignore the error when it is logged. However, if you want to avoid this error, do one of the following: Open the Reporting Services configuration file located in folder C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer, remove or comment out the Teradata extension. Do this only if you do not require functionality that the Teradata extension provides. Install the .NET Data Provider for Teradata. Do this only if you require functionality that the Teradata extension provides. You can obtain the provider from the Teradata Web site. Reporting Services requires that the provider be version 12 or later. For more information about this issue, please see Thanks, Challen Fu Challen Fu [MSFT] MSDN Community Support I haven't had this problem for nearly two months but it appeared again today. I've commented out all the references to the Teradata extension so I don't know why it appeared again.Kevin
Free Windows Admin Tool Kit Click here and download it now
November 21st, 2011 5:59pm

Why was this marked as an answer??????gimme some slamming techno!!!!
July 8th, 2012 9:07pm

This happens if one deletes a credentialed login used by Reporting Services. Someone removed the login on the local box (a non-admin account) that is used to hit other servers in the domain. The non-admin account uses credentials to run report queries. When removed, the error occurs. In the last round of this (for our team), a table, referenced by a web application that builds a URL was pointing to a non-existing report - in that case, the credentialed user could not see the report (it did not exist as you see in the title of this thread). This similar situation (missing report rather than missing login) brought up the same error. Teradata and SQLPWD seem to be associated with "BIG" data. The terms are more meaningful to the SSRS shell than to a layman. R, J
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2012 2:41pm

I have the same issue the Logs keep throwing error messages. I am using SSRS 2012 on SharePoint 2010 and don't see the entry for the TeraData on C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebServices\Reporting\rsreportserver.config How do I we get rid of this error?
February 20th, 2013 10:24am

I am also using SSRS 2012 on SharePoint 2010 and I'm having the same issue.
Free Windows Admin Tool Kit Click here and download it now
May 17th, 2013 2:19pm

Can you look at it from the point of view that the report is using a third party login - whether SQL Authenticated or through a service account, or perhaps the local administrator set up a third party user and that user was deleted or that user no longer has permissions to the right folder... something along those lines. I am assuming that the error may be related to a permission error. I have to assume it is as in the title "cannot load the SQLPDW extension". Can you post the error? Also, did you try Challen Fu's suggestion as posted by MorrisMK?R, J
May 17th, 2013 7:58pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics