Issues while readin SQL server via ODBC connection

Hi Experts,
I havea SQL server db as a source. I have configured the Datastore using ODBC connection. Developed a job which simply reads a table and populates into a flat file. when we run the job, it doesnt show any progress, it just stops after a log message "initializing data store, processing job" . I looked at the job logs file on the Job server, its incomplete as well.
One thing is that, im able to see the data when i go under data store and view data option for that particular table. My other jobs works just fine with oracle data base sources. We restarted the BODS server as well, but it doesnt help. Any idea on what might be going on ?.
Thanks for your time.
Regards,
Narayanan

Hi Narayanan ,
There are two steps:
1) Set up the ODBC connection correctly on your Linux server
http://wiki.sdn.sap.com/wiki/display/EIM/ToconfigureDataDirectODBConLinuxand+Unix
(test with isql command line if connection on that server to the SQL Server is working)
2) Select ODBC connection in the datastore and then put the name of the connection you defined. (do not choose Database - SQL Server)
Norbert

Similar Messages

CR2011, BO 4.0, connection to SQL server via ODBC

Hi,
when developing reports locally using Crystal Reports 2011 I dont' have problems connecting to our MS SQL Server using ODBC. However, as soon as the report is exported to our BO Edge 4.0 SP2 server I get this error message when viewing the report in Launchpad (or CMC) and refreshing it:
"The viewer could not process an event. Failed to open the connection. CRWEB00000119"
In CMC I then entered the credentials for this report but I still get the error message.
So I created a new ODBC connection on the BO server pointing to the SQL server - but I can't specify this ODBC connection in CMC.
Any hints?
Thanks!

BOE 4.0 is 64 bit but some parts connect through 32 bit DB clients. So it would need both the 32 and 64 bit SQL Server 2000 client's installed. Not sure if MS had a 64 bit client for 2000 so likely the problem.
CR 2011 is a 32 bit app so that explains why it works on your PC.
I would or suggest you post to the BOE Admin forum but because it's SQL 2000 I doubt they'll be able to help.
All I can suggest it to upgrade SQL Server to SQL 2005 or 2008, 2008 has a bunch of new security settings/configurations so it takes a little more time to configure and grant rights to DB's but it will work. Also required is the use of and set location to the SQL Native Client 10 Client Tools to be installed and update all of your reports to use it also.
Don

Using SQL queries via ODBC connection to obtain data for a report

Post Author: adhiann
CA Forum: General
Hi All,
I was trying to run a Crystal Reports report through Clearquest using an SQL query I designed in CQ to give me the data I need, however, from within ClearQuest, I cannot associate an SQL query on a report, so I went directly to Crystal Reports and am using the ODBC connection to the ClearQuest database to run the report. I selected the right tables and fields and am using the same formula that I used on ClearQuest's SQL query to get the data, however, the report doesn't return any data whereas I am getting at least 5 records from Clearquest for the same query.
Granted there's a difference in the way you create a SQL formula in Crystal, but I don't know if I'm doing it right as I've never had to use CR as a standalone product.
Is there a way I can directly plug my ClearQuest's SQL query into the CR and run it? I don't know why the results won't return any data for a query that has some results
Thanks in advance
nandita

Post Author: Roscoe1822
CA Forum: General
Did you try to add a command through the Database Expert? Also creating a Business View that contains your sql query might help as well.

Problem with Connection to SQL Server via Servlet (in iPlanet 6 App Server)

