SQL Server 2008 Reporting Project - Invoke/Consume Web Service and Return Dataset in C# Code-Behind
Hello,
I have a Visual Studio 2010 C# class with a method that invokes/consumes a web service and returns an XML dataset. I am traversing through the parent/child nodes and parsing out the data then inserting it into a SQL Server 2008 R2 table for a join within
another stored procedure.
Instead of using a 3rd party API to generate the PDF for this data, I am creating an SSRS report. The formatting will be easier and I can do a RenderFormat directly to PDF.
Can I expect to be able to transfer the code-behind method to this report and have it be able to work with the web service the same way? It is a SOAP-based web service returning parent nodes and two levels of nested child nodes.
I have also been researching the approach of calling the web service in the same stored procedure that is currently querying the physical tables (which is used to populate a gridview and PDF) but it looks like it may only be possible with a CLR stored procedure.
Is it possible to implement a CLR stored procedure within an SSRS report?
Hope this makes sense. Any help, suggestion or point in the right direction would be greatly appreciated.
Thanks,
Buster
Hi Buster,
SSRS supports web service data source, we can call the SOAP-based web service in SSRS report directly. Then, we can use custom code in SSRS to parse the XML data. However, we won’t be able to join another data in SQL Server database.
Reference:http://technet.microsoft.com/en-us/library/aa964129(v=sql.90).aspx#repservxmlds_topic3
We cannot implement a CLR stored procedure within an SSRS report directly. In order to execute the CLR store procedure in a SSRS report, we have to execute it as text using the following code:
Exec <stored procedure name>
Reference:
http://dotnetslackers.com/Community/blogs/bmains/archive/2009/01/15/executing-a-clr-stored-procedure-in-reporting-services.aspx
Hope this helps.
Regards,
Alisa Tang
Alisa Tang
TechNet Community Support
Similar Messages
-
Xcelsius and SQL Server 2008 Reporting Services
I am totally and utterly p1$$3d off and surely I cannot be the only person to be using a similar setup i.e. Xcelsius along with SQL Server 2008 Reporting Services.
I have installed and tried to get working the XRS gateway and get connectivity to Reporting Services so that SSRS reports can be utilized with Xcelsius... BUT NO...
when trying to configure and use the GetReports command from the xrs.asmx web file I get an error, namely:
<?xml version="1.0" encoding="utf-8" ?>
<ROOT>
<Message>Client found response content type of '', but expected 'text/xml'. The request failed with an empty response.</Message>
<StackTrace>at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Microsoft.ReportingServices.ReportingService.ListChildren(String Item, Boolean Recursive) at Microsoft.ReportingServices.CatalogManager.CreateXmlNode(XmlDocument Doc, CatalogItem Item, XmlNode ParentNode) at Microsoft.ReportingServices.CatalogManager.SerializeToXML() at Infommersion.XRS.Service.GetReports()</StackTrace>
</ROOT>
Only to be told when I logged a support call, that "SQL Server 2008 Reporting Services is NOT SUPPORTED"
please go back to using 2005!!!
I find this totally and utterly unbelievable, it's not even as if its a new product... and surely i am not the only person using Xcelsius and wanting to utilise 2008Reporting Services Reports...
has anyone come across this error or understand what is not occuring to get this message and how to resolve?
yours eternally grateful if anyone can shed light on the matter
deanIndeed, got the XRS gateway working but it isn't able to connect to RS2008.
I guess the cause is that for RS2005 the web service connection point is the file ReportService.asmx. In RS 2008 this file is renamed to ReportService2005.asmx and therefor the XRS gateway cannot connect to it.
A fix pack seems to be in the making:
[1400035 - Xcelsius 2008 with MS Reporting Services 2008 Supportability |http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_erq/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333433303330333033333335%7D.do] -
"SQL Server 2008 Reporting Services does not support map report items"
Hi,
I am trying some new feature that are introduced in SQL Server 2008 R2 version. While I try to use "Map" control within it, it threw the following error:-
"Error 1 The map, Map1, was removed from the report. SQL Server 2008 Reporting Services does not support map report items. "
-Also, similar kind of error I am getting for "Indicator" control.Hi Tej,
I think you get this error message when you are deploying a report to report server using BIDS, correct? If not, please provide more details on your scenario :-)
If I guessed correctly, then this message is a result of trying to deploy a map report (a SSRS 2008 R2 feature) to a non-R2 2008 report server. When deploying a report of RDL2010 format to a non-R2 report server, BIDS will downgrade the file to RDL2008 format, so that the non-R2 report server can process it. Any report elements using features not supported in RDL2008 will be dropped during this downgrade process.
BIDS gets the server version from a report project property called TargetServerVersion:
http://technet.microsoft.com/en-us/library/ee635898(SQL.105).aspx
If your report server is indeed the 2008 R2 version, then the TargetServerVersion property should be set to "SQL Server 2008 R2 Reporting Services." The project property page also has a "Auto Detect..." option if you are uncertain about the version of your report server.
Hope this helps!
Cheers,
LawrenceThis posting is provided "AS IS" with no warranties, and confers no rights. -
Invoking a web service that returns binary
Hi,
Is it possible to invoke a web service that returns a binary object?
Its similar the following example but I need to return a binary object :
declare
v_url:='http://www.somesite.com/function_name?invoke=placeOrder&par1=val1'
v_output varchar2(4000);
begin
select utl_http.request(v_url)
into v_output from dual;
end;
Thanks in advanceNo "advantage" as there are two very different tools.
UTL_HTTP is basically an Oracle PL/SQL web browser. It uses the HTTP application protocol. It is just like your ordinary browser (IE, Firefox, Opera), but as it is server-side and display-less, it comes without a rendering engine.
UTL_DBWS is to interact with web services using the SOAP application protocol. -
Cannot Install Sql Server 2008, Gives The Error "Database Engine Services Failed"
I cannot install Sql Server 2008 R2 on Windows 8. Tried many times but failed because it gives the error "Database
Engine Services Failed". Sql files cannot be corrupted because i can install the same setup on Windows 7 and i can connect to databases.
I tried all the things below;
* I'm uninstalling everything related with Sql Server from Control Panel/Programs And Features.
* I'm deleting all the keys related with Sql Server from Regedit.
* Later i'm restarting windows, and trying to install again. But during the install it gives the error "Database
Engine Services Failed", install is finishing but when i opened the Management Studio i cannot connect to Database Engine with Sa naturally.
* My firewall is already closed. And i have not any antivirus software.
* I gave the permission for port 1433 on firewall.
Please help me. Why i always take "Database Engine Services Failed" error? I will get crazy cause of that for many days.Here's the ERRORLOG file which i found under the folder;
Microsoft SQL Server/MSSQL10_50.MSSQLSERVER/MSSQL/Log.
2014-09-27 03:39:40.15 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
2014-09-27 03:39:40.15 Server (c) Microsoft Corporation.
2014-09-27 03:39:40.15 Server All rights reserved.
2014-09-27 03:39:40.15 Server Server process ID is 5768.
2014-09-27 03:39:40.15 Server System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX'.
2014-09-27 03:39:40.15 Server Authentication mode is MIXED.
2014-09-27 03:39:40.15 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2014-09-27 03:39:40.15 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2014-09-27 03:39:40.15 Server Command Line Startup Parameters:
-m SqlSetup
-f
-Q
-q Turkish_CI_AS
-T 4022
-T 4010
-T 3659
-T 3610
2014-09-27 03:39:40.18 Server Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically. After
the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
2014-09-27 03:39:40.18 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-09-27 03:39:40.18 Server Detected 4 CPUs. This is an informational message; no user action is required.
2014-09-27 03:39:40.31 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2014-09-27 03:39:40.32 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2014-09-27 03:39:40.43 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2014-09-27 03:39:40.45 Server Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action
is required.
2014-09-27 03:39:40.45 spid7s Warning ******************
2014-09-27 03:39:40.45 spid7s SQL Server started in single-user mode. This an informational message only. No user action is required.
2014-09-27 03:39:40.46 spid7s Starting up database 'master'.
2014-09-27 03:39:40.52 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2014-09-27 03:39:40.58 spid7s SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
2014-09-27 03:39:40.59 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:40.59 spid7s Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
2014-09-27 03:39:40.59 spid7s Starting up database 'mssqlsystemresource'.
2014-09-27 03:39:40.61 spid7s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2014-09-27 03:39:40.94 spid7s Password policy update was successful.
2014-09-27 03:39:40.94 spid8s Starting up database 'model'.
2014-09-27 03:39:40.95 spid7s Server name is 'CAGATAY'. This is an informational message only. No user action is required.
2014-09-27 03:39:41.21 spid8s Clearing tempdb database.
2014-09-27 03:39:41.21 spid10s A new instance of the full-text filter daemon host process has been successfully started.
2014-09-27 03:39:41.24 Server A self-generated certificate was successfully loaded for encryption.
2014-09-27 03:39:41.24 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2014-09-27 03:39:41.24 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag
7806. This is an informational message only. No user action is required.
2014-09-27 03:39:41.28 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2014-09-27 03:39:41.28 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014-09-27 03:39:41.70 spid8s Starting up database 'tempdb'.
2014-09-27 03:39:41.86 spid7s Warning ******************
2014-09-27 03:39:41.86 spid7s Attempting to change default collation to Turkish_CI_AS.
2014-09-27 03:39:41.92 spid7s index restored for master.syspriorities.
2014-09-27 03:39:41.95 spid7s index restored for master.sysbrickfiles.
2014-09-27 03:39:41.96 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:41.96 spid7s index restored for master.sysowners.
2014-09-27 03:39:42.13 spid7s index restored for master.sysdbreg.
2014-09-27 03:39:42.16 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.16 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.16 spid7s index restored for master.sysschobjs.
2014-09-27 03:39:42.17 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.17 spid7s index restored for master.syscolpars.
2014-09-27 03:39:42.17 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.sysxlgns.
2014-09-27 03:39:42.18 spid7s index restored for master.sysxsrvs.
2014-09-27 03:39:42.18 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.sysnsobjs.
2014-09-27 03:39:42.18 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.syscerts.
2014-09-27 03:39:42.19 spid7s index restored for master.sysrmtlgns.
2014-09-27 03:39:42.19 spid7s index restored for master.sysxprops.
2014-09-27 03:39:42.19 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.19 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.31 spid7s index restored for master.sysscalartypes.
2014-09-27 03:39:42.31 spid7s index restored for master.sysidxstats.
2014-09-27 03:39:42.31 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysendpts.
2014-09-27 03:39:42.32 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysclsobjs.
2014-09-27 03:39:42.32 spid7s index restored for master.sysremsvcbinds.
2014-09-27 03:39:42.32 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysrts.
2014-09-27 03:39:42.33 spid7s index restored for master.sysasymkeys.
2014-09-27 03:39:42.33 spid7s index restored for master.syssqlguides.
2014-09-27 03:39:42.44 spid7s index restored for master.syssoftobjrefs.
2014-09-27 03:39:42.47 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.48 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.49 spid7s index restored for master.spt_values.
2014-09-27 03:39:42.49 spid7s index restored for master.MSreplication_options.
2014-09-27 03:39:42.56 spid7s index restored for tempdb.syspriorities.
2014-09-27 03:39:42.56 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s index restored for tempdb.sysowners.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s index restored for tempdb.sysschobjs.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.59 spid7s index restored for tempdb.syscolpars.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysnsobjs.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.syscerts.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysxprops.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysscalartypes.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysidxstats.
2014-09-27 03:39:42.61 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysclsobjs.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysremsvcbinds.
2014-09-27 03:39:42.61 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysrts.
2014-09-27 03:39:42.62 spid7s index restored for tempdb.sysasymkeys.
2014-09-27 03:39:42.69 spid7s index restored for tempdb.syssqlguides.
2014-09-27 03:39:42.69 spid7s index restored for tempdb.syssoftobjrefs.
2014-09-27 03:39:42.75 spid7s index restored for model.syspriorities.
2014-09-27 03:39:42.75 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.75 spid7s index restored for model.sysowners.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.76 spid7s index restored for model.sysschobjs.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.syscolpars.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.sysnsobjs.
2014-09-27 03:39:43.00 spid7s index restored for model.syscerts.
2014-09-27 03:39:43.00 spid7s index restored for model.sysxprops.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.sysscalartypes.
2014-09-27 03:39:43.00 spid7s index restored for model.sysidxstats.
2014-09-27 03:39:43.01 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.01 spid7s index restored for model.sysclsobjs.
2014-09-27 03:39:43.01 spid7s index restored for model.sysremsvcbinds.
2014-09-27 03:39:43.01 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.01 spid7s index restored for model.sysrts.
2014-09-27 03:39:43.01 spid7s index restored for model.sysasymkeys.
2014-09-27 03:39:43.01 spid7s index restored for model.syssqlguides.
2014-09-27 03:39:43.01 spid7s index restored for model.syssoftobjrefs.
2014-09-27 03:39:43.02 spid7s Starting up database 'msdb'.
2014-09-27 03:39:43.82 spid7s index restored for msdb.syspriorities.
2014-09-27 03:39:43.85 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.93 spid7s index restored for msdb.sysowners.
2014-09-27 03:39:43.99 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.09 spid7s index restored for msdb.sysschobjs.
2014-09-27 03:39:44.12 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.20 spid7s index restored for msdb.syscolpars.
2014-09-27 03:39:44.20 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.20 spid7s index restored for msdb.sysnsobjs.
2014-09-27 03:39:44.20 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.25 spid7s index restored for msdb.syscerts.
2014-09-27 03:39:44.25 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.26 spid7s index restored for msdb.sysxprops.
2014-09-27 03:39:44.26 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.26 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.27 spid7s index restored for msdb.sysscalartypes.
2014-09-27 03:39:44.37 spid7s index restored for msdb.sysidxstats.
2014-09-27 03:39:44.41 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysclsobjs.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysremsvcbinds.
2014-09-27 03:39:44.42 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysrts.
2014-09-27 03:39:44.54 spid7s index restored for msdb.sysasymkeys.
2014-09-27 03:39:44.54 spid7s index restored for msdb.syssqlguides.
2014-09-27 03:39:44.59 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.74 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.85 spid7s index restored for msdb.syssoftobjrefs.
2014-09-27 03:39:44.89 spid7s index restored for msdb.syspolicy_policies_internal.
2014-09-27 03:39:44.90 spid7s index restored for msdb.sysproxies.
2014-09-27 03:39:44.90 spid7s index restored for msdb.syscollector_execution_stats_internal.
2014-09-27 03:39:44.90 spid7s index restored for msdb.syssubsystems.
2014-09-27 03:39:44.91 spid7s index restored for msdb.log_shipping_primary_secondaries.
2014-09-27 03:39:44.91 spid7s index restored for msdb.sysdownloadlist.
2014-09-27 03:39:44.91 spid7s index restored for msdb.log_shipping_monitor_primary.
2014-09-27 03:39:44.92 spid7s index restored for msdb.sysoriginatingservers.
2014-09-27 03:39:44.93 spid7s index restored for msdb.log_shipping_monitor_history_detail.
2014-09-27 03:39:44.95 spid7s index restored for msdb.log_shipping_monitor_error_detail.
2014-09-27 03:39:44.95 spid7s index restored for msdb.log_shipping_secondary.
2014-09-27 03:39:44.97 spid7s index restored for msdb.log_shipping_secondary_databases.
2014-09-27 03:39:45.10 spid7s index restored for msdb.log_shipping_monitor_secondary.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysjobs.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysutility_ucp_mi_file_space_health_internal.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysutility_ucp_mi_database_health_internal.
2014-09-27 03:39:45.10 spid7s index restored for msdb.syscollector_blobs_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_mi_dac_execution_statistics_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysjobsteps.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_ucp_dac_file_space_health_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.logmarkhistory.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_mi_session_statistics_internal.
2014-09-27 03:39:45.12 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.12 spid7s index restored for msdb.sysdtscategories.
2014-09-27 03:39:45.33 spid7s index restored for msdb.syspolicy_target_sets_internal.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysutility_ucp_mi_volume_space_health_internal.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysschedules.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysdac_instances_internal.
2014-09-27 03:39:45.33 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.50 spid7s index restored for msdb.sysssispackages.
2014-09-27 03:39:45.51 spid7s index restored for msdb.sysutility_ucp_computer_cpu_health_internal.
2014-09-27 03:39:45.51 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.52 spid7s index restored for msdb.sysssispackagefolders.
2014-09-27 03:39:45.52 spid7s index restored for msdb.sysdac_history_internal.
2014-09-27 03:39:45.53 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.62 spid7s index restored for msdb.syscategories.
2014-09-27 03:39:45.62 spid7s index restored for msdb.systargetservers.
2014-09-27 03:39:45.62 spid7s index restored for msdb.systargetservergroups.
2014-09-27 03:39:45.62 spid7s index restored for msdb.syspolicy_policy_category_subscriptions_internal.
2014-09-27 03:39:45.62 spid7s index restored for msdb.sysalerts.
2014-09-27 03:39:45.62 spid7s index restored for msdb.sysoperators.
2014-09-27 03:39:45.63 spid7s index restored for msdb.syspolicy_system_health_state_internal.
2014-09-27 03:39:45.63 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.63 spid7s index restored for msdb.syscollector_config_store_internal.
2014-09-27 03:39:45.65 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.65 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.65 spid7s index restored for msdb.sysmanagement_shared_server_groups_internal.
2014-09-27 03:39:45.66 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.66 spid7s index restored for msdb.sysutility_mi_smo_properties_to_collect_internal.
2014-09-27 03:39:45.66 spid7s index restored for msdb.sysmanagement_shared_registered_servers_internal.
2014-09-27 03:39:45.66 spid7s index restored for msdb.syscachedcredentials.
2014-09-27 03:39:45.79 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.79 spid7s index restored for msdb.syscollector_collection_sets_internal.
2014-09-27 03:39:45.79 spid7s index restored for msdb.sysutility_ucp_dac_health_internal.
2014-09-27 03:39:45.80 spid7s index restored for msdb.MSdbms.
2014-09-27 03:39:45.80 spid7s index restored for msdb.MSdbms_datatype.
2014-09-27 03:39:45.80 spid7s index restored for msdb.sysmail_profile.
2014-09-27 03:39:45.80 spid7s index restored for msdb.sysutility_ucp_managed_instances_internal.
2014-09-27 03:39:45.83 spid7s index restored for msdb.syspolicy_management_facets.
2014-09-27 03:39:45.84 spid7s index restored for msdb.sysutility_ucp_mi_health_internal.
2014-09-27 03:39:45.86 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.86 spid7s index restored for msdb.syscollector_collector_types_internal.
2014-09-27 03:39:45.86 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.86 spid7s index restored for msdb.syspolicy_configuration_internal.
2014-09-27 03:39:45.87 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.87 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.87 spid7s index restored for msdb.syspolicy_facet_events.
2014-09-27 03:39:45.87 spid7s index restored for msdb.sysmail_account.
2014-09-27 03:39:45.87 spid7s index restored for msdb.syspolicy_conditions_internal.
2014-09-27 03:39:45.88 spid7s index restored for msdb.sysutility_ucp_health_policies_internal.
2014-09-27 03:39:45.88 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.88 spid7s index restored for msdb.syscollector_collection_items_internal.
2014-09-27 03:39:45.90 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.00 spid7s index restored for msdb.sysmail_servertype.
2014-09-27 03:39:46.00 spid7s index restored for msdb.sysutility_ucp_filegroups_with_policy_violations_internal.
2014-09-27 03:39:46.02 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_policy_check_conditions_internal.
2014-09-27 03:39:46.03 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_configuration_internal.
2014-09-27 03:39:46.03 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_policy_target_conditions_internal.
2014-09-27 03:39:46.04 spid7s index restored for msdb.sysmail_server.
2014-09-27 03:39:46.04 spid7s index restored for msdb.syspolicy_policy_categories_internal.
2014-09-27 03:39:46.04 spid7s index restored for msdb.syspolicy_object_sets_internal.
2014-09-27 03:39:46.04 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.05 spid7s index restored for msdb.sysmail_configuration.
2014-09-27 03:39:46.05 spid7s index restored for msdb.sysdbmaintplan_databases.
2014-09-27 03:39:46.05 spid7s index restored for msdb.log_shipping_primary_databases.
2014-09-27 03:39:46.39 spid7s The default collation was successfully changed.
2014-09-27 03:39:46.39 spid7s Recovery is complete. This is an informational message only. No user action is required.
2014-09-27 03:39:47.17 spid51 Changed database context to 'master'.
2014-09-27 03:39:47.18 spid51 Changed language setting to us_english.
2014-09-27 03:39:47.72 spid51 Setting database option RECOVERY to FULL for database model.
2014-09-27 03:39:47.84 spid51 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.84 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:47.98 spid51 Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:47.98 spid51 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:48.27 spid51 Error: 15007, Severity: 16, State: 1.
2014-09-27 03:39:48.27 spid51 '' is not a valid login or you do not have permission.
2014-09-27 03:51:25.13 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:51:25.13 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:51:32.67 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:51:32.67 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:51:42.11 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:51:42.11 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:52:42.07 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:52:42.07 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:53:01.23 Logon Error: 18461, Severity: 14, State: 1.
2014-09-27 03:53:01.23 Logon Login failed for user 'CAGATAY\cagatay'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
2014-09-27 03:53:17.57 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:53:17.57 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:53:32.54 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:53:32.54 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:04.29 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:54:04.29 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:10.36 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:54:10.36 Logon Login failed for user 'CAGATAY\cagatay'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:47.18 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:54:47.18 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
Resolve the error, please refer to the following links.
Enable DAC:http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition/
could not register the SPN Kerberos:
http://saveadba.blogspot.com/2012/03/could-not-register-spn-kerberos.html
Make sure the password of sa is correct,and the login 'CAGATAY\cagatay' has been created in SQL Server -
Internal Server Error (NullPointerException) when invoking a Web Service
I'm using SOA suite 10.1.3.3 (incl the latest patch set) on Windows XP.
I've created 3 web services using the wizard interface out of 3 existing WSDL files. The Java code inside the web services is just dummy code.
I'm testing the web services using the Test Web Service functionality in Oracle Enterprise Manager's Application Server Control.
The moment I fill in the data and press invoke, I get back the following fault:
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>Internal Server Error (Caught exception while handling request: java.lang.NullPointerException)</faultstring>
</env:Fault>
</env:Body>
I know that control never reaches inside the services themselves.
I've even followed the online demo that shows users how to create, deploy and test a Web Service in JDeveloper to make sure that I wasn't doing anything silly.
What could be wrong? Please help.
Thanks in advance.Seems to be a problem in serialization??? What do I do?
When I invoke the web service from a web proxy client, this is the stack trace:
QueryGDSAsiaPackage.SearchAirline_fault: java.lang.NullPointerException
at QueryGDSAsiaPackage.runtime.SearchAirline_fault__LiteralSerializer.doDeserialize(SearchAirline_fault__LiteralSerializer.java:71)
at oracle.j2ee.ws.common.encoding.literal.LiteralObjectSerializerBase.internalDeserialize(LiteralObjectSerializerBase.java:250)
at oracle.j2ee.ws.common.encoding.literal.LiteralObjectSerializerBase.deserialize(LiteralObjectSerializerBase.java:159)
at QueryGDSAsiaPackage.runtime.QueryGDS_Asia_PortType_searchAirline_Fault_SOAPSerializer.deserializeDetail(QueryGDS_Asia_PortType_searchAirline_Fault_SOAPSerializer.java:56)
at oracle.j2ee.ws.common.encoding.SOAPFaultInfoSerializer.doDeserializeSOAP11(SOAPFaultInfoSerializer.java:132)
at oracle.j2ee.ws.common.encoding.SOAPFaultInfoSerializer.doDeserialize(SOAPFaultInfoSerializer.java:94)
at oracle.j2ee.ws.common.encoding.ObjectSerializerBase.deserialize(ObjectSerializerBase.java:180)
at oracle.j2ee.ws.common.encoding.ReferenceableSerializerImpl.deserialize(ReferenceableSerializerImpl.java:147)
at oracleesb.QueryGDA_Asia_proxy.runtime.QueryGDS_AsiaSOAP_Stub._readBodyFaultElement(QueryGDS_AsiaSOAP_Stub.java:346)
at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:321)
at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:112)
at oracleesb.QueryGDA_Asia_proxy.runtime.QueryGDS_AsiaSOAP_Stub.searchAirline(QueryGDS_AsiaSOAP_Stub.java:155)
at QueryGDSAsiaPackage.QueryGDS_AsiaSOAPClient.searchAirline(QueryGDS_AsiaSOAPClient.java:43)
at QueryGDSAsiaPackage.QueryGDS_AsiaSOAPClient.main(QueryGDS_AsiaSOAPClient.java:30)
Process exited with exit code 0. -
WebCenter Sites : Consume Web Services and apply templates
Hi,
What is the best approach to consume Web Services or REST Service with Sites?
The idea is to consume some eServices personalized for a connected user and apply different presentation templates for those services to add to Sites pages.
Any Best practices here ?
Regards
JoFor consuming SOAP services inside a delivery template, there used to be the webservices:invoke tag but it was deprecated in version 7.6, and was generally not recommended to use anyway. There are no new tags for consuming SOAP or REST webservices, customers asking to do that are generally advised to reuse the existing libraries and write their client code in java, for example directly in an element/template or custom tag that you use in elements/templates. For performing simple REST queries you could use ics.ReadPage or httpclient.
Sites (was CS) comes with jars for handling SOAP and REST services, such as saaj, xmlbeans, jaxrpc, and jersey. You can use these, but if you run into bugs or limitations with the provided versions be aware that upgrading these jars may break Sites. And similarly, upgrading Sites may change these jars and so break your client code.
Phil -
SQL Server 2008 Reporting Services HTTP 500 error
Hi Everyone,
I recently tried changing authentication mode in RSReportServer.config, I changed from RSWindowsBasic to RSWindowsNegotiate. After restarting the services, I tried to access the Reports page (which worked before my change), but I was unable to load HTTP
500 error.
I then did what anyone else would do, revert back to the origin config and restart the services. I then tried to access but I got exactly the same error, HTTP 500.
I really dont understand why, I have reverted back to exactly the same configuration that work.
The error messages from the logs are as follows:
rshost!rshost!16ec!01/16/2014-13:33:53:: i INFO: CLR runtime is initialized.
rshost!rshost!16ec!01/16/2014-13:33:53:: v VERBOSE: Initializing Memory Monitoring
rshost!rshost!16ec!01/16/2014-13:33:53:: i INFO: Derived memory configuration based on physical memory as 4193848 KB
rshost!rshost!16ec!01/16/2014-13:33:53:: w WARN: Failed to initialize performance counters: ffffffff. Possible setup issue.
rshost!rshost!16ec!01/16/2014-13:33:53:: v VERBOSE: Supported winsock version is 2.2.
appdomainmanager!DefaultDomain!18e4!01/16/2014-13:33:53:: i INFO: Entered managed ServiceMain in DefaultDomain.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing ConnectionType to '0' as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing SecureConnectionLevel to '2' as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing WebServiceUseFileShareStorage to 'False' as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing WatsonFlags to '1064' as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException,Microsoft.ReportingServices.ReportProcessing.UnhandledReportRenderingException'
as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'System.Threading.ThreadAbortException,System.Web.UI.ViewStateException,System.OutOfMemoryException,System.Web.HttpException,System.IO.IOException,System.IO.FileLoadException,Microsoft.SharePoint.SPException'
as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing AuthenticationTypes to '8' as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing RSWindowsExtendedProtectionLevel to 'Off' as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing RSWindowsExtendedProtectionScenario to 'Proxy' as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing EnableAuthPersistence to 'True' as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing IsSchedulingService to 'True' as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing IsNotificationService to 'True' as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing IsEventService to 'True' as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing WindowsServiceUseFileShareStorage to 'False' as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing MemorySafetyMargin to '80' percent as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing MemoryThreshold to '90' percent as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing UrlRoot to 'https://ssrsreportingppe.companytest9.co.uk:4434/ReportServer' as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing IsWebServiceEnabled to 'True' as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing IsReportManagerEnabled to 'True' as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing ReportServerUrl to 'https://ssrsreportingppe.companytest9.co.uk:4434/ReportServer' as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing MaxConnections to '2' as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing Timeout to '10' second(s) as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing AppID to '(Default)' as specified in Configuration file.
library!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Initializing CacheLevel to 'Default' as specified in Configuration file.
resourceutilities!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Reporting Services starting SKU: Enterprise
configmanager!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Using report server internal url https://ssrsreportingppe.companytest9.co.uk:4434/ReportServer.
configmanager!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Using report server external url https://TEST-SRV-DBA01:4445/ReportServer.
configmanager!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Using url root https://ssrsreportingppe.companytest9.co.uk:4434/ReportServer.
configmanager!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: AuthPersistence does not apply to basic authentication.
rshost!rshost!d30!01/16/2014-13:33:54:: i INFO: Configuring maxPhysicalCpu=8, minLogicalCpu=0
rshost!rshost!d30!01/16/2014-13:33:54:: i INFO: Logical processor per physical processor 1
rshost!rshost!d30!01/16/2014-13:33:54:: i INFO: Maximum logical CPU is 1
configmanager!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Using report server internal url https://ssrsreportingppe.companytest9.co.uk:4434/ReportServer.
configmanager!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Using report server external url https://TEST-SRV-DBA01:4445/ReportServer.
configmanager!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Using url root https://ssrsreportingppe.companytest9.co.uk:4434/ReportServer.
configmanager!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: AuthPersistence does not apply to basic authentication.
appdomainmanager!DefaultDomain!d30!01/16/2014-13:33:54:: i INFO: Appdomain:2 WindowsService_0 started.
resourceutilities!WindowsService_0!d30!01/16/2014-13:33:55:: i INFO: Reporting Services starting SKU: Enterprise
library!WindowsService_0!1f70!01/16/2014-13:33:55:: i INFO: Catalog SQL Server Edition = Enterprise
appdomainmanager!DefaultDomain!d30!01/16/2014-13:33:55:: i INFO: The UserAccountControl value for the service account is 512
rshost!rshost!1940!01/16/2014-13:33:55:: i INFO: Registered url=https://TEST-SRV-DBA01.company.co.uk:4444/ReportServer/, vdir=/ReportServer, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer.
rshost!rshost!1940!01/16/2014-13:33:55:: i INFO: Registered url=http://SSRSReportingPPE.companytest9.co.uk:8081/ReportServer/, vdir=/ReportServer, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer.
rshost!rshost!1940!01/16/2014-13:33:55:: i INFO: Registered url=https://+:4445/ReportServer/, vdir=/ReportServer, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer.
rshost!rshost!1940!01/16/2014-13:33:55:: i INFO: Registered url=https://+:4443/ReportServer/, vdir=/ReportServer, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer.
rshost!rshost!1940!01/16/2014-13:33:55:: i INFO: Currently registered url https://+:4443/ReportServer/ on endpoint 2
rshost!rshost!1940!01/16/2014-13:33:55:: i INFO: Currently registered url https://+:4445/ReportServer/ on endpoint 2
rshost!rshost!1940!01/16/2014-13:33:55:: i INFO: Currently registered url http://SSRSReportingPPE.companytest9.co.uk:8081/ReportServer/ on endpoint 2
rshost!rshost!1940!01/16/2014-13:33:55:: i INFO: Currently registered url https://TEST-SRV-DBA01.company.co.uk:4444/ReportServer/ on endpoint 2
appdomainmanager!DefaultDomain!d30!01/16/2014-13:33:55:: i INFO: The UserAccountControl value for the service account is 512
crypto!WindowsService_0!1f70!01/16/2014-13:33:55:: i INFO: Initializing crypto as user: company\adm.sukh.gidda
rshost!rshost!1d44!01/16/2014-13:33:55:: i INFO: Registered url=https://TEST-SRV-DBA01.company.co.uk:4444/Reports/, vdir=/Reports, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportManager.
rshost!rshost!1d44!01/16/2014-13:33:55:: i INFO: Registered url=http://SSRSReportingPPE.companytest9.co.uk:8081/Reports/, vdir=/Reports, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportManager.
rshost!rshost!1d44!01/16/2014-13:33:55:: i INFO: Registered url=https://WMSvc-TEST-SRV-DBA01:4444/Reports/, vdir=/Reports, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportManager.
rshost!rshost!1d44!01/16/2014-13:33:55:: i INFO: Registered url=https://+:4445/Reports/, vdir=/Reports, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportManager.
rshost!rshost!1d44!01/16/2014-13:33:55:: i INFO: Registered url=https://+:4434/Reports/, vdir=/Reports, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportManager.
rshost!rshost!1d44!01/16/2014-13:33:55:: i INFO: Currently registered url https://+:4434/Reports/ on endpoint 3
rshost!rshost!1d44!01/16/2014-13:33:55:: i INFO: Currently registered url https://+:4445/Reports/ on endpoint 3
rshost!rshost!1d44!01/16/2014-13:33:55:: i INFO: Currently registered url https://WMSvc-TEST-SRV-DBA01:4444/Reports/ on endpoint 3
rshost!rshost!1d44!01/16/2014-13:33:55:: i INFO: Currently registered url http://SSRSReportingPPE.companytest9.co.uk:8081/Reports/ on endpoint 3
rshost!rshost!1d44!01/16/2014-13:33:55:: i INFO: Currently registered url https://TEST-SRV-DBA01.company.co.uk:4444/Reports/ on endpoint 3
rshost!rshost!1d44!01/16/2014-13:33:55:: i INFO: Endpoint 4 is disabled and no url is registered vdir=/ReportServer/ReportBuilder, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer\ReportBuilder.
resourceutilities!DefaultDomain!d30!01/16/2014-13:33:55:: i INFO: Maximum memory limit is 2097152Mb
rshost!rshost!d30!01/16/2014-13:33:55:: i INFO: Derived memory configuration based on physical memory as 4193848 KB
servicecontroller!DefaultDomain!1d44!01/16/2014-13:33:55:: i INFO: Total Physical memory: 4294500352
rpcserver!DefaultDomain!1940!01/16/2014-13:33:55:: i INFO: Process monitoring started.
library!WindowsService_0!1f70!01/16/2014-13:33:55:: v VERBOSE: Transaction begin.
crypto!WindowsService_0!1f70!01/16/2014-13:33:55:: i INFO: Exporting public key
crypto!WindowsService_0!1f70!01/16/2014-13:33:55:: i INFO: Performing sku validation
crypto!WindowsService_0!1f70!01/16/2014-13:33:55:: i INFO: Importing existing encryption key
library!WindowsService_0!1f70!01/16/2014-13:33:55:: v VERBOSE: Transaction commit.
library!WindowsService_0!1f70!01/16/2014-13:33:56:: v VERBOSE: Transaction begin.
library!WindowsService_0!1f70!01/16/2014-13:33:56:: v VERBOSE: Transaction commit.
dbpolling!WindowsService_0!1f70!01/16/2014-13:33:56:: i INFO: EventPolling polling service started
dbpolling!WindowsService_0!1ef4!01/16/2014-13:33:56:: i INFO: HeartbeatThread(EventPolling): heartbeat thread started.
dbpolling!WindowsService_0!1f70!01/16/2014-13:33:56:: i INFO: NotificationPolling polling service started
dbpolling!WindowsService_0!1f94!01/16/2014-13:33:56:: i INFO: HeartbeatThread(NotificationPolling): heartbeat thread started.
dbpolling!WindowsService_0!1f70!01/16/2014-13:33:56:: i INFO: SchedulePolling polling service started
dbpolling!WindowsService_0!1f70!01/16/2014-13:33:56:: i INFO: UpgradePolling polling service started
dbpolling!WindowsService_0!1a54!01/16/2014-13:33:56:: i INFO: PollingMaintenance: Polling started
resourceutilities!WindowsService_0!1a54!01/16/2014-13:33:56:: i INFO: Maximum memory limit is 2097152Mb
rpcserver!DefaultDomain!1f70!01/16/2014-13:33:56:: i INFO: RPC Server started.
servicecontroller!DefaultDomain!1f70!01/16/2014-13:33:56:: i INFO: RPC Server started. Endpoint name ='ReportingServices$MSRS10_50.MSSQLSERVER'
appdomainmanager!WindowsService_0!1f70!01/16/2014-13:33:56:: i INFO: Appdomain:2 WindowsService_0 initialized.
library!WindowsService_0!1a54!01/16/2014-13:33:56:: Attempting upgrade of MigrateExecutionLog
rshost!rshost!18e4!01/16/2014-13:34:39:: v VERBOSE: AcceptCallback(): accepted new connection pipeline=0x000000000036DC50...
rshost!rshost!1478!01/16/2014-13:34:39:: v VERBOSE: ThreadContinuePipeline: processing request on pipeline=0x000000000036DC50, state=0, IOError=0, node=0.
appdomainmanager!DefaultDomain!1478!01/16/2014-13:34:49:: i INFO: Appdomain:3 ReportManager_MSSQLSERVER_0-1-130343528892811172 started.
appdomainmanager!ReportManager_0-1!1478!01/16/2014-13:34:49:: i INFO: RS authentication mode is 8; effective ASP.NET authentication mode is Windows. vdir=/Reports.
appdomainmanager!ReportManager_0-1!1478!01/16/2014-13:34:49:: v VERBOSE: Managed threadpool maxWorkerThread=100, maxIoCompletionThread=100 ...
appdomainmanager!ReportManager_0-1!1478!01/16/2014-13:34:49:: v VERBOSE: Managed threadpool minWorkerThread=1, minIoCompletionThread=1 ...
appdomainmanager!DefaultDomain!1478!01/16/2014-13:34:49:: i INFO: Appdomain:3 ReportManager_MSSQLSERVER_0-1-130343528892811172 initialized (#1).
rshost!rshost!1478!01/16/2014-13:34:49:: v VERBOSE: Processing request pipeline=0x000000000036DC50, callback=0xace640, callback->pipeline=0x000000000036DC50, id=17077649789136404660, connid=17077649788599533747 ...
httpruntime!ReportManager_0-1!1478!01/16/2014-13:34:49:: v VERBOSE: Response header encoding is Unicode (UTF-8).
ui!ReportManager_0-1!1478!01/16/2014-13:34:51:: v VERBOSE: User map'<Users><User><Name>TEST-SRV-DBA01\LocalAdmin</Name><Paths><Path>/Reports/home.aspx</Path><NrReq>1</NrReq></Paths></User></Users>'
rshost!rshost!1478!01/16/2014-13:34:51:: v VERBOSE: HttpPipelineCallback::EndOfRequest(): continue pipeline=0x000000000036DC50.
rshost!rshost!18e4!01/16/2014-13:34:51:: v VERBOSE: ThreadContinuePipeline: processing request on pipeline=0x000000000036DC50, state=2, IOError=0, node=0.
rshost!rshost!1180!01/16/2014-13:34:52:: v VERBOSE: AcceptCallback(): accepted new connection pipeline=0x0000000003631610...
rshost!rshost!1478!01/16/2014-13:34:52:: v VERBOSE: ThreadContinuePipeline: processing request on pipeline=0x0000000003631610, state=0, IOError=0, node=0.
rshost!rshost!1478!01/16/2014-13:34:52:: v VERBOSE: Processing request pipeline=0x0000000003631610, callback=0xace620, callback->pipeline=0x0000000003631610, id=17365880165288116379, connid=17365880164751245466 ...
ui!ReportManager_0-1!1478!01/16/2014-13:34:52:: v VERBOSE: User map'<Users><User><Name>TEST-SRV-DBA01\LocalAdmin</Name><Paths><Path>/Reports/Pages/Folder.aspx</Path><NrReq>1</NrReq></Paths></User></Users>'
ui!ReportManager_0-1!1478!01/16/2014-13:34:53:: e ERROR: Microsoft.SqlServer.ReportingServices2010.RSConnection2010+MissingEndpointException: The attempt to connect to the report server failed. Check your connection information and that the report
server is a compatible version. ---> System.Net.WebException: The remote server returned an error: (404) Not Found.
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.ReportingServices.UI.ServerAuthType.GetReportServerAuthentication()
at Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetNewWebRequest(Uri uri)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.SqlServer.ReportingServices2010.ReportingService2010.ListItemTypes()
at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.<ListItemTypes>b__10f()
at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SoapMethodWrapper`1.ExecuteMethod(Boolean setConnectionProtocol)
--- End of inner exception stack trace ---
at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.MissingEndpointException.ThrowIfEndpointMissing(WebException e)
at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SoapMethodWrapper`1.ExecuteMethod(Boolean setConnectionProtocol)
at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SoapMethodWrapper`1.ExecuteMethod()
at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.ListItemTypes()
at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
at Microsoft.ReportingServices.UI.ReportingPage.EnsureHttpsLevel()
at Microsoft.ReportingServices.UI.ReportingPage.ReportingPage_Init(Object sender, EventArgs args)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Web.UI.Control.OnInit(EventArgs e)
at System.Web.UI.Page.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
ui!ReportManager_0-1!1478!01/16/2014-13:34:53:: e ERROR: Microsoft.SqlServer.ReportingServices2010.RSConnection2010+MissingEndpointException: The attempt to connect to the report server failed. Check your connection information and that the report
server is a compatible version. ---> System.Net.WebException: The remote server returned an error: (404) Not Found.
at System.Net.HttpWebRequest.GetResponse()
at Microsoft.ReportingServices.UI.ServerAuthType.GetReportServerAuthentication()
at Microsoft.ReportingServices.UI.Global.RSWebServiceWrapper.GetNewWebRequest(Uri uri)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Microsoft.SqlServer.ReportingServices2010.ReportingService2010.ListItemTypes()
at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.<ListItemTypes>b__10f()
at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SoapMethodWrapper`1.ExecuteMethod(Boolean setConnectionProtocol)
--- End of inner exception stack trace ---
at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.MissingEndpointException.ThrowIfEndpointMissing(WebException e)
at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SoapMethodWrapper`1.ExecuteMethod(Boolean setConnectionProtocol)
at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.SoapMethodWrapper`1.ExecuteMethod()
at Microsoft.SqlServer.ReportingServices2010.RSConnection2010.ListItemTypes()
at Microsoft.ReportingServices.UI.Global.SecureAllAPI()
at Microsoft.ReportingServices.UI.GlobalLinks.Control_Init(Object sender, EventArgs args)
ui!ReportManager_0-1!1478!01/16/2014-13:34:53:: e ERROR: HTTP status code --> 500
Anyone seen this issue before? Or know why its failing from the logs?
Thanks,
JohnHi John,
HTTP 500 error can occur if there are conflicting authentication settings in the report server Web.config file and the RSReportServer.config file. HTTP 500 is returned if authentication initially succeeds and then the mismatch is detected. In RSReportServer.config
file, make sure the AuthenticationTypes setting as follows:
<AuthenticationTypes>
<RSWindows*/>
</AuthenticationTypes>
In the report server Web.config file, please also check the authentication type:
Authentication=”Windows”
Reference:
http://technet.microsoft.com/en-us/library/ms159778(v=sql.105).aspx
If the issue is persist, please check if the web services URL in web.config file is correct.
Hope this helps.
Regards,
Alisa Tang
If you have any feedback on our support, please click
here.
Alisa Tang
TechNet Community Support -
have added name to Sql server , users cannot access the report, getting error message ,
I have give all the permission to this users, so why this users still cannot look at the report,
and getting error message,
An error has occurred during report processing.
cannot create a connection to data source Ax live
for more information about this error navigate to the report server on the local server machine or enable remote errors.
can some please help me what this message means,
I really appreciate it
thanks In advanceIf "Credentials supplied by the user running the report" is selected, when the report is run, the user will be prompted to provide credentials. They would need to provide credentials that have the appropriate permissions (e.g., read, execute) to the
database. This prevents the double hop.
If "Credentials stored securely in the report server" is selected, you have to enter the username and password of a user (or service account) that has the appropriate permissions (e.g., read, execute) to the database. When the report is run, SSRS will use
these stored credentials each time to authenticate to the database engine and query the data. Users running the report are not prompted to provide credentials. With this option you can use an Active Directory or SQL Server account.
In order to access/run the report, a user will need to authenticate to SSRS. There are options here as well. You can provide them the link to the report manager and they can authenticate, navigate to, and run the report. You can also provide
direct links to reports that users click in a document or application. At this point the user is typically still prompted to authenticate to SSRS. You can also programmatically call the report using API's and essentially build a proxy that authenticates
to SSRS and open the report.
Not sure if that answers your question. -
How to make a PDF form call Web service and return a static pdf for user to print?
Hi all,
Can anyone help me regarding the feasibility of using PDF forms for my following case?
I would like to create a Dynamic pdf form. User only have the Acrobat reader. they can enter some information. Then have a submit button. when user click the submit button, it can call the web service with data. then Web service returns a Static PDF document based on data and the user can print it out. (and maybe save as separate pdf file)
1. Is that possible to implement? Because I know PDF can call web service, but dont know how it handle when the webservice returns another static PDF document. could it able to handle the responds and open up in another acrobat reader?
2. As I understand I need to have Live Cycle Designer to create a pdf and make it Reader Enabled. So user can user reader to call webservice? am I correct?
3. What minimum reader that user need to have? PDF reader 7 or above?
4. I have a webservice serve the same purpose for web. But if I want the same web services can serve both web and PDF form. So, whatever client (PDF or Web)make the web service call, server returns the PDF document to client. Is that possible ? Do I need to make any changes on web service?
5. Do I need to get any other Adobe server product? (other than Live Cycle Designer )
Thanks a lotWe have done a similar approach in the past and yes, it can be doable.
1. Is that possible to implement? Because I know PDF can call web service, but dont know how it handle when the webservice returns another static PDF document. could it able to handle the responds and open up in another acrobat reader?
Srini: We have developed a Servlet to talk to Webservice. Based on the Webservice response, the Servlet, prepares the Byte stream and sends it to Webbrowser to display as a PDF. The PDF data was submitted to Servlet in XML format.
But if you do not want to use the above approach, then you have to use the Workbench Process.
Submit the PDF data to a Workbench process and the inside process, execute Webservice Service with the data. Once the response is received, prepare the data XML and render a PDF with it.
To do this, you need LiveCycle Server and Reader Extensions server component.
2. As I understand I need to have Live Cycle Designer to create a pdf and make it Reader Enabled. So user can user reader to call webservice? am I correct?
Srini: If you want to use the Servlet, you can Reader extend the PDF with Acrobat.. But if you want to submit the data directly to Webservice, then you need Reader Extensions server component.
3. What minimum reader that user need to have? PDF reader 7 or above?
Srini: Not sure but Reader 8 and above should work.
4. I have a webservice serve the same purpose for web. But if I want the same web services can serve both web and PDF form. So, whatever client (PDF or Web)make the web service call, server returns the PDF document to client. Is that possible ? Do I need to make any changes on web service?
Srini: If you use the Servlet approach, then you can re-use the same webservice. But if you want to submit directly to the same webservice, you may need to change it to suit your data XML.
5. Do I need to get any other Adobe server product? (other than Live Cycle Designer )
Srini: If you use the Servlet approach, you do not need any server component but other approach, you need Livecycle Server and Reader Extensions server component.
Thanks
Srini -
Create Web Services and return a complex type with ADF
Hello,
I've tried tried using ADF BC and service interface to create a Web service, this works well, but I needed to return more complex data types, such as a list of person objects (name, last name, ...), as I reviewed in the ADF BC service interface can return only some types of data :(
Anyone know how I could do this using ADF BC, or how else do you recommend
thanksHow I can access to the AppModule from java class in the Model Project
I've tried use
String amDef = "model.services.WsAM";
String config = "WsAMLocal";
ApplicationModule am = Configuration.createRootApplicationModule(amDef, config);
WsAMImpl myAm = (WsAMImpl)am;
but in the Web Service, this throw a exception
<ns2:exception class="java.lang.NoClassDefFoundError" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false" xmlns:ns2="http://jax-ws.dev.java.net/">
<message>oracle/jbo/client/Configuration</message>
please I hope your help
Thanks.
Edited by: rmespas80 on 08-jul-2011 16:26 -
I'm quite stumped. All of my reports are suddenly blank. I see the icons for the reports, and I can even download the PDF by exporting to Excel of PDF.
Can someone help explain what may have happened to my instance and how to correct this?Hi JMitchell1,
According to your description, your reports become blank when you access them on Report Manger. Right?
In this scenario, does the exported file also show you a blank report? Since you can access the Report Manager successfully and open report means the report server is still working. It can be running out of memory. You can open the report with Report
Builder to see if the report is damaged. Also try to restart report server and reconnect the database. If it's still not working, you may need to redeploy your reports.
If you have any question, please feel free to ask.
Best Regards,
Simon Hou -
10g: Invoking a web service asynchronously from BPEL
Hello,
I am trying to figure out a good, generic method for making a previously synchronous web service asynchronous and changing the way in which it is invoked from BPEL. I am using SOA Suite 10g (10.1.3.5)
As I understand, one possible method to achieve this is to use IDeliveryService.post() to deliver the web service's response to the BPEL process. For this route, the standard practice of correlation seems to be to supply a correlation Id when invoking the web service and returning the same correlation id as a part of the web service's response message. However, I want to avoid this since it would mean that all response messages from the web service (10+) would have to be modified to include a correlationId, which is problematic in the special case of this web service. Including a correlationId in the request message is possible, however.
I have tried the approach of using the conversation Id directly instead of the correlation Id, by reading the value of ora:getConversationId(), passing this to the web service and setting the property CONVERSATION_ID of the response NormalizedMessage to the same value when returning. However, I cannot seem to get this approach right. Is this possible at all?
An alternative might be to use WS-Addressing, but I do not know if I can make the web service support this - it is written using the EJB WebService-Annotations feature and runs on OC4J as well.
Do you have any suggestions on how this problem could be resolved?
Edited by: 901765 on 12.12.2011 06:01I have found the following tutorial that implements something similiar to what I am trying to do: http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/odi/10g/10135/odiscenario_bpelcallback/odiscenario_bpelcallback.htm#t3
Because of this, I am now confident that the conversation IDs can be used to achieve correlation. I have implemented the pattern by performing
an invoke activity on the web service, passing the result of ora:getConversationId() as part of the message. The conversation Id returned is of UUID-Form.
After the invoke activity, I have added a pick activity to receive the response message supplied by the web service through IDeliveryService.post(...). I can see that the message is received correctly by loooking at the contents of DLV_MESSAGE. However, the pick activity times out every time (after 10m). Looking at DLV_SUBSCRIPTION reveals that the conversation_id for the pick/receive activity is set to a value of the form bpel://localhost/default/MyBpelProcessName~1.0/7610001-BpInv0-BpSeq2.7-2. As far as I know, this should instead be set to the UUID that ora:getConversationId() returned before performing the invoke activity. What is going wrong here?
Thanks for your help! -
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 -
SQL Server 2008 Express Setup Issue SKU
Hi,
a configuration file driven setup worked on roughly 30 machines without problems.
However, on one certain machine (which is costumer owned in Saudi Arabia) the installation seems to
be blocked at an early stage. Logfiles reporting something about "SKU", but this makes not clear for me
what the problem is.
The Summary.txt is pasted, below this Details.txt is placed (the bottom part which contains the error portion).
Thanks for help in advance!
Peter
Summary.txt
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Exit code (Decimal): -213508975
Exit facility code: 838
Exit error code: 7313
Exit message: sku
Start time: 2013-11-14 19:00:59
End time: 2013-11-14 19:03:07
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.2531.0%26EvtType%3d0xC16B698F%400x6AD84D9E
Machine Properties:
Machine name: F950DS1
Machine processor count: 4
OS version: Windows Vista
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x86
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
Sql Server 2008 SQLEXPRESS MSSQL10.SQLEXPRESS Database Engine Services
1033 Express Edition 10.1.2531.0 No
Sql Server 2008 SQLEXPRESS MSSQL10.SQLEXPRESS Database Engine Services
1031 Express Edition 10.1.2531.0 No
Sql Server 2008 SQLEXPRESS MSSQL10.SQLEXPRESS SQL Server Replication
1033 Express Edition 10.1.2531.0 No
Sql Server 2008 SQLEXPRESS MSSQL10.SQLEXPRESS SQL Server Replication
1031 Express Edition 10.1.2531.0 No
Sql Server 2008 GESTRAVKP4030 MSSQL10.GESTRAVKP4030 Database Engine Services
1033 10.1.2531.0
No
Sql Server 2008 GESTRAVKP4030 MSSQL10.GESTRAVKP4030 Database Engine Services
1031 10.1.2531.0
No
Package properties:
Description: SQL Server Database Services 2008
SQLProductFamilyCode: {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName: SQL2008
Type: RTM
Version: 10
Installation location: C:\Users\Administrator\Desktop\VKP30\MSSql2008ExpressSP1\X86\x86\setup\
Installation edition: Invalid
Slipstream: True
SP Level 1
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: True
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Automatic
CONFIGURATIONFILE: C:\Users\Administrator\Desktop\VKP30\MSSql2008ExpressSP1\X86\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: True
ERRORREPORTING: False
FEATURES: SQLENGINE
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: True
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: GESTRAVKP4030
INSTANCENAME: GESTRAVKP4030
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PCUSOURCE: C:\Users\Administrator\Desktop\VKP30\MSSql2008ExpressSP1\X86\PCUSOURCE
PID: *****
QUIET: False
QUIETSIMPLE: False
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: System.ArgumentException
Message:
sku
Data:
DisableWatson = true
Stack:
at Microsoft.SqlServer.Configuration.InstallFeatureEdition..ctor(ServiceContainer context, SqlEdition sku, String instanceName)
at Microsoft.SqlServer.Configuration.InstallFeatureTree..ctor(ServiceContainer context)
at Microsoft.SqlServer.Configuration.InstallWizard.InstallFeatureTreeController.LoadFeatureTree()
at Microsoft.SqlServer.Configuration.InstallWizard.InstallFeatureTreeController.Initialize()
at Microsoft.SqlServer.Configuration.InstallWizardFramework.ConfigurationController.Microsoft.SqlServer.Configuration.InstallWizardFramework.ISettingStoreSite.SetSettingStore(SettingStore store)
at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardPageHost.SiteObject(Object pageController)
at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardPageHost.CreatePageController(Type type)
at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.EnsurePageControllerExists()
at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.CreateView()
at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.get_Control()
at Microsoft.SqlServer.Configuration.WizardFramework.HostControl.OnSelectedPageChanged(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.OnSelectedPageChanged()
at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.set_SelectedPageIndex(Int32 value)
at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.GoNext()
at Microsoft.SqlServer.Configuration.WizardFramework.NavigationButtons.nextButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Detail.txt
2013-11-14 19:01:44 Slp: -- SkuPublicConfigObject : Calling SkuPublicConfigObject.Calculate.
2013-11-14 19:01:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2013-11-14 19:01:44 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\100
2013-11-14 19:01:44 Slp: Sco: Attempting to get registry value SharedCode
2013-11-14 19:01:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2013-11-14 19:01:44 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.GESTRAVKP4030\Setup
2013-11-14 19:01:44 Slp: Sco: Attempting to get registry value ProductID
2013-11-14 19:01:44 Slp: Sco: Attempting to get registry value DigitalProductID
2013-11-14 19:01:44 Slp: -- SkuPublicConfigObject : Using edition 'Invalid' from existing instance 'GESTRAVKP4030'.
2013-11-14 19:01:44 Slp: SLP: GetDiskCostByProductFeatures: mapped to 3 target directories
2013-11-14 19:01:44 Slp: SLP: GetDiskCostByProductFeatures: Target Directory is "SYSTEMDRIVE"; Disk Cost: "121559"kb
2013-11-14 19:01:44 Slp: SLP: GetDiskCostByProductFeatures: Target Directory is "INSTALLSHAREDDIR"; Disk Cost: "132"kb
2013-11-14 19:01:44 Slp: SLP: GetDiskCostByProductFeatures: Target Directory is "INSTANCEDIR"; Disk Cost: "181258"kb
2013-11-14 19:01:44 Slp: Sco: Attempting to get directory information for path C:\Program Files\Microsoft SQL Server\
2013-11-14 19:01:44 Slp: Sco: Attempting to get directory information for path C:\Program Files\Microsoft SQL Server\
2013-11-14 19:01:44 Slp: Sco: Attempting to get directory information for path C:\Program Files\Microsoft SQL Server\
2013-11-14 19:01:44 Slp: Sco: Attempting to get directory information for path C:\Program Files\Microsoft SQL Server\
2013-11-14 19:01:44 Slp: Error: Action "GatherUserSettings" threw an exception during execution.
2013-11-14 19:01:44 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Thread was being aborted. ---> System.Threading.ThreadAbortException: Thread was being aborted.
2013-11-14 19:01:44 Slp: at System.Threading.WaitHandle.WaitOneNative(SafeHandle waitableSafeHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
2013-11-14 19:01:44 Slp: at System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
2013-11-14 19:01:44 Slp: at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext)
2013-11-14 19:01:44 Slp: at System.Threading.WaitHandle.WaitOne()
2013-11-14 19:01:44 Slp: at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
2013-11-14 19:01:44 Slp: at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.SubmitAndWait(Request request)
2013-11-14 19:01:44 Slp: at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
2013-11-14 19:01:44 Slp: at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Waypoint(String moniker)
2013-11-14 19:01:44 Slp: at Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
2013-11-14 19:01:44 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2013-11-14 19:01:45 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2013-11-14 19:01:45 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2013-11-14 19:01:45 Slp: --- End of inner exception stack trace ---
2013-11-14 19:01:45 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2013-11-14 19:01:45 Slp: Received request to add the following file to Watson reporting: C:\Users\Administrator\AppData\Local\Temp\tmp5718.tmp
2013-11-14 19:01:45 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2013-11-14 19:01:45 Slp: Inner exceptions are being indented
2013-11-14 19:01:45 Slp:
2013-11-14 19:01:45 Slp: Exception type: System.ArgumentException
2013-11-14 19:01:45 Slp: Message:
2013-11-14 19:01:45 Slp: sku
2013-11-14 19:01:46 Slp: Stack:
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.InstallFeatureEdition..ctor(ServiceContainer context, SqlEdition sku, String instanceName)
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.InstallFeatureTree..ctor(ServiceContainer context)
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.InstallWizard.InstallFeatureTreeController.LoadFeatureTree()
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.InstallWizard.InstallFeatureTreeController.Initialize()
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.InstallWizardFramework.ConfigurationController.Microsoft.SqlServer.Configuration.InstallWizardFramework.ISettingStoreSite.SetSettingStore(SettingStore
store)
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardPageHost.SiteObject(Object pageController)
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardPageHost.CreatePageController(Type type)
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.EnsurePageControllerExists()
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.CreateView()
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.get_Control()
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.WizardFramework.HostControl.OnSelectedPageChanged(Object sender, EventArgs e)
2013-11-14 19:01:46 Slp: at System.EventHandler.Invoke(Object sender, EventArgs e)
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.OnSelectedPageChanged()
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.set_SelectedPageIndex(Int32 value)
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.GoNext()
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.WizardFramework.NavigationButtons.nextButton_Click(Object sender, EventArgs e)
2013-11-14 19:01:46 Slp: at System.Windows.Forms.Control.OnClick(EventArgs e)
2013-11-14 19:01:46 Slp: at System.Windows.Forms.Button.OnClick(EventArgs e)
2013-11-14 19:01:46 Slp: at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
2013-11-14 19:01:46 Slp: at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
2013-11-14 19:01:46 Slp: at System.Windows.Forms.Control.WndProc(Message& m)
2013-11-14 19:01:46 Slp: at System.Windows.Forms.ButtonBase.WndProc(Message& m)
2013-11-14 19:01:46 Slp: at System.Windows.Forms.Button.WndProc(Message& m)
2013-11-14 19:01:46 Slp: at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
2013-11-14 19:01:46 Slp: at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
2013-11-14 19:01:46 Slp: at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
2013-11-14 19:02:13 Slp: Watson Bucket 1
Original Parameter Values
2013-11-14 19:02:13 Slp: Parameter 0 : SQL2008@RTM@
2013-11-14 19:02:13 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.InstallFeatureEdition..ctor
2013-11-14 19:02:13 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.InstallFeatureEdition..ctor
2013-11-14 19:02:13 Slp: Parameter 3 : System.ArgumentException@-2147024809
2013-11-14 19:02:13 Slp: Parameter 4 : System.ArgumentException@-2147024809
2013-11-14 19:02:13 Slp: Parameter 5 : GatherUserSettings
2013-11-14 19:02:13 Slp:
Final Parameter Values
2013-11-14 19:02:13 Slp: Parameter 0 : SQL2008@RTM@
2013-11-14 19:02:13 Slp: Parameter 1 : 0xC16B698F
2013-11-14 19:02:13 Slp: Parameter 2 : 0xC16B698F
2013-11-14 19:02:13 Slp: Parameter 3 : 0x6AD84D9E
2013-11-14 19:02:14 Slp: Parameter 4 : 0x6AD84D9E
2013-11-14 19:02:14 Slp: Parameter 5 : GatherUserSettings
2013-11-14 19:02:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2013-11-14 19:02:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2013-11-14 19:02:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2013-11-14 19:02:22 Slp: sku
2013-11-14 19:02:23 Slp: Watson bucket for exception based failure has been created
2013-11-14 19:02:23 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2013-11-14 19:02:23 Slp: Sco: Attempting to open registry subkey
2013-11-14 19:02:23 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
2013-11-14 19:02:23 Slp: Sco: Attempting to get registry value DW0200
2013-11-14 19:03:07 Slp: Submitted 1 of 1 failures to the Watson data repository
2013-11-14 19:03:12 Slp:
2013-11-14 19:03:12 Slp: ----------------------------------------------------------------------
2013-11-14 19:03:12 Slp:
2013-11-14 19:03:12 Slp: Error result: -213508975
2013-11-14 19:03:12 Slp: Result facility code: 838
2013-11-14 19:03:12 Slp: Result error code: 7313Hi,
a configuration file driven setup worked on roughly 30 machines without problems.
However, on one certain machine (which is costumer owned in Saud Arabia) the installation seems to
be blocked at an early stage. Logfiles reporting something about "Invalid edition ... SKU", but it not clear for me
what the problem is.
The Summary.txt is shown here, below this I will paste Details.txt (the bottom part which contains the error portion).
Thanks for help in advance!
Peter
Summary.txt
Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Exit code (Decimal): -213508975
Exit facility code: 838
Exit error code: 7313
Exit message: sku
Start time: 2013-11-14 19:00:59
End time: 2013-11-14 19:03:07
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\Detail.txt
Exception help link: http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.0.2531.0%26EvtType%3d0xC16B698F%400x6AD84D9E
Machine Properties:
Machine name: F950DS1
Machine processor count: 4
OS version: Windows Vista
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x86
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID
Feature Language
Edition Version Clustered
Sql Server 2008 SQLEXPRESS MSSQL10.SQLEXPRESS Database Engine Services
1033 Express Edition 10.1.2531.0 No
Sql Server 2008 SQLEXPRESS MSSQL10.SQLEXPRESS Database Engine Services
1031 Express Edition 10.1.2531.0 No
Sql Server 2008 SQLEXPRESS MSSQL10.SQLEXPRESS SQL Server Replication
1033 Express Edition 10.1.2531.0 No
Sql Server 2008 SQLEXPRESS MSSQL10.SQLEXPRESS SQL Server Replication
1031 Express Edition 10.1.2531.0 No
Sql Server 2008 GESTRAVKP4030 MSSQL10.GESTRAVKP4030 Database Engine Services
1033 10.1.2531.0
No
Sql Server 2008 GESTRAVKP4030 MSSQL10.GESTRAVKP4030 Database Engine Services
1031 10.1.2531.0
No
Package properties:
Description: SQL Server Database Services 2008
SQLProductFamilyCode: {628F8F38-600E-493D-9946-F4178F20A8A9}
ProductName: SQL2008
Type: RTM
Version: 10
Installation location: C:\Users\Administrator\Desktop\VKP30\MSSql2008ExpressSP1\X86\x86\setup\
Installation edition: Invalid
Slipstream: True
SP Level 1
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: True
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Automatic
CONFIGURATIONFILE: C:\Users\Administrator\Desktop\VKP30\MSSql2008ExpressSP1\X86\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: True
ERRORREPORTING: False
FEATURES: SQLENGINE
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: True
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: GESTRAVKP4030
INSTANCENAME: GESTRAVKP4030
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PCUSOURCE: C:\Users\Administrator\Desktop\VKP30\MSSql2008ExpressSP1\X86\PCUSOURCE
PID: *****
QUIET: False
QUIETSIMPLE: False
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: Latin1_General_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: System.ArgumentException
Message:
sku
Data:
DisableWatson = true
Stack:
at Microsoft.SqlServer.Configuration.InstallFeatureEdition..ctor(ServiceContainer context, SqlEdition sku, String instanceName)
at Microsoft.SqlServer.Configuration.InstallFeatureTree..ctor(ServiceContainer context)
at Microsoft.SqlServer.Configuration.InstallWizard.InstallFeatureTreeController.LoadFeatureTree()
at Microsoft.SqlServer.Configuration.InstallWizard.InstallFeatureTreeController.Initialize()
at Microsoft.SqlServer.Configuration.InstallWizardFramework.ConfigurationController.Microsoft.SqlServer.Configuration.InstallWizardFramework.ISettingStoreSite.SetSettingStore(SettingStore store)
at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardPageHost.SiteObject(Object pageController)
at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardPageHost.CreatePageController(Type type)
at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.EnsurePageControllerExists()
at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.CreateView()
at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.get_Control()
at Microsoft.SqlServer.Configuration.WizardFramework.HostControl.OnSelectedPageChanged(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.OnSelectedPageChanged()
at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.set_SelectedPageIndex(Int32 value)
at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.GoNext()
at Microsoft.SqlServer.Configuration.WizardFramework.NavigationButtons.nextButton_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
Detail.txt
2013-11-14 19:01:44 Slp: -- SkuPublicConfigObject : Calling SkuPublicConfigObject.Calculate.
2013-11-14 19:01:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2013-11-14 19:01:44 Slp: Sco: Attempting to open registry subkey Software\Microsoft\Microsoft SQL Server\100
2013-11-14 19:01:44 Slp: Sco: Attempting to get registry value SharedCode
2013-11-14 19:01:44 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2013-11-14 19:01:44 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.GESTRAVKP4030\Setup
2013-11-14 19:01:44 Slp: Sco: Attempting to get registry value ProductID
2013-11-14 19:01:44 Slp: Sco: Attempting to get registry value DigitalProductID
2013-11-14 19:01:44 Slp: -- SkuPublicConfigObject : Using edition 'Invalid' from existing instance 'GESTRAVKP4030'.
2013-11-14 19:01:44 Slp: SLP: GetDiskCostByProductFeatures: mapped to 3 target directories
2013-11-14 19:01:44 Slp: SLP: GetDiskCostByProductFeatures: Target Directory is "SYSTEMDRIVE"; Disk Cost: "121559"kb
2013-11-14 19:01:44 Slp: SLP: GetDiskCostByProductFeatures: Target Directory is "INSTALLSHAREDDIR"; Disk Cost: "132"kb
2013-11-14 19:01:44 Slp: SLP: GetDiskCostByProductFeatures: Target Directory is "INSTANCEDIR"; Disk Cost: "181258"kb
2013-11-14 19:01:44 Slp: Sco: Attempting to get directory information for path C:\Program Files\Microsoft SQL Server\
2013-11-14 19:01:44 Slp: Sco: Attempting to get directory information for path C:\Program Files\Microsoft SQL Server\
2013-11-14 19:01:44 Slp: Sco: Attempting to get directory information for path C:\Program Files\Microsoft SQL Server\
2013-11-14 19:01:44 Slp: Sco: Attempting to get directory information for path C:\Program Files\Microsoft SQL Server\
2013-11-14 19:01:44 Slp: Error: Action "GatherUserSettings" threw an exception during execution.
2013-11-14 19:01:44 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Thread was being aborted. ---> System.Threading.ThreadAbortException: Thread was being aborted.
2013-11-14 19:01:44 Slp: at System.Threading.WaitHandle.WaitOneNative(SafeHandle waitableSafeHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
2013-11-14 19:01:44 Slp: at System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
2013-11-14 19:01:44 Slp: at System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext)
2013-11-14 19:01:44 Slp: at System.Threading.WaitHandle.WaitOne()
2013-11-14 19:01:44 Slp: at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
2013-11-14 19:01:44 Slp: at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.SubmitAndWait(Request request)
2013-11-14 19:01:44 Slp: at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
2013-11-14 19:01:44 Slp: at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Waypoint(String moniker)
2013-11-14 19:01:44 Slp: at Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
2013-11-14 19:01:44 Slp: at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2013-11-14 19:01:45 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2013-11-14 19:01:45 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2013-11-14 19:01:45 Slp: --- End of inner exception stack trace ---
2013-11-14 19:01:45 Slp: at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2013-11-14 19:01:45 Slp: Received request to add the following file to Watson reporting: C:\Users\Administrator\AppData\Local\Temp\tmp5718.tmp
2013-11-14 19:01:45 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2013-11-14 19:01:45 Slp: Inner exceptions are being indented
2013-11-14 19:01:45 Slp:
2013-11-14 19:01:45 Slp: Exception type: System.ArgumentException
2013-11-14 19:01:45 Slp: Message:
2013-11-14 19:01:45 Slp: sku
2013-11-14 19:01:46 Slp: Stack:
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.InstallFeatureEdition..ctor(ServiceContainer context, SqlEdition sku, String instanceName)
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.InstallFeatureTree..ctor(ServiceContainer context)
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.InstallWizard.InstallFeatureTreeController.LoadFeatureTree()
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.InstallWizard.InstallFeatureTreeController.Initialize()
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.InstallWizardFramework.ConfigurationController.Microsoft.SqlServer.Configuration.InstallWizardFramework.ISettingStoreSite.SetSettingStore(SettingStore
store)
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardPageHost.SiteObject(Object pageController)
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.InstallWizardFramework.InstallWizardPageHost.CreatePageController(Type type)
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.EnsurePageControllerExists()
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.CreateView()
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.WizardFramework.PageHost.get_Control()
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.WizardFramework.HostControl.OnSelectedPageChanged(Object sender, EventArgs e)
2013-11-14 19:01:46 Slp: at System.EventHandler.Invoke(Object sender, EventArgs e)
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.OnSelectedPageChanged()
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.set_SelectedPageIndex(Int32 value)
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.WizardFramework.UIHost.GoNext()
2013-11-14 19:01:46 Slp: at Microsoft.SqlServer.Configuration.WizardFramework.NavigationButtons.nextButton_Click(Object sender, EventArgs e)
2013-11-14 19:01:46 Slp: at System.Windows.Forms.Control.OnClick(EventArgs e)
2013-11-14 19:01:46 Slp: at System.Windows.Forms.Button.OnClick(EventArgs e)
2013-11-14 19:01:46 Slp: at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
2013-11-14 19:01:46 Slp: at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
2013-11-14 19:01:46 Slp: at System.Windows.Forms.Control.WndProc(Message& m)
2013-11-14 19:01:46 Slp: at System.Windows.Forms.ButtonBase.WndProc(Message& m)
2013-11-14 19:01:46 Slp: at System.Windows.Forms.Button.WndProc(Message& m)
2013-11-14 19:01:46 Slp: at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
2013-11-14 19:01:46 Slp: at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
2013-11-14 19:01:46 Slp: at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
2013-11-14 19:02:13 Slp: Watson Bucket 1
Original Parameter Values
2013-11-14 19:02:13 Slp: Parameter 0 : SQL2008@RTM@
2013-11-14 19:02:13 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.InstallFeatureEdition..ctor
2013-11-14 19:02:13 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.InstallFeatureEdition..ctor
2013-11-14 19:02:13 Slp: Parameter 3 : System.ArgumentException@-2147024809
2013-11-14 19:02:13 Slp: Parameter 4 : System.ArgumentException@-2147024809
2013-11-14 19:02:13 Slp: Parameter 5 : GatherUserSettings
2013-11-14 19:02:13 Slp:
Final Parameter Values
2013-11-14 19:02:13 Slp: Parameter 0 : SQL2008@RTM@
2013-11-14 19:02:13 Slp: Parameter 1 : 0xC16B698F
2013-11-14 19:02:13 Slp: Parameter 2 : 0xC16B698F
2013-11-14 19:02:13 Slp: Parameter 3 : 0x6AD84D9E
2013-11-14 19:02:14 Slp: Parameter 4 : 0x6AD84D9E
2013-11-14 19:02:14 Slp: Parameter 5 : GatherUserSettings
2013-11-14 19:02:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2013-11-14 19:02:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2013-11-14 19:02:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131114_185940\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2013-11-14 19:02:22 Slp: sku
2013-11-14 19:02:23 Slp: Watson bucket for exception based failure has been created
2013-11-14 19:02:23 Slp: Sco: Attempting to create base registry key HKEY_LOCAL_MACHINE, machine
2013-11-14 19:02:23 Slp: Sco: Attempting to open registry subkey
2013-11-14 19:02:23 Slp: Sco: Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Installed
2013-11-14 19:02:23 Slp: Sco: Attempting to get registry value DW0200
2013-11-14 19:03:07 Slp: Submitted 1 of 1 failures to the Watson data repository
2013-11-14 19:03:12 Slp:
2013-11-14 19:03:12 Slp: ----------------------------------------------------------------------
2013-11-14 19:03:12 Slp:
2013-11-14 19:03:12 Slp: Error result: -213508975
2013-11-14 19:03:12 Slp: Result facility code: 838
2013-11-14 19:03:12 Slp: Result error code: 7313
Maybe you are looking for
-
UPDATE FAILED MESSAGE WHEN TRYING TO DOWNLOAD FROM CC DESKTOP APP.
I keep getting an 'update failed' message everytime I try to download from my CC desktop. What could this be?
-
I've had this card for a few months. When I first installed it, there were some problems with the image on the monitor: one of my monitors is too dark (I had to raise the brightness up all the way and it's still too dark), and the colors on both moni
-
Redirect not functioning on Firefox 27
I was putting up a sales page on my site and I noticed that the redirect on my page was NOT FUNCTIONING with Firefox version 27, so I downloaded Firefox version 25 and the redirect on my sales page was working with Firefox version 25. Can you look in
-
We are very pleased to announce the availability of the DMU 1.1 production release for download from OTN and My Oracle Support (MOS). For new features and changes in the new release, please see Release Notes. <br><br> Best regards, The DMU Developmen
-
ITunes freezes whilst trying to download duplicate episodes
I use home sharing. On one PC (not the PC i used to purchase the episodes) there are 2 episodes of a TV series that have already downloaded but have duplicates in the library which have not downloaded. iTunes is trying to download these duplicates.