Oracle Odbc Driver On Windows 2003 64 Bit, SQL Server 2005
Oct 24, 2006
God morning!
I 've just installed SQL Server 2005 on Windows 2003 Server 64 bit. One of my databases need to connect to seveal Oracle databases.
- I tried installing 64 bit Orcale 9 on this server. Got a strange message that the application (Oracle 64 bit) could not be installed on a 32 bit server! Strange!
- I installed Oracle 9 32 bit on the server, but I could not find ODBC driver in the Data sources! Neither the oledb under providers in MSS Manager Studio!
- Same result efter several desintall and installation. A college copied the .dll files och run a script to register the dll files. We could then se the Oracle driver in the Database sources, but we could not create any connection.
- We have even tried an 10G version of Oracle with the same result.
Is there anyone who succeeded installing Oracle on 64 bit Windows and could create odbc connection/linked server?
I have installed windows 2003 R2 64bit on one of the system, but my devlopment team pointed out that there is no odbc driver available.
I check it for odbc driver on OS cd but i do not found any relevant files/packages, can any one tell me from where I can download the ODBC driver for windows 2003 64bit OS.
I was a Oracle Developer / DBA on Unix Environments all along my career, Very recently iam starting to manage a SQL Server 2005/Windows 2003 Server setup.
Part of my new job is to automate to load Huge Data files/Flat Files (3/4 GB in size) into SQL Server 2005 DB.
Have these initial questions.. Since the files are too large to open at once... What sort of Command Line Interfaces people use on the Windows Boxes.. like doing a "wc" (Word Count) / GREP 'ng Files / Massaging Data Files one line at a time (Like using SED / AWK Commands).. Etc
Current (working) Environment within same domain: Quote: MS SQL (v8 sp3?) on windows 2000 sp3 web server on windows 2000 sp3
New (not working) Environment: Quote: MS SQL (v8 sp3?) on windows 2000 sp3 web server on windows 2003 sp3
when i try to connect to the remote sql db (the asp page code has remained unchanged), i get this error: Quote: Microsoft OLE DB Provider for ODBC Drivers error '80004005' [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
/Default.asp, line 567 line 567 is the attempt to open the connection (again, no code changes).
The ODBC reg tree has the IUSR internet guest account permissions.
When I try to create a system DSN via the ODBC manager on the current, working system, I can see a list of the SQL boxes on the network. When I try the same on the new 2003 server...our SQL server list isn't displayed.
Any ideas on why I'm getting this error in the asp page? {UPDATE} Creating a system DSN on the new 2003 server works, if the "Named Pipes" network libraries are choosen in the set up. If the TCP/IP network libraries are choosen...the connection fails. Named pipes uses port(s) 445 & 139. The TCP/IP libraries use port 1433.
Why would Named pipes work and not TCP/IP?
Thanks.
P.S. I posted this in the O/S forum, but it looks like no one browsing that forum can help on this, so it was suggested I post in the DB forum. http://forums.devshed.com/showthrea...061#post1086061
I am currently having issues getting the odbc32ad driver configured properly so I can transfer the database off of the old Oracle 7 database (currently running SCO UNIX). I have the orignal Oracle 7 disk and installed the drivers, but I am not sure what the SA login for Oracle is, nor do I know what the "Connection String" is.
Has anyone made this transfer before? Please help.
I have an application that talks to a SQL backend using an ODBC DSN connection. It works fine when running on a 32bit machine but fails in the 64bit environment. The DSN is setup properly on the 64bit box and the Test Connection returns sucess. However when my application tries to use the DSN to connect to the database I recieve the following error.
IM002 - Data source name not found and no default driver specified.
The data source name does exist, it's in the ODBC.INI and in registry. As mentioned above the Test Connection succeeds in the ODBC Administrator so logic would dictate that it's setup correctly.
Please help share with me if you know the version compatibility matrix of Ms SQL Server, ODBC driver (sqlsrv32.dll), Driver Manager (odbc32.dll) and ODBC API spec. For instance, how can I know Ms SQL Server 2000 can work with which version of sqlsrv32.dll, a particular version of sqlsrv32.dll can work with which version of odbc32.dll and a certain version of sqlsrv32.dll/odbc32.dll conforms to which version of ODBC API spec (e.g. 3.5).
Hi everybody I have installed SqlServer 2005 on my server but my Windows application on the client computers should connect to server via ODBC connection so what should i install on the client computers (that don't have any sql server installed) to enable them to connect? When i want to create ODBC connection on client computers through (Control panelAdministrative ToolsData Sources) i don't see SQL-Server 2005 ODBC driver in the list ....could anyone help me? Kind Regards.
Does the x64 version of SQL Server 2005 June CTP contain 64-bit versions of the SQL Server ODBC Driver and the OLE DB Provider? I am not interested in the .NET Managed Provider here, just the legacy ODBC and OLE DB drivers, and only 64-bit versions of those.
Now I'm trying to run PHP web application on x64 2003 Server with Microsoft SQL Server 2005. The version of PHP is 5.2.3. and the web application should be run as 64bit applications. Since there seems no way to use php_mssql.dll on the environment, I'm trying to use SQL Server 2005 Driver for PHP but when PHP loads php_sqlsrv.dll, an error has occurd and there's a following message in an error log...
PHP Warning: PHP Startup: Unable to load dynamic library 'c:phpextphp_sqlsrv.dll' - %1 is not a valid Win32 application
From this message, I thought the distributed libraries for Windows would be for a Win32 environment but there seemed no information that says the libraries run on Win32 environment only.
I have an Application developed on ASP, I got a few new servers 64bits, I installed microsoft WIN 2003 SR. When I get in into the web site I receive this errors:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
/ConnectToDatabase.asp, line 17
I made some obvios checks, I checked that the ODBC really exists and we move the IIS 6.0 to run in 32bits mode as I found in some page.
I am using MFC ODBC classes in my VC++ application for database accesss (on a SQL Server 2005 Database). After opening a Recordset I have to use the CRecordset::GetFieldValue( LPCTSTR lpszName, CDBVariant& varValue, short nFieldType = DEFAULT_FIELD_TYPE ) method of the CRecordset object to obtain field values. The above method works fine with ODBC drivers for Jet but when I use ODBC for SQL Server it throws the following exception.
State:S1002,Native:0,Origin:[Microsoft][ ODBC SQL Server Driver] Invalid Descriptor Index
I don't understand why the Microsoft SQL Server ODBC Driver is throwing this exception.
I've got a Windows Server 2003 for Small Business Server. It had got SQL installed. But then SQL was uninstalled. Now I need to put SQL back in, but I don't see how!
There're three CD-Rom but I don't see how and from which CD to install back SQL.
PS: Correct me if I'm wrong, Windows Server 2003 is sold with SQL 2005, right?
I'm unable to successfully install SQL 2005 on Windows Server 2003. Everything installs correctly except 'SQLXML4', and after installation, there's no Management Studio, unless I then install SQL Express Management Studio.
Installation details: Successfully installs 'Native Client' and the 'Support Files'. The 'System Configuration Check' passes everything. Installed 'Database Services', 'Integration Services', 'Client Components' (except for the 2 development tools), and 'Books Online'. Created the default instance (there were no other instances). Set it to run as 'Local System'. Set only the 'SQL Server' service to start after setup. Specified 'Mixed Mode'.
Then the installation proceeds, and everything looks good until SQLXML4 fails. Soon after, a window pops up saying "Setup is preparing to continue with the installation". Nothing happens till I click 'OK', and then 'Workstation Components' shows as having failed. Then the installation finishes normally. However there's no Management Studio, except that I then installed the SQL Express Management Studio, which appears to work fine.
I tried uninstalling, and installing again, but got the same results.
Hello!I'm migrating an IIS/SQL-Server application from Windows NT4.0 and SQL-Server 2000 to Windows 2003 Server and SQL-Server 2005.My problem is that it is not possible to connect local (IIS and SQL-Server 2005 are runnng on the same node) using ODBC. Running theapplikation on a remote IIS (XPPro) all works fine. I can't see anydifferences in the ODBC-configuration.Any idea?Thanks
I get and error when installing MS SQL 2005 on Windows 2003 server with SP2. It bombs at the very end of the install and Microsoft notification program generated he message below to be sent to Microsoft. Please help. At a stand still. ------------------------------------------------------------------------------------------------------------------- EventType : sql90setup P1 : unknown P2 : 0x645 P3 : unknown P4 : 0x645 P5 : unknown P6 : unknown P7 : sqlserver2005_bc.msi@
Below is the summary.txt -------------------------------------
Microsoft SQL Server 2005 9.00.1399.06 ============================== OS Version : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790) Time : Thu Feb 28 22:52:28 2008
Machine : ESAPPS Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_1.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : Microsoft SQL Server Native Client Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_1.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_1.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : MSXML 6.0 Parser Product Version : 6.00.3883.8 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_1.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_2.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : Microsoft SQL Server Native Client Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_2.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_2.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : Microsoft SQL Server VSS Writer Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SqlWriter_1.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : MSXML 6.0 Parser Product Version : 6.00.3883.8 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_2.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLSupport_3.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : Microsoft SQL Server Native Client Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLNCLI_3.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : Microsoft Office 2003 Web Components Product Version : 11.0.6558.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_OWC11_3.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : Microsoft SQL Server 2005 Books Online (English) Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_BOL_1.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : MSXML 6.0 Parser Product Version : 6.00.3883.8 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_MSXML6_3.log -------------------------------------------------------------------------------- Machine : ESAPPS Product : SQLXML4 Product Version : 9.00.1399.06 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_ESAPPS_SQLXML4_1.log -------------------------------------------------------------------------------- SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
I cannot make named pipe connection with client by ODBC DSA. Here is information. Refering to http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1. [1] Client side: 1. What is the connection string in you app or DSN? (please specify) ODBC \[SERVER_NAME]pipesqlguery 2. If client fails to connect, what is the client error messages? (please specify) Connection failed: SQLState: €™01000€™ SQL ServerError: 1326 [Microsoft][ODBC SQL Server Driver][Named Pipes]connectionOpen (Connect()) Connection failed: SQLState: €™08001€™ SQL Server Error: 17 [Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or access denied. 3. Is the client remote or local to the SQL server machine? [Remote | Local] 4. Can you ping your server? [YES | NO ] In cmd.exe console, type €œping -a <server_name>€?. 5. Can you telnet to your SQL Server? [YES | NO, please specify the error message ] In cmd.exe console, type €œtelnet <server name> port, where port can be 135, 445 or sql_server_tcp_port. If your cmd.exe console turns into a complete black screen with a cursor flushing on top left corner, you are connected. Type ctrl+€™[€˜ to bring up telnet prompt and type €œquit€? <enter>. 6. What is your client database provider? [SNAC | MDAC | ADO.NET1.0 | ADO.NET2.0| other ODBC (please specify] Or/And, what is your client application? [SQL Management Studio | SQL Profiler | Visual Studio | Other (please specify). 7. Is your client computer in the same domain as the Server computer? (Same domain | Different domains | WorkGroup) 8. What protocol the client enabled? [Shared Memory | TCPIP | Named Pipes]. 9. Do you have aliases configured that match the server name portion of your connection string? If so, please check if it is correct. You can use cliconfg.exe (SS 2000) or SQL Server Configuration Manager (SS 2005) to configure the alias. [NO] 10. Do you select force encryption on server and/or client? [NO]
I was able to connect with TCP/IP settings. [2] Server side: 1. What is the MS SQL version? [SQL Server 2005] 2. What is the SKU of MS SQL? [Enterprise | Standard | Workgroup | Express (or MSDE) | other (please specify)]. 3. What is the SQL Server Protocol enabled? [Shared Memory | TCPIP | Named Pipes ]. Use SQL Server Configuration Manager to configure it and check ERRORLOG or event log to confirm. 4. Does the server start successfully? [YES | NO] If not what is the error messages in the SQL server ERRORLOG? 5. If SQL Server is a named instance, is the SQL browser enabled? [YES | NO] 6. What is the account that the SQL Server is running under?[Local System | Network Service | Domain Account] 7. Do you make firewall exception for your SQL server TCP port if you want connect remotely through TCP provider? [YES | NO | not applicable | not enabled] 8. Do you make firewall exception for SQL Browser UDP port 1434? In SQL2000, you still need to make firewall exception for UDP port 1434 in order to support named instance.[YES | NO | not applicable | not enabled]
I could connect locally with named pipes. Do I have to make some file shares manually? [2a] Tool Used to Connect What tool or Application are you using to connect to SQL Server (eg: Visual Studio, SQL Server Management Studio, SQLCmd.exe, OSQL, etc) and especially the version of SQL Server (Express, Workgroup, Standard, Enterprise, Developer) [3] Platform: 1. What is the OS version? [Windows XPSP2 | Windows 2003 | Windows 2000 | Windows 98 | others (please specify ) ]. 1. Server [Windows Server 2003 R2] 2. Client [Windows XP SP2] 2. Do you have third party antivirus, anti-spareware software installed? [Symantec | Norton | other (please specify) ½ NO].
[4] Misc: 1. If you have certificate configuration issue: Please use €œcertutil.exe €“v €“store my€? to dump certificate specific info and post it in your question. [NO]
I am trying to install SQL 2005 in a 2-node virtual Windows 2003 cluster. I set the cluster up through Virtual Server 2005 with 2 virtual nodes and one virtual domain. The nodes can connect to each other as well as the physical machine. When I try to install a fresh copy of SQL 2005 on my cluster, I get an error every time. The error stops the installation while checking system configuration after installing prerequisites. The log file entry is as follows:
******************************************* Setup Consistency Check Report for Machine: --SERVERNAME-- ******************************************* Article: WMI Service Requirement, Result: CheckPassed Article: MSXML Requirement, Result: CheckPassed Article: Operating System Minimum Level Requirement, Result: CheckPassed Article: Operating System Service Pack Level Requirement, Result: CheckPassed Article: SQL Compatibility With Operating System, Result: CheckPassed Article: Minimum Hardware Requirement, Result: CheckPassed Article: IIS Feature Requirement, Result: Warning Description: IIS is not installed, therefore Report Server feature will be disabled Action: Install IIS in order for Report Server feature to be enabled Article: Pending Reboot Requirement, Result: CheckPassed Article: Performance Monitor Counter Requirement, Result: CheckPassed Article: Default Installation Path Permission Requirement, Result: CheckPassed Article: Internet Explorer Requirement, Result: CheckPassed Article: Check COM+ Catalogue, Result: CheckPassed Article: ASP.Net Registration Requirement, Result: CheckPassed Article: Minimum MDAC Version Requirement, Result: CheckPassed <Func Name='PerformDetections'> 1 Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.1399.0 Error: Action "InvokeSqlSetupDllAction" threw an exception during execution. Error information reported during run: Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "ComputerList" {"SqlComputers", "", ""} in cache Source File Name: datastoreclusterinfocollector.cpp Compiler Timestamp: Fri Sep 16 13:20:12 2005 Function Name: ClusterInfoCollector::collectClusterVSInfo Source Line Number: 883 ---------------------------------------------------------- Failed to detect VS info due to datastore exception. Source File Name: datastoreclustergroupsproperties.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: ClusterGroupScope.SharedDisks Source Line Number: 56 ---------------------------------------------------------- Failed to find a cluster group that owned shared disk: J: WinException : 2 Error Code: 0x80070002 (2) Windows Error Text: The system cannot find the file specified. Source File Name: datastoreclustergroupsproperties.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: ClusterGroupScope.SharedDisks Source Line Number: 56
Hello, we currently have our database (MSSQL 2005) on our web server however to do increased traffic and business we are now moving our database to its own server. I was wondering if anyone here knew of some good ways to setup/tune Windows Server 2003 and SQL 2005 for best performance. MSSQL will be the only application running on the server and want to make sure it is as fast as possible! Thanks in advance!!!
Hello - We have been unable to successfully install Integration Services with an instance of SQL 2005 running on a Windows Small Business Server 2003. Installation proceeds with no errors, but when you attempt to connect to the Integrations Services and browse to where it apparently exists, the SQL Server Managment Studio returns the following error:
TITLE: Connect to Server ------------------------------
I'm a new developer to both SQL Server 2005 & Windows 2003, so forgive me if this question seems a little too basic. I'm coming from a Oracle and UNIX background.
I've create a stored procedure in SQL Server 2005. I now want to execute this from the command line in Windows 2003. Eventually, I want our UNIX scheduler, autosys (which runs on a different UNIX machine obviously) to be able to execute this. In my old environment, I created a UNIX shell script as a wrapper let's say 123.sh. This shell script would accept as a parameter the name of the stored procedure I wanted to execute. If this stored procedure also had parameters it needed to be passed to it, I would have strung these values out in the command line in UNIX. Two examples of how the command line in UNIX I used to execute the Oracle stored procedure might look are listed below.
This way anytime I created a new stored procedure, I could reuse the shell script wrapper 123.sh and just pass in the name of the newly created stored procedure and any parameters it needed.
How can I accomplish this same type of functionality in the SQL Server 2005/Windows 2003 environment.
I have installed SQL 2005 (X64) on 64-bit Windows 2003 server (AMD). One of my databases need to connect several Oracle databases on 32 bit servers.
I managed to install Oracle 32 bit Client (was unsuccessful with 64 bit installation) and could set up the odbc (32). But I coul'nt find Oracle under linked servers!
I am having major performance issues with Microsoft SQL 2005 x64 Standard Editions performance on Windows Server 2003 x64. The PC has two quad core cpu's with 8gb of ram and running a 500gb mirrored SCSI (Raid 1) drive system. The database running on the server is about 11gb. I've run a defrag several times which helps a little but I was hoping I could do something else to increase the performance.
I have also found that the bottle neck in the SSIS package is the backup and restore process of an 11gb database which takes about 1 hour (backup takes 1 hour and restore takes 1 hour) when it should take about 11 minutes. Is there anything I can do to make these processes run faster or to find out why they are taking so long? Any ideas would be a great help.
I am testing SQL 2005 Standard (32 bit) on a Windows 2003 Server 64 bit with 8GB of RAM? Should I enable the AWP Setting or not and should I change the maximum server memory (currently saying 2GB)?
Hi all,I just asked some people to help me out and phone microsoft with thefollowing information, kindly they refused unless we setup a supportcontract with them first, for pre-sales information. (That really doesnot sound like good business sense to me - anyway here is our problem,if anyone could help thanks)."To tell and ask microsoft:We will be setting up a microsoft sql server 2000 instance running on awindows 2003 server.1) We need to check this can run alongside a microsoft 2003 sql server(either workgroup or standard edition), on the same machine. Are thereany .dll clashes if we do this? If there are can we run SQL Server2000, in a virtual machine running windows 2000 professional. (I have alicenced copy we can use for this).2) If we run one instance of 2000, and one of 2003 of the sql servers,can one use the processor licence model, and one use the CAL licencemodel."Thanks for any help, and any idea why they actually force you to usenews groups for pre-sales information?David
Windows 2003 Server and all client PCs are all on the same network. I installed SQL 2005 std version on windows server 2003 and created a database and tables in it.
I have two users, who want to connect to SQL server 2005 from their PCs (they have windows XP):
These are two things that I need to facilitate:
1) They want to be able to write queries using Query Designer and run from their PCs.
2) I created an MS Access database on my PC, I want to use Access database as a front end to the SQL server database. I will create queries, forms in Access DB, and I want to be able to get the data from SQL server Database to do this. I guess I can use ODBC to connect to tables in SQL server database.
3) I want to connect SQL server to Oracle database, and run oracle stored procedures. I want to load the results of oracle stored procedures into SQL server database tables. I guess I will use IIS for this.
Any suggestions are appreciated, especially with item number 1.
SQL Server Reporting Services 2005 Service would not Start on windows server 2003. Working great till yesterday and no changes were made to config file.
Here is the error in Event log
Event Type: Error Event Source: SQL Server Report Service Event Category: None Event ID: 0 Date: 12/13/2007 Time: 8:25:59 AM User: N/A Computer: XXXXXXXXXXX Description: Service cannot be started. Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information. at Microsoft.ReportingServices.Library.ServiceAppDomainController.Start(Boolean firstTime) at Microsoft.ReportingServices.NTService.ReportService.OnStart(String[] args) at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Here is i found in log files ReportingServicesService!resourceutilities!4!12/13/2007-08:25:59:: i INFO: Running on 0 physical processors, 1 logical processors ReportingServicesService!servicecontroller!4!12/13/2007-08:25:59:: e ERROR: Exception caught loading and setting code permissions policy level: System.Security.XmlSyntaxException: Invalid syntax on line 158. at System.Security.Util.Parser.GetRequiredSizes(TokenizerStream stream, Int32& index) at System.Security.Util.Parser.ParseContents() at System.Security.Util.Parser..ctor(Tokenizer t) at System.Security.SecurityManager.LoadPolicyLevelFromStringHelper(String str, String path, PolicyLevelType type) at System.Security.SecurityManager.LoadPolicyLevelFromString(String str, PolicyLevelType type) at Microsoft.ReportingServices.Library.ServiceController.SetAppDomainPolicy() ReportingServicesService!servicecontroller!4!12/13/2007-08:25:59:: e ERROR: Error Starting Service: System.Security.XmlSyntaxException: Invalid syntax on line 158. at System.Security.Util.Parser.GetRequiredSizes(TokenizerStream stream, Int32& index) at System.Security.Util.Parser.ParseContents() at System.Security.Util.Parser..ctor(Tokenizer t) at System.Security.SecurityManager.LoadPolicyLevelFromStringHelper(String str, String path, PolicyLevelType type) at System.Security.SecurityManager.LoadPolicyLevelFromString(String str, PolicyLevelType type) at Microsoft.ReportingServices.Library.ServiceController.SetAppDomainPolicy() at Microsoft.ReportingServices.Library.ServiceController.StartService(Boolean firstStart)