Hi ,
I am using the iPlanet ApplicationServer 6.0 SP2 for development & testing of an internet application.
I am facing a problem when I am trying to connect to MS SQL SERVER via the native jdbcodbc driver (obdc32.dll). The error is something like this :
[26/Jul/2001 11:50:35:7] warning: DriverConnect: (28000): [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user '\'.(DB Error: 18456)
[26/Jul/2001 11:50:35:7] warning: ODBC-027: CreateConn: failed to create connection [new connection]: DSN=fadd,DB=cashbook,USER=test,PASS=xxxxxxxxx
[26/Jul/2001 11:50:35:7] error: DATA-108: failed to create a data connection wit
h any of specified drivers
Error in connecting to the Database for cirrus :java.sql.SQLException: failed to
create a data connection with any of specified drivers
java.sql.SQLException: failed to create a data connection with any of specified
drivers
at com.netscape.server.jdbc.Driver.afterVerify(Unknown Source)
at com.netscape.server.jdbc.Driver.connect(Unknown Source)
at com.netscape.server.jdbc.DataSourceImpl.getConnection(Unknown Source)
at gefa.util.DBConnection.jdbcConnectionOpen(DBConnection.java:65)
at gefa.servlet.ServUpload.doPost(ServUpload.java:45)
at gefa.servlet.ServUpload.doGet(ServUpload.java:29)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at com.netscape.server.servlet.servletrunner.ServletInfo.service(Unknown
Source)
at com.netscape.server.servlet.servletrunner.ServletRunner.execute(Unkno
wn Source)
at com.kivasoft.applogic.AppLogic.execute(Unknown Source)
at com.kivasoft.applogic.AppLogic.execute(Unknown Source)
at com.kivasoft.thread.ThreadBasic.run(Native Method)
at java.lang.Thread.run(Thread.java:479)
I have configured a DSN with the name "fadd" on the machine with the application server and it used NT authentication. I have supplied an NT userid and password that has appropriate rights on the database "cashbook".
When I write a java standalone program, it does connect but via a servlet it does not connect.
Can some guide me with this problem please ?
Anything one might have observed in the past ? (may be specific to iPlanet ?)
Thanks a lot in advance
~Sunil

I'm using iPlanet App server as well and experiencing similar problem. I load my SQL Server driver by Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver"), then use DriverManager.getDriver() to obtain the Driver.
However, the Driver returned is not the SQLServerDriver as expected. The Driver returned is com.netscape.server.jdbc.Driver! And then when I do Driver.getConnection("jdbc:microsoft:sqlserver://MyServer"), it throws an SQLException saying that it doesn't accept a jdbc:microsoft:sqlserver subprotocol. Well, of course it doesn't, it's not a microsoft Driver at all.
I suspect the problem is that the netscape Driver's acceptsURL() method ALWAYS returns true in iPlanet app server, thus when you getDriver(), the netscape Driver is always returned (and always returned as the first one since it's default?). Thus even though the same piece of code works fine as a standalone application, it just doesn't work on iPlanet app server.
My work around is:
Class.forName("my.Driver");
Enumeration enu = DriverManager.getDrivers();
Driver useThis = null;
while (enu.hasMoreElements()) {
Driver d = (Driver)enu.nextElement();
if (d.getClass().toString().indexOf("my.Driver") > -1) {
useThis = d;
Mind that my above code does not have an performance issue. If you look into the source code of how DriverManager get a Driver for a particular URL, it also loads the whole set of available Drivers, then call acceptsURL() method on each of them to find the first "suitable" one. Thus time complexity is the same.
I know this is not a very elegant solution and it defeats the purpose of having a DriverManager. Does any one else has a better way to solve this problem, like a way to specify the priority of each Driver so that SQLServerDriver is returned before the netscape Driver?
Thanks a lot.

Error when connecting to SQL*PLUS via ODBC to Excel

OS: Windows 2000 Professional
Oracle DB: 9i release 2
SQL*Plus: Release 9.2.0.1.0
MS Excel: 2000
===================
When I try to connect to SQL*PLUS via ODBC to Excel with "connect scott/tiger@odbc:libro" I get the following error:
ORA-03121: no interface driver connected - function not performed

SQL Server objects are commonly case sensitive, so please surround the column and table names by double quotes:
SELECT "Type_PK_ID" FROM "dbo"."boundaries"@sqlserver
SIDE NOTE: Oracle is by default not case sensitive and all object names are stored in upper case. To get case sensitive objects they need to be surrounded by double quotes. In HSODBC case sensitive table names were commonly found even when not surrounded by double quotes as the gateway used internal SQL Server methods to find the correct table nameing - this method does not work for column names. So to be able to query a case sensitive column it needs to be surrounded by double quotes and the table name must be written as stored in the source database.

Inserting data to a . SDF database (SQL Server Compact Edition connection)

Hi, all.
I'm working on a project that worked fine while connecting to SQL Server 2008. I used a connection string like this:
Driver={SQL Server Native Client 10.0};Server=myServerAddress;Database=myDataBase;Uid=myUsername;Pwd=myPassword;
Now, I've replaced all database connections in my project to work with SQL Server Compact Edition, and my connection string is something like this:
Provider=Microsoft.SQLSERVER.CE.OLEDB.3.5;Data Source=myDir\myDataBase.sdf;
After changing the type of connection, I'm getting an error on "DB Tools Insert Data.vi". This is what I get:
Error -2147217872 occurred at NI_Database_API.lvlib:Cmd Execute.vi->NI_Database_API.lvlib: DB Tools Insert Data.vi->Main.vi
Possible reason(s):ADO Error: 0x80040E30 Exception occured in Microsoft SQL Server Compact OLE DB Provider: The given type name was unrecognized. [,,,,,] in NI_Database_API.lvlib:Rec Create - Command.vi->NI_Database_API.lvlib:Cmd Execute.vi->NI_Database_API.lvlib: DB Tools Insert Data.vi->Main.vi
This is a simplified block diagram (as I said, it worked perfectly while using SQL Server 2008 connection):
Could you please help me?
Thanks in advance,
Francisco

Hi, Steve. Thanks for your answers.
I worked around this problem by using directly a SQL query instead of this function (you were right, using DBTools Execute Query VI). But now I'm getting problems with other functions, when inserting data into the DB including NULL values.
I make a SQL query like this using DBTools Execute Query VI:
INSERT INTO Table1 (Column1, Column2, Column3, Column4, Column5, Column6) VALUES ('Value1', 'Value2', 'Value3', 'NULL', 'Value5', 'Value6')
and get the following error:
ADO Error: 0x80040E07Exception occured in Microsoft SQL Server Compact OLE DB Provider: A literal value in the command could not be converted to the correct type due to a reason other than data overflow. [,,,,,] in NI_Database_API.lvlib:Conn Execute.vi->INSERT (new) restricción (DBCT).vi->Restricciones a Base de Datos (DBCT).vi->Definir - editar restricciones.vi->Main.vi
The same SQL query worked perfectly when using the SQL Server 2008 connection, so it's not a database structure issue.
Could somebody please help me?
Regards,
Francisco

The unattended installation failed while installing SQL Server 2008 R2 ????

Hi gurus,
I got an error while installing SQL Server 2008 R2 in Windows 2008 R2 standard 64 bit operating system.
LOG file*
Customized installation of SQL Server 2008R2 for SAP *
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlWriter_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Full-Text Search
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Client Tools Connectivity
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Management Tools - Complete
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Client Tools SDK
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Client Tools Backwards Compatibility
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
Configuration status:          Passed
Feature:                       Business Intelligence Development Studio
Status:                        Failed: see logs for details
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_common_core_Cpu64_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SqlBrowser_Cpu32_1.log
MSI error description:
MSI status:                    Failed: see details below
MSI error code:                0x1639
MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\sql_tools_Cpu64_1.log
MSI error description:
Configuration status:          Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20120116_221104\SystemConfigurationCheck_Report.htm
1/16/2012 10:13:34 PM
Message Box "Installation failed"
The unattended installation failed.
Installation Step: The unattended installation failed.
Return Code:       -2068052377
Log File:          C:\Windows\SQL4SAP.log
Check the log file above.
See SAP note 1144459 for known issues.
Result: vbOK
Registry settings (2/2):
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
WRITE(REG_DWORD): 4
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{2b9034f3-b661-4d36-a5ef-60ab5a711ace}
WRITE(REG_DWORD): 4
1/16/2012 10:37:32 PM
Quit script with return code 1
Please help me out with this issue.
REGARDS,
Raj

Hello Raj,
MS SQL DB installation specific steps for SAP system is clearly documented in SAP Installation guide. Please download from SMP, read it carefully and install as mentioned in the guide.
Hope it helps.
Thanks,
Siva Kumar

To Restrict SQL account from accessing Sql server via SSMS

Hi All,
We are planning to tighten the security of our SQL Server.
In the initial phase, we want to restrict all the SQL accounts(except sa) from accessing SQL Server via SSMS
Since the SQL passwords are used in the connection strings(plain text) of our .NET Applications, developers are able to see it and they are accessing SQL server through SSMS with the credentials in the connection string.
The requirement is, SQL accounts should only be accessing the databases through .NET applications and not through any other applications like SSMS, SQLCMD...etc
1) We tried "Logon Trigger", but later we came to know that there is security breach in it.
2) Application Roles - Password is plain text, again back to square one.
We are looking for an alternate. Please share some ideas.
Thanks & Regards,
K.P.Senthil Kumar

