Print NOT working in SQL Server 2008

Hi Experts,
I am trying to debug my stored procedure with print statements but I dont see any print statements at the end of the execution of the code.
I even tried for the simplest code as below -
ALTER PROCEDURE [dbo].[test]
AS
BEGIN
print 'abdbd'
END
But still no luck. Can anybody let me know the issue with it?
Thanks a ton!
Prabhakar

So where are you looking?
And you did execute the procedure, didn't you?
I may help if you post some screenshots.
Erland Sommarskog, SQL Server MVP, [email protected]

Similar Messages

  • 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

  • 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

  • Why is the LookUp object in the Flow Task of my SSIS package going red (and not working) ? Sql Server 2008 R2

    I have been working with the Sql Server 2008 R2 SSIS Tutorial at
    https://msdn.microsoft.com/en-us/library/ms170419(v=sql.105).aspx
    --specifically -- Lesson 1.  I have been having some problems with this lesson where the source data from the samples download doesn’t exactly match the data described in the tutorial, and the tables in the tutorial are different from what
    is contained in AdventureWorksDW (tutorial refers to DimTime – AdventureWorksDW contains DimDate and no DimTime).  
    So, after futzing in BI with this tutorial  so that I can at least get it to run in Debug – it errors out on the 2<sup>nd</sup> LookUp object.
    Rather than looking for a fix to the problem(s) that I am having between the tutorial and the stuff I downloaded in the samples --
     I want “Adapt” the tutorial so I can use the stuff I downloaded and hopefully learn how to use SSIS with the elements (source data and tables) that are present on my workstation. 
    Here is a description of what is going on for me – which I really don’t understand what is going on in BI – based on the images below – like what columns (from what tables) are they associating to in the OleDB Destination? 
    Note:  the sql in the LookUps here is the sql that I copied from the tutorial. 
    I probably need to modify these sql statements – so -- the help I am requesting is to make the required modifications/changes
     so that I can adapt this tutorial with the stuff that’s on my workstation.
    I downloaded the samples and the AdventureWorksDW mdf for Sql Server 2008 R2. 
    It turns out that in the tutorial it wants me to select a DimTime table, but the version of the AdventureWorksDW db does not contain a DimTime table. 
    Instead, it contains a DimDate table.  So I tried adapting DimDate for the tutorial. 
    Additionally, the sample data file -- SampleCurrencyData.txt -- has slightly different data types than the types described in the tutorial, so I selected data types for the columns in the datasource text file that would work in BI would to
    connect column from source data file to the table.
    After finishing all the steps for Lesson 1 -- when I tried debugging the package – and it error'd out on  the 2<sup>nd</sup> Lookup object whichwent red.
      I edited the lookups and the sample Ole DB Destination to "ignore on fail” and I did all
     green but the FactCurrencyRate table is not being populated -- as described in the tutorial, so I reset the on error back to default (Fail on error option).   And based on this tutorial -- I believe FactCurrencyRate
    table is the table which is supposed to be populated with the data from SampleCurrencyData.txt?
    In the sample data file that downloaded with all the samples  I removed all the data from the text file except for 6 rows, so instead of the original 1100 or so rows, I have only 6 rows of data in the source data file (just to keep things
    simple for debugging for now).  I did not modify the data itself. 
    Here is what the (raw) data contained in SampleCurrencyData.txt looks like (from the samples that I downloaded from codeplex) – it’s supposed to be 4 columns of data – float, nvarchar, datetime, float:
    0.281690141       USD      
    6/26/2004 0:00  0.281713948
    0.281690141       USD      
    6/27/2004 0:00  0.281642539
    0.281690141       USD      
    6/28/2004 0:00  0.281761573
    0.283286119       USD      
    6/29/2004 0:00  0.283221933
    0.283286119       USD      
    6/30/2004 0:00  0.283358363
    0.281690141       USD      
    7/1/2004 0:00     0.281682206
    Below are images of my BI Layout for Lesson 1 from this tutorial -- the FlatFile and configurations for On Fail Error, A Flow task, the 2 LookUps (CurrencyKey and DataKey), the OleDB Destination configuration, the Design view of the associated tables and
    the Debug Run of Lesson 1, and the following error messages. My goal is to figure out what is going on in BI for this tutorial.
    Error: 0xC020901E at Extract Sample Currency Data, Lookup Datakey [51]: Row yielded no match during lookup.
    Error: 0xC0209029 at Extract Sample Currency Data, Lookup Datakey [51]: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. 
    The "component "Lookup Datakey" (51)" failed because error code 0xC020901E occurred, and the error row disposition on "output "Lookup Match Output" (53)" specifies failure on error. An error occurred on the specified
    object of the specified component.  There may be error messages posted before this with more information about the failure.
    Error: 0xC0047022 at Extract Sample Currency Data, SSIS.Pipeline: SSIS Error Code DTS_E_PROCESSINPUTFAILED. 
    The ProcessInput method on component "Lookup Datakey" (51) failed with error code 0xC0209029 while processing input "Lookup Input" (52). The identified component returned an error from the ProcessInput method. The error is specific
    to the component, but the error is fatal and will cause the Data Flow task to stop running. 
    There may be error messages posted before this with more information about the failure.
    --this is the flat file
     -- SampleCurrencyData.txt (which only contains 6 data rows for my purposes)
    --and here is where I assign the data types for the colums of -- SampleCurrencyData.txt
    This is the first LookUp Object -- LookUp Currency Key – The DB contains DimCurrency table. 
    I copied the sql from the tutorial here.
    I actually have a DimCurrency table in my copy of AdventureWorksDW. 
    Here’s the design view of DimCurrency and a sample of the data contained in DimCurrency and the On Fail configuration
    I actually have a DimCurrency table in my copy of AdventureWorksDW. 
    Here’s the design view of DimCurrency and a sample of the data contained in DimCurrency and the On Fail configuration
    --Here is what the data looks like in the DimCurrency table
    --2<sup>nd</sup> LookUp object  -- LookUp Data Key – this is the LookUp
     where BI errors out on Debug
    --it appears this lookup is referencing the DimDate table – which I DO have in the DB.
    --I can’t find the following sql in the tutorial, so I suppose BI added the sql (did it?)
    --Here's how I configured for On Error
    --Here is DimDate table in Design view
    --Here is a sample of the original data contained in DimData
    OleDB Destination
    --Here is where I get lost a bit – what is going on in the destination here?
    --Here's my On Error configuraino
    --and here is the FactCurrencyRate table
    --and here is a sample of the data contained in FactCurrencyRate
    Rich P

    Thank you for your reply.  I changed the error handling as you suggested on the 2nd lookup to redirect to unmatched rows.  Now I get all greet.  I don't have the conditional split as in your diagram.  But also, nothing appears to have
    happened in the DB.  Aren't the rows in my text file supposed to be added to the FactCurrencyRate table?
    How do I get a conditional split?
    Rich P
    OK, sorry I forgot to reply you back.
    Conditional Split was just dummy task. Ignore it.
    Manipulate the data in such way that you get matching records.
    Inside Source, for first 2 rows I put the dates which are available in DimDate.
    1.00010001,ARS,7/1/2005 0:00,0.99960016
    1.00010001,ARS,2/5/2006 0:00,1.001001001
    1.00020004,ARS,9/5/2001 0:00,0.99990001
    1.00020004,ARS,9/6/2001 0:00,1.00040016
    1.00050025,ARS,9/7/2001 0:00,0.99990001
    1.00050025,ARS,9/8/2001 0:00,1.001001001
    Then in OLE DB Destination, I loaded the rows to TestFactTable.
    (Now, you don't even need NO MATCH OUTPUT as there are matching records here)
    Cheers,
    Vaibhav Chaudhari
    [MCTS],
    [MCP]

  • SQL Server Usage Summary page, the count of user/device: does not show for SQL Server 2008

    Does MAP tool capture User Summary  (count of users, their details) for SQL Server 2008? 
    At my end, its working for SQL Server 2012 but not showing User Summary for SQL Server 2008..
    Does the User Summary only works for SQL Server 2008 Enterprise edition as one of the thread points out?

    This is from the
    Wiki article:
    SQL Server 2008 Enterprise and Datacenter Editions introduced audit event configuration for Windows security logging, which enabled SQL Server 2008 to log logon events to the Windows Security log. The table below shows which versions and editions have the Audit
    feature that is needed to record the logon events. MAP cannot obtain user and device access information for any other editions or any older versions of SQL Server.
    Datacenter
    Enterprise
    Business Intelligence
    Standard
    Workgroup
    Web
    Express
    SQL Server 2008
    N/A
    Yes
    N/A
    No
    No
    No
    No
    SQL Server 2008 R2
    Yes
    Yes
    N/A
    No
    No
    No
    No
    SQL Server 2012
    N/A
    Yes
    Yes
    Yes
    N/A
    Yes
    Yes
    Please remember to click "Mark as Answer" on the post that helps you, and to click
    "Unmark as Answer" if a marked post does not actually answer your question. Please
    VOTE as HELPFUL if the post helps you. This can be beneficial to other community members reading the thread.

  • 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

  • Web Service Client(Console App) not working on Windows Server 2008 R2 Standard Edition

    I am trying to consume an ASMX Web Service in a console app, its working fine in Windows 7,Windows Server 2012 Standard,Windows Server 2008 R2 DataCenter,Windows Server 2008 R2 Enterprise, But its not working in Windows Server 2008 R2 Standard Edition which
    is the deployment server.
    I tried consuming the ASMX web service using Web Reference and Service Reference as well but its not helping. Its throwing up the following error,
    Message:There is an error in XML document (1, 331491).
    Inner Exception : System.Xml.XmlException: '.', hexadecimal value 0x00, is an invalid character. Line 1, position 331491.
    The scenario is that i call the web service and it returns me an XML i am not able to receive the XML on Windows Server 2008 R2 Standard Edition.
    Please provide suggestions on this I need to resolve this ASAP.

    Hi,
    This question is better asked here:
    http://social.msdn.microsoft.com/Forums/en-US/home?forum=asmxandxml
    Experts here are more familiar about it and they can give you more efficient suggestion.
    Thank you.

  • 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

  • EXEC SP_EXECUTESQL not working in sql server 2014

    EXEC SP_EXECUTESQL not working in sql server 2014

    EXEC SP_EXECUTESQL not working in sql server 2014
    Hi Amar,
    What's the error when executing this stored procedure?
    I have tested it on my local environment, we can run this SP without any problems.
    Please provide us more information, so that we can make further analysis.
    Regards,
    Charlie Liao
    TechNet Community Support

  • Addon not working on Windows Server 2008 OS

    Dear Friends,
    I have developed an addon in XP and its working fine with XP operating system but it is not working on Windows Server 2008 Standard. Error is "An Attempt was made to load a program with an incorrect format.(Exception from HRESULT: 0x8007000B)".
    Regards,
    Mahesh.
    Edited by: mahesh A on Sep 19, 2009 9:26 AM

    Hi,
    Since only Windows 2008 SBS is supported with SAP Business One and that Server is available for 64bit Hardware as defined by Microsoft, I guess you should look into that direction.
    Regards
    Mario

  • File- Print not working from SQL Developer 1.2.1 Build MAIN-32.13

    File->Print not working from SQL Developer 1.2.1 Build MAIN-32.13.
    I downloaded sqldeveloper-1.2.1.3213.ZIP and extract to a local directory. From the extracted directory I ran ..\sqldeveloper\sqldeveloper.exe from Windows XP sp2. The program itself seems to run just fine but File-Print doesn't do anything. In Help-About, Java Platform is reported as 1.5.0_06 and Oracle IDE is 1.2.1.3213. I'm not sure where to look for what is causing the problem.
    Thanks

    I hadn't tried CTRL-P before but I did today. On the first attempt, I saw a small jump in the memory usage for sqldeveloper.exe as reported in Windows Task Manager. Otherwise, there was no change. A second CTRL-P in the same session produced a further bump but subsequent attempts in the same session produced no further change in CPU or Memory Usage.
    Using Task Manager to monitor this further, I tried File->Print again and saw that sqldeveloper would periodically climb to 1 or 2 percent CPU and consume a little more memory. After a minute or so, though, all activity stops again.
    I do not get a print dialog box from SQLDeveloper using either CTRL-P or File->Print

  • Group Chat feature in Office Communications Server 2007 R2 does not work in Windows Server 2008 R2 domains

       Hello to all, there are two confliting articles about this topic:
       1-
    http://technet.microsoft.com/en-us/library/upgrade-domain-controllers-to-windows-server-2008-r2(v=ws.10).aspx#BKMK_Whatsnew : this one says that it does not work "The Group Chat feature in Office Communications Server 2007 R2 does not work in Windows
    Server 2008 R2 domains". This article was updated in 2013.
       2-
    http://technet.microsoft.com/en-us/library/ee692314(office.13).aspx: this other article says that it will function "Office Communications Server 2007 R2 Group Chat will function in a Windows Server 2008 R2 forest". This article was updated in
    2010 and was refered by the first one.
       What is the correct support position for Group Chat feature in Office Communications Server 2007 R2 and Windows Server 2008 R2 domains?
       Regards, EEOC.

    Hi,
    I notice the following sentence in the link below “Office Communications Server 2007 R2, Group Chat will not function in a Windows Server 2008 R2 forest or when Group Chat member servers are joined to a Windows Server 2008 R2 domain.
    We know of an issue with changes in Windows 2008 R2 that requires a Group Chat Client and Group Chat Admin Tools hotfix. The Group Chat Client and Group Chat Admin Tools hotfixes are currently scheduled for mid-April 2010.”
    http://blogs.technet.com/b/nexthop/archive/2010/11/06/supportability-for-office-communications-server-2007-r2-and-windows-server-2008-r2.aspx
    So in my opinion, if you update to the latest version of Windows Server 2008 R2, OCS Server 2007 R2 and Group Chat Client, Group Chat Admin Tools to the latest version, it should work.
    However, the best method for you is make a lab to test the problem firstly.
    Best Regards,
    Eason Huang
    Eason Huang
    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

  • SSIS Package developed in SQL Server 2008 R2 Using BIDS 2008 is not working in SQL Server 2012

    I am working in a Product based company.
    We have given a Pre-requisites to our customers like SQL Server version should be 2008 or later.
    I have developed and deployed my SSIS package in SQL Server 2008 R2 with BIDS 2008.
    I have used "Script Component" in my package.
    We will take only DTSX package file to the customer places and run using SQL Agent Job daily. 
    Who are all(Customer Environments) using SQL 2008 or R2 my package is running fine.
    Who are all(Customer Environments) using SQL 2012, I am facing the below issue 
    The component metadata for “Script Component, clsid {874F7595-FB5F-4OFF-9BAF-FBFF825OE3EF}” could not be upgraded to the newer version of the component. The PerformUpgrade method failed.
    Still the same package is running fine for some of the customers having SQL 2012.
    I am getting the above error only for few customers.
    Can someone please guide me how to proceed on this. Is there any solution to go without upgrading the package to SQL 2012. Because we need to maintain only one package for all customers

    Hi Katherine,
    I am just using the script component only for generating Identity column purpose. I will get the maximum count from the table and using this count value as Input (JurisCount in my below code) for script component and increment the counter for new records.
    Finally I am mapping the Script component output value (JurisKey in my below code) to Key column of the table. That's all I am doing with Script Component.
    Here is my Simple .net code
    /* Microsoft SQL Server Integration Services Script Component
    *  Write scripts using Microsoft Visual C# 2008.
    *  ScriptMain is the entry point class of the script.*/
    using System;
    using System.Data;
    using Microsoft.SqlServer.Dts.Pipeline.Wrapper;
    using Microsoft.SqlServer.Dts.Runtime.Wrapper;
    [Microsoft.SqlServer.Dts.Pipeline.SSISScriptComponentEntryPointAttribute]
    public class ScriptMain : UserComponent
        public override void PreExecute()
            base.PreExecute();
              Add your code here for preprocessing or remove if not needed
        public override void PostExecute()
            base.PostExecute();
              Add your code here for postprocessing or remove if not needed
              You can set read/write variables here, for example:
              Variables.MyIntVar = 100
        int counter = 0;
        public override void Input0_ProcessInputRow(Input0Buffer Row)
            if (counter == 0)
                counter = Convert.ToInt32(Row.JurisCount);
            Row.JurisKey = counter;
            counter = counter + 1;
    PAVAN MSBI

  • Windows 8 and IE 10 crashed after printing from Report Manager SQL server 2008 / 2008 R2

    We have a problem with Windows 8 in combination with IE 10 and printing reports.
    When we print a report from the Report Manager 'http://<servername>/reports' the browser crashed after a print.
    Sometimes before printing and somthimes after printing or when you close the browser.
    Al other operating systems like XP, Vista, Windows 7 with different IE versions have no problem.
    I tried the report manager from SQL Server 2008 and SQL Server 2008 R2.
    The same error occured when printing from our Internet application and the reportviewer.
    (ASP application written in Visual Studio 2010 and reportviewer version 10.)
    The event log shows two different messages.
    Faulting application name: IEXPLORE.EXE, version: 10.0.9200.16453, time stamp: 0x509b0dfb
    Faulting module name: ntdll.dll, version: 6.2.9200.16420, time stamp: 0x505aaa82
    Exception code: 0xc0000005
    Fault offset: 0x00061252
    Faulting process id: 0x780
    Faulting application start time: 0x01ce03a294f7d1d5
    Faulting application path: C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    Report Id: d4a72486-6f96-11e2-be6e-10604b6a74ed
    Faulting package full name:
    Faulting package-relative application ID:
    Faulting application name: IEXPLORE.EXE, version: 10.0.9200.16384, time stamp: 0x50107ee0
    Faulting module name: rsclientprint.dll, version: 2009.100.1600.1, time stamp: 0x4bb67a74
    Exception code: 0xc0000005
    Fault offset: 0x00017e7a
    Faulting process id: 0x9c8
    Faulting application start time: 0x01ce02f35c70ab85
    Faulting application path: C:\Program Files (x86)\Internet Explorer\IEXPLORE.EXE
    Faulting module path: C:\Windows\Downloaded Program Files\rsclientprint.dll
    Report Id: a13fccc6-6ee6-11e2-be67-10604b6a74ed
    Faulting package full name:
    Faulting package-relative application ID:
    Is there a fix for this problem?

    Dear Mike Yin,
    Thank you for your response. Your answer was the
    reason for finding the real problem.
    In december 2010 a SQL Server 2008 fix was the cause. I don't remember exactly the problem, but we changed the RSCLIENTPrint-x86.cab file. But instead to use the version of SQL Server 2008 we used the version of SQL Server 2008
    R2 (10.50.1600.1). This worked until
    Windows 8 (Internet Explorer crashed when printing).
    We fixed this problem by using the RSClientPrint-x86.cab file from SQL server 2008 (10.0.5500.0).
    But we now get the known problem that the
    activeX always must be installed again. 
    The reason for this is that the version of
    the SQL Server (10.0.5512.0) 
    and the rsclientprint.dll (10.0.5500.0) is different. SQL Server is newer (caused
    by a security patch (KB2716436)).
    Do you know when this problem will be resolved
    by Microsoft?
    Work arrounds
    I've also tried to install the RSClientprint.dll
    every time automatically (without user interaction).
    But this will be delayed the printing for more
    than 4 seconds. This
    is very annoying.
    Another workaround is to generate a PDF and print the PDF. But this is also
    a lot slower.
    Uninstall the security patch. but I don't know the security risk.

Maybe you are looking for