Will Report Builder 2012 Work with SQL Server 2008???

Simple question really
Will Report Builder 2012 work in conjunction with SQL Server 2008???
Is it worth while upgrading?
The main reason i ask is the ability to export in an xlsx format
Thanks

Hi Gmach,
The version of Report Builder on SQL Server Reporting Service (SSRS) 2012 is Report Builder 3.0. The Report Builder 3.0 manufactures 2010 RDL reports, so it only works with the version of SQL Server 2008 R2 or later. So in your scenario, we can no connect
to SQL Server 2008 Server using Report Builder that on SSRS 2012.
If you have any questions, please feel free to ask.
Regards,
Charlie Liao
TechNet Community Support

Similar Messages

Reporting with Report Builder 3.0 and SQL Server 2008 R2

Hi everyone
I'm trying really hard to find books about Report Builder 3.0 or SQL Server 2008 R2
I found the following books on the "learn" site, sadly they do not cover Report Builder 3.0 or SQL Server 2008 R2 since there all too old.
Microsoft® SQL Server® 2008 Analysis Services Step by Step
Microsoft® SQL Server® 2008 MDX Step by Step
Microsoft® SQL Server® 2008 Reporting Services Step by Step
What are good books (like the ones above) for the newest system?

Hello wishmasterIN,
Thank you to post your question on TechNet forum.
Based on my experience, the books are always delayed to the new technology, since the author need time to summarize and analyze the new features in the new product or technology, write it down and publish it. If you want to have a quick learning about the
new technology, MSDN library is a good place. It can be a cookbook for you. It contains some detail steps for tools, such as Report Builder or BIDS. It also contains many new features introduction. It is always very useful for you to understand the new features.
In addition, it is based on web and many links make you can jump to the other technical point freely. The most important is all of these is free and all the information will be updated if the new feature is released.
In short, if you want to learn the latest technology about Microsoft product, MSDN is a good choice. I hope my introduction is helpful to you.
Regards,
Edward
Edward Zhu
TechNet Community Support

ColdFusion8 works with SQL Server 2008 compatibility level 90?

We're currently is using ColdFusion8 and need to upgrade the database from SQL Server 2000 to 2008. Will ColdFusion8 work with SQL Server 2008 compatibility level 90?

Hi,
ColdFusion 8 is not supported with SQL Server 2008. A list of supported environment is available at http://www.adobe.com/products/coldfusion/pdfs/cf8_systemsupportmatrix.pdf
Regards,
Anit Kumar

Creating the report in BI Publisher with SQL SERVER 2008

Dear Team,
I want to create report on BI Publisher....i am able to create report with the help of oracle database ...but i dont'nt know how to create DATA MODEL in sql server 2008 ...
plz tell me the wright way....
Thanks,
Him..

Hi Jin Chen,
Thank you for your response. I have disabled all the Symantec End Point Protection Service, but problem persists..
Further, I have checked through the ULS Log in SharePoint, there is more error reported there:
11/03/2010 15:19:48.44 ReportingServicesService.exe (0x3510)
0x4064
Windows SharePoint Services Database
6f8g Unexpected
Unexpected query execution failure, error code 282. Additional error information from SQL Server is included below. "The 'proc_GetTpWebMetaDataAndListMetaData' procedure attempted to return a status of NULL, which is not allowed. A status of 0 will be
returned instead." Query text (if available): "{?=call proc_GetTpWebMetaDataAndListMetaData(?,'F77D6A37-F8D2-492C-911C-923C8A135DEB',?,NULL,1,?,?,6187)}"
11/03/2010 15:19:51.46 ReportingServicesService.exe (0x3510)
0x4064
Windows SharePoint Services General
8e2s Medium
Unknown SPRequest error occurred. More information: 0x80020009
11/03/2010 15:19:51.69 ReportingServicesService.exe (0x3510)
0x1EEC
Windows SharePoint Services General
8e2s Medium
Unknown SPRequest error occurred. More information: 0x80020009
Do you have any idea based on the error above?

Report builder error after applying sql server 2008R2 SP3 when click on report builder gives error like 'Application validation did not succeed. Unable to continue.