The basic presumption here is that there is on way you can tie a connection to an application as such. There is app_name(), but since this is passed from the application, the application can call itself whatever you want.
As long as it is only a matter of keeping business users out, you can solve the issue with some three-tiered solution. Either by having a true middle layer, or just having a web server, or the application running on Terminal Server or Citrix.
But you want to keep the developers out who work with the code. That makes it difficult to lock them out of the middle layer.
Then again, you say "our SQL Server" is that singular? Don't you have more than one SQL Server? One for developement, one for test and one for production? If you only want to keep the devs out from development, you have different usernames
and password for different environments, and they are read from config files. The config files for production should be well-protected.
By the way, only permitting sa from logging in from SSMS is bad idea. Rather, you should disable sa, and everyone should log in with their individual Windows account. And those who should perform system-administration tasks should be member of sysadmin.
Erland Sommarskog, SQL Server MVP, [email protected]

Error while installing SQL Server 2012 X64 SP2,

Error while installing SQL Server 2012 X64 SP2,
When I installed the SQL Server 2012 X64 SP1, I got the attached error.
What might be the issue here?
Thank you
Best
Jamal

Hello,
Are you trying to install SQL Server on a compressed or encrypted drive? SQL Server won’t install on a drive/folder with these attributes.
Are you trying to install SQL Server on a ReFS file system? It is not supported on SQL Server 2012.
Disable any security/antivirus software and download the media again. Mount the media (.ISO file) and try to install again.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SETUP ERROR WHILE INSTALLING SQL SERVER 2008 R2