Hi All,
I applied SQL server 2008 R2 SP3 recently but report builder doesn't work since then
When click on report builder gives error like 'Application validation did not succeed. Unable to continue.
and when I try to see details the error summary like following:
+File, Microsfot.ReportingServices.ComponentLibrary.Controls.dll, has a different computed hash than specified in manifest.
this is urgent.
Please reply me asap.
thanks a lot in advance.
Regards,
Nik
Regards, Naman

Hi nikp11,
According to your description, you recently updated SQL Server 2008 R2 to SP3, Report Builder doesn’t work since then the error occurs: "Application validation did not succeed. Unable to continue".
This is an known issue in SSRS 2008 R2 SP3 that Microsoft has published an article addressing this issue. It is not planning to release a fix for this issue. But we could implement one of the following workarounds:
Install and run Report Builder 3.0 of SQL Server 2008 R2 RTM.
Install and run Report Builder of SQL Server 2014.
Uninstall Service Pack 3 then uninstall Service Pack 2 and then reinstall Service Pack 3.
Reference:
Report Builder of SQL Server 2008 R2 Service Pack 3 does not launch
Thank you for your understanding.
Best Regards,
Wendy Fu

Transact-SQL debugger not working in SQL Server 2008: "...debugger does not support SQL Server 2005 or earlier..."

I have recently installed SQL Server 2008. When I try to execute a query against an Access database, I receive this debugging error:
"Unable to start Transact-SQL debugger. The Transact-SQL debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors)"
Nor will the query execute; I get a transport-level error 0. Any thoughts?

Hi Davidmhjr,
>>Unable to start the Transact-SQL Debugger. The Transact-SQL Debugger does not support SQL Server 2005 or earlier versions of SQL Server. (SQLEditors).
Have you tried to restart the server once you have installed SQL Server 2008? As Naomi N mentioned please check the version of SQL Server you are using.
If you tried to connect to SQL Server 2005 from SQL Server 2008 SSMS, you would not be able to debug and get this error, it happens because T-SQL debugger includes both server-side and client-side components. The server-side debugger components are installed
with each instance of the SQL Server 2008 Database Engine. The client-side components are installed when you install the SQL Server 2008 client-side tools.
So it works with SQL Server 2008 only so far. Another way is you can triy to use SQL Server 2005 SSMS to connect to SQL Server 2005.
More information about configuration requirement to run T-SQL debugger as below, please refer:
There are no configuration requirements to run the Transact-SQL debugger when SQL Server Management Studio is running on the same computer as the instance of the SQL Server Database Engine. However, to run the Transact-SQL debugger when SQL Server Management
Studio is running on a different computer from the instance of the Database Engine, you must enable program and port exceptions by using the Windows Firewall Control Panel application on both computers.
On the computer that is running the instance of the Database Engine, in Windows Firewall, specify the following information:
•Add TCP port 135 to the exceptions list.
•Add the program sqlservr.exe to the exceptions list. By default, sqlservr.exe is installed in C:\Program Files\Microsoft SQL Server\MSSQL10.InstanceName\MSSQL\Binn, where InstanceName is MSSQLSERVER for the default instance, and the instance name for
any named instance.
•If the domain policy requires network communications to be done through IPsec, you must also add UDP port 4500 and UDP port 500 to the exception list.
On the computer that is running SQL Server Management Studio, in Windows Firewall, specify the following information:
•Add TCP port 135 to the exceptions list.
•Add program ssms.exe (SQL Server Management Studio) to the exceptions list. By default, ssms.exe is installed in C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE.
Hope it is helpful.
Regards, Amber zhang

Report Builder 1.0 for SQL Server Reporting Services 2008 R2