Hi ,
I'm coming across the following error while installing Microsoft SQL Server 2008R2
SQL Server Setup has encountered the following error:
The required MSI package 'D:\SQL Sever 2008 R2 Developer Edition\x86\setup\sql_engine_core_shared_msi\sql_engine_core_shared.msi' doesn't exist.
Error code 0x84B20001.
I tried reinstalling the same. But results the same.
Please suggest. :)

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):           -2068709375
Exit facility code:            1202
Exit error code:               1
Exit message:                  The required MSI package 'D:\softwares\SQL Sever 2008 R2 Developer Edition\x86\setup\sql_engine_core_shared_msi\sql_engine_core_shared.msi'
doesn't exist.
Start time:                    2013-12-31 20:47:50
End time:                      2013-12-31 20:55:44
Requested action:              Install
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131231_204629\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.50.1600.1%26EvtType%3d0xD2FD83B3%400xC2B0B50B%401202%401
Machine Properties:
Machine name:                  SAMPLE-PC
Machine processor count:       2
OS version:                    Windows 7
OS service pack:
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 2005
Tools                                    1033
Express Edition      9.2.3042        No
Sql Server 2005
ToolsClient                              1033
Express Edition      9.2.3042        No
Sql Server 2005
ToolsClient\Connectivity                 1033                 Express Edition
9.2.3042        No
Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             Database Engine Services
1033                 Express Edition      10.1.2531.0     No
Sql Server 2008      SQLEXPRESS           MSSQL10.SQLEXPRESS             SQL Server Replication
1033                 Express Edition      10.1.2531.0     No
Package properties:
Description:                   SQL Server Database Services 2008 R2
ProductName:                   SQL Server 2008 R2
Type:                          RTM
Version:                       10
SPLevel:                       0
Installation location:         D:\softwares\SQL Sever 2008 R2 Developer Edition\x86\setup\
Installation edition:          DEVELOPER
User Input Settings:
ACTION:                        Install
ADDCURRENTUSERASSQLADMIN:      False
AGTSVCACCOUNT:                 TEST
AGTSVCPASSWORD:                *****
AGTSVCSTARTUPTYPE:             Manual
ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10_50.TEST\OLAP\Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS10_50.TEST\OLAP\Config
ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS10_50.TEST\OLAP\Data
ASDOMAINGROUP:                 <empty>
ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS10_50.TEST\OLAP\Log
ASPROVIDERMSOLAP:              1
ASSVCACCOUNT:                  TEST
ASSVCPASSWORD:                 *****
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            SAMPLE-PC\SAMPLE
ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS10_50.TEST\OLAP\Temp
BROWSERSVCSTARTUPTYPE:         Automatic
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131231_204629\ConfigurationFile.ini
CUSOURCE:
ENABLERANU:                    False
ENU:                           True
ERRORREPORTING:                False
FARMACCOUNT:                   <empty>
FARMADMINPORT:                 0
FARMPASSWORD:                  *****
FEATURES:                      SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,SSMS,ADV_SSMS
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD:                 *****
HELP:                          False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS:              False
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files\Microsoft SQL Server\
INSTALLSQLDATADIR:             <empty>
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    TEST
INSTANCENAME:                  TEST
ISSVCACCOUNT:                  TEST
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
NPENABLED:                     0
PASSPHRASE:                    *****
PCUSOURCE:
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
ROLE:                          <empty>
RSINSTALLMODE:                 DefaultNativeMode
RSSVCACCOUNT:                  SAMPLE-PC\TEST
RSSVCPASSWORD:                 *****
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  <empty>
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT:                 TEST
SQLSVCPASSWORD:                *****
SQLSVCSTARTUPTYPE:             Automatic
SQLSYSADMINACCOUNTS:           SAMPLE-PC\SAMPLE
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  False
TCPENABLED:                    0
UIMODE:                        Normal
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20131231_204629\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Full-Text Search
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Analysis Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Reporting Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Integration Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Connectivity
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Complete
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Management Tools - Basic
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools SDK
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Client Tools Backwards Compatibility
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Feature:                       Business Intelligence Development Studio
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\20131231_204629\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: Microsoft.SqlServer.Chainer.Infrastructure.ChainerInvalidOperationException
    Message:
        The required MSI package 'D:\softwares\SQL Sever 2008 R2 Developer Edition\x86\setup\sql_engine_core_shared_msi\sql_engine_core_shared.msi' doesn't exist.
    Data:
      ChainerInvalidOperationExceptionData = InstallPackage
      DisableWatson = true
    Stack:
        at Microsoft.SqlServer.Configuration.SetupExtension.MsiInstallEngineActionBehavior.ModifyAction(String installedProductCode, String installedProductVersion, String pathOfPackageOnMedia, InstallAction pkgAction)
        at Microsoft.SqlServer.Configuration.SetupExtension.MSIInstallerEngine.InstallPackage(PackageId pkg, InstallAction pkgAction)
        at Microsoft.SqlServer.Configuration.MsiExtension.PackageInstallAction.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)