We are trying to implement Ad-Hoc Reporting using SSRS 2008 R2.
First of all, it is very unhelpful that all SSRS books are for either 2008 or 2012, even though SSRS has major changes in 2008 R2 compared to 2008.
Our instructional materials indicate that we should build Report Models to abstract out our databases into terms familiar to our business users.
The problem we are having is the difference in functionality between Report Builder 1.0 and Report Builder 3.0. Report Builder 3.0 is touted as having the modern, ribbon based interface that is supposed to make end-users feel more comfortable. However,
all the documentation says that end users are supposed to use Report Builder 1.0 for Ad-Hoc Reporting. And, it seems, that the reports generated by Report Builder 1.0 are not round-trip compatible with all the other reporting tools for SSRS 2008 R2.
The documentation we have illustrates that Report Builder 1.0 is nice for Ad-Hoc reporting, because is based on connecting directly to Report Models, and the end users can directly drag-and-drop entities and fields into their reports.
When we try working with Report Builder 3.0, it seems we must first connect to the Report Model as a Data Source and then build a Dataset query on the Report Model. Only then are some entity attributes available to be dropped into the report.
If the user decides another source column is needed, they have to go back, edit the query, save the query, and then drag the column from the Dataset to the report. This does not seem end user friendly at all!
We are also concerned that if we train our users on the seemingly soon-to-be-obsolete Report Builder 1.0, and get them used to having direct Report Model access, that at some point we will have to move them to the Dataset-interrupted approach of Report Builder
2+. Highlighting this perception of impending obsolescence of Report Builder 1.0 is that in our shop that is starting with SSRS 2008 R2, we cannot figure out how to get a copy of Report Builder 1.0 in the first place.
We just don't see our end users being savvy enough to handle the steps involved with creating Datasets on top of Report Model Data Sources. So we would have to build the Datasets for them. But in that case, what point is there in creating any
Report Models in the first place if DBAs are the ones to make Datasets?
As such, it is hard to envision a forward-looking SSRS implementation that has the end user ease-of-use Ad-Hoc reporting that the SSRS 2008 documentation presents.
What is it that Microsoft actually wants/expects SSRS implementers to do?
Dan Jameson
Manager SQL Server DBA
CureSearch for Children's Cancer
http://www.CureSearch.org

Hi Dan,
Report Builder 1.0
Simple template-based reports
Requires report model
Supports only SQL Server, Oracle, and Analysis Services as data sources
Supports RDL 2005
Bundled in SSRS
Report Builder 2.0 or later
Full-featured reports as the BIDS Report Designer
Doesn't require (but supports) report models
Supports any data source
Supports RDL 2008
Available as a separate web download
In your scenario, you want to use Report Builder 1.0 in SQL Server Reporting Services 2008 R2, I am afraid this cannot achieve. Report Builder 1.0 is available in the box in either SQL 2005 or SQL 2008. It is not available as a separate client apps and is
only available as a click once application.
Report Builder 1.0
Report Builder 3.0
Thank you for your understanding.
Regards,
Charlie Liao
If you have any feedback on our support, please click
here.
Charlie Liao
TechNet Community Support

Database Mail not working with SQL Server Agent

I'm running SQL Server 2005 Standard edition 64 bit with SP2 on a 64 bit machine.
Database mail does not work with SQL Server Agent. When I configure SQL Server Agent to use database mail the test email button is greyed out and inactive therefore I cannot send emails using operators or for jub success failure etc.
I've read that there was supposed to be a fix for this with SP1 but I have SP2 and still receive the same problem. Please can somebody help as I do not wish to use SQL Mail as a work around due to this becomming redundant in future versions of SQL Server.
Kind Regards

The problems solved
steps:
1)we create a mail profile at at Managment->Database Mail ,of SQL Managment
2)we set this account as "default" at Managment->Database Mail -> Configure Database Mail -> Manage profile security
3)At tab "Alert System" of SQL Server Agent properties , we check the "Enable mail profile" , Mail System=Database Mail, Mail profile = "the profile we already create"
4)we create a new operator at "Operators" of sql agent, where at "notification options" -> "Email name" we put the mail where we want to sent the agent the mails at failured job
5)We go at a specific job, at tab "Notifications" ,we check the "email" check box and then we choose the operator we just create, at the text box next to check box.
I hope not to forget something
Thank You all for the help

Can TS work with sql server compact or express?

I'm don't have much experience with the underpinning of database systems. I know conceptually how they work and can hack my way through sql queries. Is there something fundamentally different about a Sql Server Compact itnstall versus Sql Server versus Sql Server Express? Can TS work with any of them with a proper connection string?
My problem is at our local site a previous employee set us up on Sql Server and wrote a web app (.asp) to do the query for presentation on a web page. At an offsite location they can't install Sql Server and I'm trying to figure out the best path for them to be able to use the same .asp tool we have. My gut feeling is the .asp tool is probably set up such that it wouldn't take much to make it work with MySql but because I don't have the luxury of time I'm hoping someone can point me in what they think might be the easiest direction (whether that is sql compact if possible or MySql for them).

Hi,
TestStand works with SQL server express. (not sure about SQL server compact).
Ravi