Getting error while installing sql server std 2008 R2 on win 7 prof. sp1 64bit

Hi,
I am getting error while installing sql server std 2008 R2 on win 7 prof. sp1 64bit. I have already tried all option but fail to installation
an error during the installation of assembly micro soft.vc80.crt

Hi,
I am getting error while installing sql server std 2008 R2 on win 7 prof. sp1 64bit. I have already tried all option but fail to installation
an error during the installation of assembly micro soft.vc80.crt
Can you please post summary.txt file here.Below link will help you in finding it.
http://technet.microsoft.com/en-us/library/ms143702(v=sql.105).aspx
Also with error you posted I guess it is a known issue .You need to install below package and then continue with fresh installation
http://www.microsoft.com/en-gb/download/details.aspx?id=15336
Please make sure before beginning fresh installation you make sure previous failed installation is removed completely.Use add remove program to remove failed SQL Server.If yu still face issue please post summary.txt file here
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Error while installing SQL Server 2008 R2 in Windows 7 SP1 machine

Hi Team,
Error while installing SQL Server 2008 R2 in Windows 7 SP1 machine. I can confirm this machine has .Net
Feature enabled and with Latest version.
TITLE: Microsoft SQL Server 2008 R2 Setup
The following error has occurred:
Error 25541.Failed to open XML file C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config, system error: -2147024786
Regards,
Muthukumar.S.P.