Distributed transaction using linked server not working in SQL Server 2008 64 bit

Hi. I have had an issue trying to get distributed transactions to work in SQL Server 2008 using a linked server. The error message I get is
OLE DB provider "SQLNCLI10" for linked server "pod1" returned message "No transaction is active.".
Msg 7391, Level 16, State 2, Line 3
The operation could not be performed because OLE DB provider "SQLNCLI10" for linked server "pod1" was unable to begin a distributed transaction.
My Environment:
Windows Server 2008 Enterprise 64 bit, SQL Server 2008 Enterprise 64 bit
Problem occurs with multiple different builds of SQL Server 2008 - I have been able to reproduce the problem with 10.0.1600.0, 10.0.1779.0 (CU 2), as well as 10.0.2531 (SP1)
I am aware that other people have had this issue and have reviewed all existing posts. I have verified that the MSDTC is configured correctly on both machines. I have also used DTCTester to verify that DTC is working correctly on all machines in question.
None of the mentioned resolutions has solved this problem for me.
I am not seeing this problem occur on my 32 bit test machines - it is only occurring if at least one of the two machines is 64 bit.

Hi All,
I realise that this topic may be a little bit out-of-date but if someone gets here from some search engine trying to find a solution for DTC problems, this MAY be useful.
So... I recently had the same issue, tried all the approaches described in KB and other articles, but it didn't help. Because my task to solve this was not of the highest priority I forgot about it for some time.
Today I was troubleshooting some other issue and, by accident discovered source of that first problem:
In the EventViewer I found Error entry logged by MSDTC saying:
"The local MS DTC detected that the MS DTC on vm-server1 (other machine name that also runs DTC - my comment) has the same unique identity as the local MS DTC. This means that the two MS DTC will not be able to communicate
with each other. This problem typically occurs if one of the systems were cloned using unsupported cloning tools. MS DTC requires that the systems be cloned using supported cloning tools such as SYSPREP. Running 'msdtc -uninstall' and then 'msdtc -install'
from the command prompt will fix the problem. Note: Running 'msdtc -uninstall' will result in the system losing all MS DTC configuration information."
So I followed suggestion and run:
msdtc -uninstall
msdtc -install
This solved my problems with DTC. Hope it will help someone.
Piotr

DI Server with SQL Server 2008

Hello.
In the company where I work we develop an application that uses B1WS.
In the development environment had the following characteristics:
SAP Business One 2007 SP01, PL 09
SQL Server 2005 Developer Edition
Windows XP Professional SP 3
SAP Business One Web Services 1.0
At the time we applied to the deploying the SAP Business One version 8.8, but I had a serious problem. The test environment has the following characteristics:
SQL Server 2008 Enterprise Edition
SAP Busines One 8.8 * PL 10
Windows Server 2008
The problem is that when trying to connect to the DI Server generates the following messages:
The TAO NT Naming Service has stopped. (WithOut DBUser and DBPassword)
Unable to access SBO-Common database Login (With DBUser and DBPassword)
I tested the connection directly to the DI Server disponbile by example in the SDK and it generates the same error. For the SAP interface is connected correctly.
DI Server allows connect with SQL Server 2008?
Messagge:
<DatabaseServer>mv-05910a0046</DatabaseServer>
<DatabaseName>Prueba</DatabaseName>
<DatabaseType>dst_MSSQL2008</DatabaseType>
<DatabaseUsername>sa</DatabaseUsername>
<DatabasePassword>12345</DatabasePassword>
<CompanyUsername>manager</CompanyUsername>
<CompanyPassword>12345</CompanyPassword>
<Language>ln_English</Language>
<LicenseServer>mv-05910a0046:30000</LicenseServer>
Thanks
Edited by: Andres Naranjo on May 14, 2010 12:47 AM
Edited by: Andres Naranjo on May 14, 2010 3:56 PM
Edited by: Andres Naranjo on May 14, 2010 3:58 PM

Had the same error
'The TAO NT Naming Service has stopped.'
Was using the external IP address for the LicenceServer - which is on the same server as SAP DIserver and B1WS.
I changed to using localhost:30000 and that solved the issue.
I suspect if I had used the internal IP it would have worked as well (ie the one you get from ipconfig) but as it works I'm not going to test that.
HTH

ODBC function SQLDriverConnect() crashes with SQL Server 2008 R2

When calling the SQLDriverConnect() function from a 64-bit process and selecting a system DSN with a SQL Server Native Client 10.0 ODBC driver with SQL Server 2008 R2 SP3, then this call crashes here:
    sqlncli10.dll!SNIMemRegion::Pop() + 0x77 bytes
    sqlncli10.dll!SNIPacketAllocateEx2() + 0xa8 bytes
    sqlncli10.dll!Np::ReadSync() + 0x7e bytes
    sqlncli10.dll!Ssl::HandshakeReadToken() - 0x1b bytes
    user32.dll!InternalDialogBox() + 0x132 bytes
    user32.dll!DialogBoxIndirectParamAorW() + 0x56 bytes
    user32.dll!DialogBoxParamW() + 0x85 bytes
    sqlncli10.dll!SQLDriverConnectW() + 0x34f23 bytes
    odbc32.dll!SQLInternalDriverConnectW() + 0x17c bytes
    odbc32.dll!SQLDriverConnectW() + 0xa15b bytes
Am I calling SQLDriverConnect() correctly (see below)? Or is this a bug in the 64-bit version of the ODBC driver?
In the 32-bit version, everything works fine.
Here is a test program:
int _tmain(int argc, _TCHAR* argv[])
SQLHENV hEnv = NULL;
SQLHDBC hDbc = NULL;
SQLRETURN ret = SQLAllocHandle(SQL_HANDLE_ENV, SQL_NULL_HANDLE, &hEnv);
assert(ret == SQL_SUCCESS || ret == SQL_SUCCESS_WITH_INFO);
ret = SQLSetEnvAttr(hEnv, SQL_ATTR_ODBC_VERSION, (SQLPOINTER) SQL_OV_ODBC3, 0);
if (ret != SQL_SUCCESS && ret != SQL_SUCCESS_WITH_INFO)
fprintf(stderr, "SQLSetEnvAttr failed\r\n");
return EXIT_FAILURE;
ret = SQLAllocHandle(SQL_HANDLE_DBC, hEnv, &hDbc);
assert(ret == SQL_SUCCESS || ret == SQL_SUCCESS_WITH_INFO);
SQLTCHAR szConnection[2048];
SQLSMALLINT cbChars;
ret = SQLDriverConnect(hDbc, ::GetDesktopWindow(), (SQLTCHAR*) _T(""), SQL_NTS,
szConnection, _countof(szConnection)-1, &cbChars, SQL_DRIVER_PROMPT);
if (ret != SQL_SUCCESS && ret != SQL_SUCCESS_WITH_INFO && ret != SQL_NO_DATA)
fprintf(stderr, "SQLDriverConnect failed\r\n");
return EXIT_FAILURE;
else
fprintf(stdout, "Success\r\n");
return 0;
The stdafx.h contains the following includes:
#include "targetver.h"
#include <stdio.h>
#include <tchar.h>
#include <Windows.h>
#include <sql.h>
#include <sqlext.h>
#include <assert.h>
Steps to reproduce the crash: compile program with Visual Studio 2010 as 64-bit console application; run it and select a 64-bit SQL Server DSN.
If the crash does not occur, try using the "AllocationPreference" registry entry set to 0x100000 (see https://msdn.microsoft.com/en-us/library/windows/hardware/Dn613975%28v=vs.85%29.aspx for details); don't forget to reboot Windows. This registry
helps to find 64-bit portability issues.

Hi T.holt,
Personally, I don’t believe SQL 2008 R2 with ADMT 3.2 is supported. From the guidelines of install the Active Directory Migration Tool (ADMT), ADMT v3.2 requires a preconfigured instance of SQL Server for its underlying data store. We
should use SQL Server Express and install ADMT v3.2 on a member server. ADMT installation enforces the following service pack requirements:
• SQL Server 2005 Express must be installed with Service Pack 3 (SP3) or later.
• SQL Server 2008 Express must be installed with Service Pack 1 (SP1) or later.
If you use full versions of SQL Server 2005 or SQL Server 2008. In this case, you need to install and run the ADMT console on a remote computer, and you can run multiple ADMT consoles on different remote computers. If
you use a full version of SQL Server, ADMT installation does not enforce any service pack requirements.
For more information about installing ADMT in the target domain, you can review the following article.http://technet.microsoft.com/en-us/library/cc974370(v=ws.10).aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

DeadLocks on Query Notifications with SQL Server 2008 SP3

Hello,
according to this article https://support.microsoft.com/kb/975090 the issue with deadlocks on query notifications should be fixed with SQL Server 2008 SP3 (10.0.5500.0). But we still get deadlocks in the following manner:
<resource-list>
<keylock hobtid="72057598393909248" dbid="5" objectname="MyDB.sys.query_notification_1411013420" indexname="cidx" id="lock1731c1f00" mode="RangeX-X" associatedObjectId="72057598393909248">
<owner-list>
<owner id="process573dc8" mode="RangeX-X"/>
</owner-list>
<waiter-list>
<waiter id="process58ddc8" mode="RangeS-U" requestType="wait"/>
</waiter-list>
</keylock>
<keylock hobtid="72057598372872192" dbid="5" objectname="MyDB.sys.query_notification_253437289" indexname="cidx" id="lock800c8780" mode="RangeS-U" associatedObjectId="72057598372872192">
<owner-list>
<owner id="process58ddc8" mode="RangeS-U"/>
</owner-list>
<waiter-list>
<waiter id="process573dc8" mode="RangeS-U" requestType="wait"/>
</waiter-list>
</keylock>
</resource-list>
Is there any need to install another fix?
Thanks in Advance!

Hello,
SQL Server 2008 SP4 and all cumulative updates of SP3 do not have fixes related to deadlocks.
Maybe the following workarounds and solutions can help in your scenario.
http://stackoverflow.com/questions/3707137/understanding-deadlocks-with-sql-server-query-notifications
Deadlock Prevention. In case you need to lock multiple conversation groups in a transaction, you need to take the same order to lock the different conversation groups in all transactions, otherwise you will have a deadlock issues.
Source:
http://blogs.msdn.com/b/kangmo/archive/2008/12/17/a-brief-guide-on-sql-server-service-broker.aspx
Try to may transactions more simple and shorter.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Add does not run with sql server 2008

Hi all,
My add on in the development environment does not run with SQL SERVER 2008. It ran well with SQL Server 2005 and sap b1 2207 B.
On executing the project file system throws an error "YOU ARE NOT CONNECTED TO THE COMPANY"
we are trying this scenario on a test machine where SAP B1 2007B with temporary license for one month and SQL server 2008
is installed.
Help needed.
Thanking you
Pradnya

Hi Use this
Dim i as integer
i=oCompany.Connect()
if i<> 0 Then
msgbox(ocompany.GetLastErrorDescription ())
end if
the you will get the error description also use try catch wherever necessary
Alternatively you can use
Dim SboGuiApi As SAPbouiCOM.SboGuiApi
Dim sConnectionString As String
Set SboGuiApi = New SAPbouiCOM.SboGuiApi
sConnectionString = Command
SboGuiApi.Connect sConnectionString
Set SBO_Application = SboGuiApi.GetApplication()
Set ocompany = New SAPbobsCOM.Company 'initialate DI company object
ocompany = SBO_Application.Company.GetDICompany
HTH,
Atul

I cannot debug with SQL server 2008 SSMS asks for Firewall permission?

hi friends,
I run SQL server 2008 R2 developer edition on windows 8 basic edition. SQL server is installed in my local machine. when I tried to debug a sql script it asked the firewall permission as show on image
when googled I found this
Article from MSDN with fix tool but it cannot installed on my Windows 8 OS, is there way to fix it without giving any unauthorized access to my system?
thanks
I use Visual studio 2012 Ultimate and SQL server 2008 developer edition!

Hi,
The hotfix you provide applies for Windows Server 2008.
The windows firewall on this machine is currently blocking remote debugging.
According the message, the following ports need to be enabled for remote debugging. Use the procedure that is described in the section
Configuring a Port in Windows Firewall to enable the following ports through Windows Firewall:
Ports
Protocol
135
TCP
Required
500, 4500
UDP
Required if your domain policy requires network communication to be performed through IPSec.
See the below article for more information:
How to: Enable Transact-SQL Debugging
http://msdn.microsoft.com/en-us/library/vstudio/s0fk6z6e(v=vs.100).aspx
Thanks.
Tracy Cai
TechNet Community Support

Will Report Builder 2012 Work with SQL Server 2008???

Similar Messages

Maybe you are looking for