Hi,
Can you follow workaround mentioned in below msdn blog
http://blogs.msdn.com/b/astebner/archive/2007/11/01/5826719.aspx
As per the blog you have to open the msi log files which must be located at
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log
In MSI log files search for the error mentioned in blog. Below link will help you read setup log files
http://msdn.microsoft.com/en-gb/library/ms143702%28v=sql.105%29.aspx
PS: Please read links carefully and patiently and if it does not solves issue please post summary.txt file and details.txt file on skydrive for analysis
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles

Attempted to perform an unauthorized operation error on windows 8.1 while installing SQL server 2008

Hi,
I am getting the error "Attempted to perform an unauthorized operation" on windows 8.1 while installing
SQL server 2008.
The specific error is The error is Attempted to perform an unauthorized operation."
at stepSqlBrowserConfigAction_install_ConfigNonRC_Cpu32 .
I have tried everything from copying to the C drive. I am the admin on the machine. I also checked access in registry. It already has acesss to HKLM\System\CurrentControlSet\Control\WMI\security
Can someone comment on how to resolve this issue. I also tried NT
AUTHORITY\SYSTEM but getting the same error.
Any help would be appreciated.

Hello,
Please note that SQL Server 2008 requires Service Pack 3 (SP3) to make it compatible with
Windows 8.1. Please perform an slipstream installation of SQL Server 2008 + SP3:
http://support.microsoft.com/kb/955392
If it fails again, please share with us the Summary.txt log file and the details.txt log file. The following article
may help you locate those files on disk::
http://msdn.microsoft.com/en-us/library/ms143702(v=sql.100).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Inserting Japanese characters to SQL Server via CFMX

What is necessary in the setup to save non-Latin characters
to SQL Server via CFMX form? The ColdFusion data source has the
Unicode option enabled (Enable Unicode for data sources configured
for non-Latin characters). The target field in the database is an
nvarchar. What else is necessary to properly insert and then later
display the non-Latin characters?
On Microsoft's site they describe the need to convert to and
from UCS-2 when accessing SQL Server via ASP. Is this type of
conversion relevant to CFMX?

jegrubbs wrote:
> What is necessary in the setup to save non-Latin
characters to SQL Server via
> CFMX form? The ColdFusion data source has the Unicode
option enabled (Enable
> Unicode for data sources configured for non-Latin
characters). The target field
> in the database is an nvarchar. What else is necessary
to properly insert and
> then later display the non-Latin characters?
- define db columns as "N" types
- ensure cf pages are utf-8 encoding:
--tag the files w/a BOM
--use
<cfprocessingDirective pageencoding="utf-8">
on each page
--use
<cfset setEncoding("form","utf-8")>
<cfcontent type="text/html; charset=utf-8">
in application.cfm or .cfc
- when doing INSERT/UPDATE make sure to use either unicode
hinting (N'text') or
cfqueryparam (making sure to turn on the unicode option for
that DSN in
cfadmin). cfqueryparam is the best choice.
also see:
http://www.sustainablegis.com/unicode/greekTest.cfm
> On Microsoft's site they describe the need to convert to
and from UCS-2 when
> accessing SQL Server via ASP. Is this type of conversion
relevant to CFMX?
nope the JDBC driver will handle that gruff. make sure you
use the JDBC driver
(name as ms sql server in cfadmin) and NOT the odbc bridge
thnig.

Sql Server 2012 Encrypted Connection Accept only Internal IP

Hi Friends,
As we are using sqlserver 2012 is it possible we can configure Sql Server to Accept connection only internal ip (local) network as wel encrypted connections only , if possible please let me know how we can A chive this .
thank you.
Regards,
asad

Hello,
SQL Server TCP/IP protocol is a common protocol widely used over the Internet. It communicates across interconnected networks of computers that have diverse hardware architectures and various operating systems. Named Pipes is a protocol developed for
local area networks. In this case, you can configure SQL Server only use Named Pipes protocol via SQL Server Configuration Manager.
Choosing a Network Protocol:
http://technet.microsoft.com/en-us/library/ms187892(v=sql.105).aspx
Regards,
Elvis Long
TechNet Community Support

Issues while readin SQL server via ODBC connection

Similar Messages

Maybe you are looking for