JDBC Adapter Error to conect to SQL Server 2005
Hi all.
I´m trying to conect to a SQL Server 2005 database, but facing this error:
UnsupportedClassVersionError: (com/microsoft/sqlserver/jdbc/SQLServerDriver) bad major version at offset=6'
The parameters are:
JDBC Driver: com.microsoft.sqlserver.jdbc.SQLServerDriver
Connection: jdbc:sqlserver://
How can I resolve this issue?
Thanks.
The jdbc driver seems to be incompatible. Use the compatible version from [http://www.microsoft.com/downloads/details.aspx?familyid=99B21B65-E98F-4A61-B811-19912601FDC9&displaylang=en|http://www.microsoft.com/downloads/details.aspx?familyid=99B21B65-E98F-4A61-B811-19912601FDC9&displaylang=en]
Similar Messages
-
Sender JDBC support the stored procedure in SQL Server 2005
Dear All,
My question here is , Sender is JDBC adpter support to call the Stored procedure in Microsoft SQL Server 2005?
I followed the below thread before posting this question
Sender JDBC Adapter Supports Stored Procedures????
In the thread Suraj response has mentioned SAP note: 941317, I checked the note, Note says it supported only ORACLE DBMS versions.
Could you please clarify about this to possibility to call the stored procedure in Microsoft SQL server 2005?
Thank you in Advance
SateeshHi Sateesh,
To answer your query, Yes it does. SP call works with SQL Server 2005 as well, the SP call should be "execute SPNAME <paramas>". In the place of update statement put any junk value as mentioned in the earlier comment.
But just one thing to be noted, the select or any other query returning the desired resultset must be the first statement in youre SP returning value to the calling app. Means if there are any update, deletion or intermediate select queries to be used with in your SP, those all should be placed after the Main Select query that returns the desired resultset. Variable declarions and assignments are allowed.
But if the seq of statements in your SP are like:
@var1 Varchar
Update <tablename>....
Select * from <tablename>
Then the output of the SP is :
1 row updated
<the resultset from select>
In such cases, PI can recognise the first value returned only, that is "1 row updated" and hence the returned resultset wouldn't be seen by PI or not be passed to integration engine. Hence the update should come after the main Select.
One more interesting piece of information, even if you copy and paste the entire SP code in place of the query string of Sender JDBC adapter, that too will work with all your variable declarations, multiple queries and updates and everything. Just have to follow the above rule.
Let us know what you find.
Regards,
Suddhasatta -
Error 1406 while installing SQL server 2005 on windows 2003 64 bit standard
Hi Gurus,
When I am trying to install SQL SERVER 2005 on Windows Serevr 2005 i get the error code 1406
I tried using the script sql4sap.vbs. and tried to set the named instance.
please suggest
Please find the contents of 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 : Mon Apr 14 14:51:07 2008
Machine : UKSAPTEST02
Product : .NET Framework 2.0
Product Version : 2.0.50727
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST02_.NET Framework 2.0.log
Last Action : InstallFinalize
Error String :Could not write value to key \Software\Classes\.appref-ms
Error Number : 1406
UKSAPTEST02 : There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information.
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time : Mon Apr 14 14:52:26 2008
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST02_Core.log
Many thanks
Sreeram
Edited by: sreeram kaki on Apr 14, 2008 6:12 PMHi Clas,
Thanks for the valuable suggestions,
I tried to install the database (sql server 2005) using the local admin password on another server which do not have the antivirus installed. I started the installation at 3:15 PM today and the installation is still in progerss
please see the log below from 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 : Tue Apr 15 15:04:28 2008
Machine : UKSAPTEST01
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SQLSupport_1.log
Machine : UKSAPTEST01
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SQLNCLI_1.log
Machine : UKSAPTEST01
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SqlWriter_1.log
Machine : UKSAPTEST01
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_MSXML6_1.log
Machine : UKSAPTEST01
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SQLSupport_2.log
Machine : UKSAPTEST01
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SQLNCLI_2.log
Machine : UKSAPTEST01
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_BOL_1.log
Machine : UKSAPTEST01
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_MSXML6_2.log
Also see the last few lines of the log file
SQLSetup0001_UKSAPTEST01_SQL.log
Action start 17:10:43: Rollback_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
MSI (s) (C0!50) [17:10:43:815]: PROPERTY CHANGE: Deleting Rollback_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its current value is '1 0 0 Installing Local Groups 50000 SQLServer2005MSFTEUser$UKSAPTEST01$RDE NT AUTHORITY\SYSTEM '.
Action ended 17:10:43: Rollback_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
<EndFunc Name='ScheduleActionX' Return='0' GetLastError='0'>
<Func Name='ScheduleActionX'>
<Func Name='SetCAContext'>
MSI (s) (C0!50) [17:10:43:815]: PROPERTY CHANGE: Adding Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its value is '1 1 0 Installing Local Groups 50000 SQLServer2005MSFTEUser$UKSAPTEST01$RDE NT AUTHORITY\SYSTEM '.
MSI (s) (C0!50) [17:10:43:815]: Doing action: Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Action start 17:10:43: Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
MSI (s) (C0!50) [17:10:43:830]: PROPERTY CHANGE: Deleting Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its current value is '1 1 0 Installing Local Groups 50000 SQLServer2005MSFTEUser$UKSAPTEST01$RDE NT AUTHORITY\SYSTEM '.
Action ended 17:10:43: Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
<EndFunc Name='ScheduleActionX' Return='0' GetLastError='0'>
<EndFunc Name='Write_sqlGroupMember' Return='0' GetLastError='0'>
PerfTime Stop: Write_sqlGroupMember : Tue Apr 15 17:10:43 2008
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (C0:F0) [17:10:43:830]: Doing action: Write_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
Action ended 17:10:43: Write_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
MSI (s) (C0:50) [17:10:43:830]: Invoking remote custom action. DLL: C:\WINDOWS.0\Installer\MSI1D8.tmp, Entrypoint: Write_sqlUserSecurity
Action start 17:10:43: Write_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
<Func Name='LaunchFunction'>
Function=Write_sqlUserSecurity
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: Write_sqlUserSecurity
PerfTime Start: Write_sqlUserSecurity : Tue Apr 15 17:10:43 2008
<Func Name='Write_sqlUserSecurity'>
<Func Name='ScheduleActionX'>
<Func Name='SetCAContext'>
MSI (s) (C0!34) [17:10:43:924]: PROPERTY CHANGE: Adding Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its value is '0 1 0 Setting User Security 50000 SQLServer2005SQLBrowserUser$UKSAPTEST01 SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeChan
MSI (s) (C0!34) [17:10:43:924]: Doing action: Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Action start 17:10:43: Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
MSI (s) (C0!34) [17:10:43:924]: PROPERTY CHANGE: Deleting Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its current value is '0 1 0 Setting User Security 50000 SQLServer2005SQLBrowserUser$UKSAPTEST01 SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$
Action ended 17:10:43: Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
<EndFunc Name='ScheduleActionX' Return='0' GetLastError='0'>
<EndFunc Name='Write_sqlUserSecurity' Return='0' GetLastError='0'>
PerfTime Stop: Write_sqlUserSecurity : Tue Apr 15 17:10:43 2008
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (C0:F0) [17:10:43:940]: Doing action: Write_sqlFileSDDL.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
Action ended 17:10:43: Write_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
MSI (s) (C0:10) [17:10:43:940]: Invoking remote custom action. DLL: C:\WINDOWS.0\Installer\MSI1D9.tmp, Entrypoint: Write_sqlFileSDDL
Action start 17:10:43: Write_sqlFileSDDL.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
<Func Name='LaunchFunction'>
Function=Write_sqlFileSDDL
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: Write_sqlFileSDDL
PerfTime Start: Write_sqlFileSDDL : Tue Apr 15 17:10:43 2008
Thanks & Regards,
Sreeram
Edited by: sreeram kaki on Apr 15, 2008 6:45 PM -
Error when upgrading from SQL Server 2005 to SQL Server 2014
Hello everyone,
Could you help me, i have an error when i try to upgrade my SQL Server 2005 Enterprise Edition to SQL Server 2014 Enterprise Edition,
All of prerequisits are available and i dont have a problem,
before the end of migration process, i have this error: The group name could not be found (0x84BB0001)
File log:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: The upgrade process for SQL Server failed. To continue the upgrade process, use the following information to resolve the error. Next, uninstall SQL Server by using this
command line: setup /q /action=uninstall /instanceid=MSSQLSERVER /features=SQLENGINE,FULLTEXT,REPLICATION. Then, run SQL Server Setup again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84BB0001
Error description: The group name could not be found.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x0AD059E6%400x3FAAA006&EvtType=0x0AD059E6%400x3FAAA006
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: The upgrade process for SQL Server failed. To continue the upgrade process, use the following information to resolve the error. Next, uninstall SQL Server by using this
command line: setup /q /action=uninstall /instanceid=MSSQLSERVER /features=SQLENGINE,FULLTEXT,REPLICATION. Then, run SQL Server Setup again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84BB0001
Error description: The group name could not be found.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x0AD059E6%400x3FAAA006&EvtType=0x0AD059E6%400x3FAAA006
Feature: SQL Server Replication
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: The upgrade process for SQL Server failed. To continue the upgrade process, use the following information to resolve the error. Next, uninstall SQL Server by using this
command line: setup /q /action=uninstall /instanceid=MSSQLSERVER /features=SQLENGINE,FULLTEXT,REPLICATION. Then, run SQL Server Setup again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84BB0001
Error description: The group name could not be found.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x0AD059E6%400x3FAAA006&EvtType=0x0AD059E6%400x3FAAA006
Best regards,
Guiga HafedhThere are more detailed logs for the various components. The one of interesting is the one for the engine or possibly the one for full-text.
These logs are extremely verbose, and the errors are rarely crystal clear, but at least give them a try. If you have problems, find a place to upload them (Dropbox, Skrydrive etc), so that we can look.
The closest at hand is that "group" that cannot be found is an AD group.
Erland Sommarskog, SQL Server MVP, [email protected] -
-net.sourceforge.jtds.jdbc.Driver ERROR WHILE CONNECTING TO SQL SERVER
Hi,
While making a new connection to Sql Server Express Edition Database, through Oracle Sql Developer i am getting a problem when retrieving the database.The error is "-net.sourceforge.jtds.jdbc.Driver" .I have downloaded the "jTDS - SQL Server and Sybase JDBC driver " from sourceforge website, but i am confused about where to paste it.
thanks.I'm not sure why you are having the error but I am sure of the following:
1. This forum is not appropriate for SQL*Developer questions.
2. Or questions about code from SourceForge
3. Or Microsoft products.
It seems unlikely this has anything to do with Oracle so I would recommend you find a forum related to the driver if one exists. Otherwise you can try the SQL*Developer forum but I would be there aren't more than a dozen other people on the product trying to do this. -
SQL Server 2005 Installation Error
I am installine ECC6 on SQL Serer 2006. I have started the SQL Server installation, using the SQL4SAP.vbs and after about 10 minutes the installation stops with an error. I am pointed to a fine Summary.txt but the details in the file do not give a clue on the problem:
Machine : SAPDEMO
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLXML4_1.log
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time : Mon Dec 03 09:09:38 2007
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Core(Local).log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLSupport_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLNCLI_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_OWC11_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SqlWriter_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_BackwardsCompat_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_MSXML6_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLSupport_2.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLNCLI_2.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_OWC11_2.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_BOL_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_BackwardsCompat_2.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SQLXML4_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework 2.0 LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Upgrade Advisor.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Upgrade Advisor LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Windows Installer.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_.NET Framework Windows Installer LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SNAC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_Support.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_SCC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_SAPDEMO_WI.logHi Rajeev,
Indeed it was a typo error I am attempting SQL Server 2005.
I am using the 32 bit installation, that has been checked.
Here are the details from C:\Windows\SQL4SAP.log
Customized installation of SQL Server 2005 for SAP *
Log File: C:\WINDOWS\SQL4SAP.log
Script started 03/12/2007 08:46:25 on SAPDEMO
System settings:
Win32_Processor.Name=Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz
Win32_Processor.Name=Intel(R) Core(TM)2 Duo CPU T7500 @ 2.20GHz
Win32_ComputerSystem.SystemType=X86-based PC
Win32_OperatingSystem.OSType=18
Win32_OperatingSystem.Version=5.2.3790
Win32_OperatingSystem.ServicePackMajorVersion=2
Win32_OperatingSystem.Caption=Microsoft(R) Windows(R) Server 2003, Standard Edition
Win32_OperatingSystem.ProductType=3
Win32_OperatingSystem.OSProductSuite=272
Win32_OperatingSystem.OSLanguage=1033
Windows version:
OSVersion = 5.2
OSFamily = Windows2003
OSServicePack = 2
OSEdition = Server
OSSystemType = X86
OSProductSuite = Terminal Server
OSMsiVersion = 3.1.4000.4042
OSMdacVersion = 2.82.3959.0
OSLanguage = English United States
OSLanguageID = 1033
Environment on SAPDEMO:
userDir = C:\Documents and Settings\Administrator\
tmpDir = C:\DOCUME1\ADMINI1\LOCALS~1\Temp\1\
rootDir = C:\WINDOWS\
prgDir = C:\Program Files\
prgDirX86 = \
SQL4SAP version:
version: ' v3.2.44 Mar 2007: SQL2005 SP2, Windows2003 SP2
size: 86124
created: 30/11/2007 16:59:31
modified: 20/03/2007 13:36:44
exe: C:\WINDOWS\system32\cscript.exe
script: C:\SAP_CD\CD2\SQL4SAP.vbs
C: C:
Script path:
myRoot = C:\SAP_CD\CD2\
myDir = C:\SAP_CD\CD2\x86\
myDirUNC = C:\SAP_CD\CD2\x86\
Script settings:
SqlAuthInstall = False
SilentInstall = False
DeEditionOnly = False
DeEditionPossible = False
SapItMsgBox = False
SilentRtmSetup = True
Service Account:
"C:\SAP_CD\CD2\x86\SqlCmd\GetSidName.exe" S-1-5-18 =>NT AUTHORITY\SYSTEM
OSSystemAccount= NT AUTHORITY\SYSTEM
03/12/2007 08:46:28
Input Box "Select SQL Server instance"
No SQL Server instance was found.
SQL Server Native Client not installed
SQL Server 2005 Client Tools not installed
Enter a new or existing instance name.
- for a Default Instance, enter: (default) or .
- for a Named Instance, enter: <SID>
To install SQL Client Tools Only, press Cancel.
Result: (default)
Registry settings (1/2):
HKLM\SOFTWARE\Microsoft\DataAccess\FullInstallVer
READ: 2.82.3959.0
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
READ: 4
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
WRITE(REG_DWORD): 4
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{319b29ae-7427-4fbc-9355-22df056c27a4}
READ: 4
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{319b29ae-7427-4fbc-9355-22df056c27a4}
WRITE(REG_DWORD): 4
HKLM\SOFTWARE\Microsoft\Microsoft SQL Native Client\CurrentVersion\Version
READ:
HKLM\SOFTWARE\Microsoft\Microsoft SQL Native Client\CurrentVersion\PatchLevel
READ:
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools\ClientSetup\CurrentVersion\CurrentVersion
READ:
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools\ClientSetup\CurrentVersion\CSDVersion
READ:
03/12/2007 08:46:32
Message Box "Confirmation"
You have chosen to install the new instance
SQL Instance: (default)
SQL Version: 9.00.3042
SQL Edition: 2005 Enterprise Edition
SQL Collation: SQL_Latin1_General_CP850_BIN2
Authentication: Windows only
Login sa: random password, login disabled
=======================================
The installation may take 15 minutes or longer
=======================================
Do you want to start the installation now?
Result: vbOK
03/12/2007 08:46:34
installing SQL Server 2005 Enterprise Edition on X86 - build 9.00.1399 ...
Log File: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
Command: "C:\SAP_CD\CD2\x86\EnterpriseEdition\Servers\setup.exe" /qn USERNAME="SAP ISV Royalty Licensing Program" ADDLOCAL=Connectivity,SQL_Tools90,SQLXML,Tools_Legacy,SQL_Documentation,SQL_BooksOnline,SQL_Data_Files,SQL_FullText PERSEAT=50 INSTANCENAME=MSSQLSERVER SQLCOLLATION=SQL_Latin1_General_CP850_BIN2 AGTAUTOSTART=1 SQLACCOUNT="NT AUTHORITY\SYSTEM" AGTACCOUNT="NT AUTHORITY\SYSTEM" SQLBROWSERACCOUNT="NT AUTHORITY\SYSTEM" DISABLENETWORKPROTOCOLS=0 SAPWD=xxxxxxxxxxxxxxxx
Return Code: 1605
03/12/2007 08:48:41
Log file C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\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 : Mon Dec 03 08:46:48 2007
Machine : SAPDEMO
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_1.log
Machine : SAPDEMO
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_1.log
Machine : SAPDEMO
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SqlWriter_1.log
Machine : SAPDEMO
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_2.log
Machine : SAPDEMO
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_2.log
Machine : SAPDEMO
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_BOL_1.log
Machine : SAPDEMO
Product : SQLXML4
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLXML4_1.log
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time : Mon Dec 03 08:48:39 2007
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Core(Local).log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SqlWriter_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_MSXML6_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLSupport_2.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLNCLI_2.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_BOL_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SQLXML4_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework 2.0 LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Upgrade Advisor.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Upgrade Advisor LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Windows Installer.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_.NET Framework Windows Installer LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SNAC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_Support.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SAPDEMO_SCC.log
service MSSQLSERVER does not exist
03/12/2007 08:48:41
Message Box "Installation failed"
The unattended installation failed.
Installation Step: SQL Server - build 9.00.1399
Return Code: 1605
Log File: C:\WINDOWS\SQL4SAP.log
Check the log file above!
See also SAP note 896566 for known issues
Result: vbOK
Registry settings (2/2):
HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL\MSSQLSERVER
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg0
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg1
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg2
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg3
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg4
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg5
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg6
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg7
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg8
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg9
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg10
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg11
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg12
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg13
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg14
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg15
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg16
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg17
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg18
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg19
READ:
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Parameters\SQLArg20
READ:
HKLM\SOFTWARE\Microsoft\MSSQLSERVER\Setup\SQLPath
READ:
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{3d06c673-5e8a-41c0-b47f-3c3ca0a22e67}
WRITE(REG_DWORD): 4
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\{319b29ae-7427-4fbc-9355-22df056c27a4}
WRITE(REG_DWORD): 4
03/12/2007 08:48:47
Quit script with return code 1 -
SQL Server 2005 with an ODBC-JDBC Bridge
Hello,
I use an ODBC - JDBC Bridge (because when I use SQL Server 2005 Driver JDBC Version 1.1, the text connection failed). I don't know why I can't reverse my model.
What happened?
thanks
BillieWe have also a SQL server 2000 instance at the same server. Yesterday I have spoken with the sql server admin and he told me that he has disconnect the sql server 2000 databases whatever this means. :-D
Now all works fine. Thank you for your help
BTW I use the following connection string:
jdbc:sqlserver://my_db_server;instanceName=my_instance_name;DatabaseName=my_db_name -
Error deploying JDBC driver for SQL Server 2005
Hi all
I'm trying to deploy a JDBC driver for MS SQL Server 2005 (downloaded [here|http://www.microsoft.com/downloads/details.aspx?familyid=C47053EB-3B64-4794-950D-81E1EC91C1BA&displaylang=en]). When I try to deploy it according to the instructions found [here|http://help.sap.com/saphelp_nwce10/helpdata/en/51/735d4217139041e10000000a1550b0/frameset.htm] it fails.
The error in the logs doesn't give any useful information though. It only says Error occurred while deploying component ".\temp\dbpool\MSSQL2005.sda".
Has anyone else deployed a driver for SQL Server 2005, or perhaps have any suggestions of what else I could try?
Thanks
StuartHi Vladimir
That's excellent news! Thanks for the effort you've put into this. I'm very impressed with how seriously these issues are dealt with, specifically within the Java EE aspects of SAP.
May I make two suggestions on this topic:
1. Given that NWA has such granular security permissions, please could the security error be shown when it is raised? This would help immediately identify that the problem isn't actually a product error, but rather a missing security permission (and thus save us time and reduce your support calls).
2. Please could the role permissions be clearly documented (perhaps they already are, and I just couldn't find the docs?) so we know what is and isn't included in the role. The name is very misleading, as a "superadmin" is generally understood to have no limitation on their rights - so clear documentation on what is in-/excluded would be most helpful.
On a related topic, I came across another issue like this that may warrant your attention (while you're already looking into NWA security issues). I logged a support query about it (ref: 0120025231 0000753421 2008) in case you can retrieve details there (screenshots, logs, etc.). It's basically a similar security constraint when trying to create a Destination. I'm not sure if this is something you would like to include as standard permissions within the NWA_SUPERADMIN role or not, but I think it's worth consideration.
Thanks again for your help!
Cheers
Stuart -
JDBC Connection Error with Sql Server 2005
Hi
I am trying to connect the Sql Server 2005 thru jdbc but I am getting the following error.
SQLException: The TCP/IP connection to the host usselect.com/x-logs, port 1433 has failed. Error: usselect.com/x-logs. Please verify the connection properties and check that a SQL Server instance is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.
I am using sqljdbc4.jar (driver)
import java.sql.Connection; import java.sql.DatabaseMetaData; import java.sql.DriverManager; import java.sql.SQLException; public class testdb { public static void main(String s[]){ String userid="xxxx", password = "xxxxx"; String url = "jdbc:sqlserver://usselect.com/x-logs:1433"; Connection con = null; try { Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver"); }catch(java.lang.ClassNotFoundException e) { System.err.print("ClassNotFoundException: "); System.err.println(e.getMessage()); } try { con = DriverManager.getConnection(url,userid,password); } catch(SQLException ex) { System.err.println("SQLException: " + ex.getMessage()); } if(con!= null){ System.out.println("Got Connection."+con); }else{ System.out.println("Could not Get Connection"); } } }
Please advise.srinu1198 wrote:
By using Jdbc thin driver are we able to connect to mssql 2005 through windows authentication or not? "thin driver" refers to a specific Oracle driver.
Far as I know both the current (not older) MS driver supports windows auth. Certianly the jTDS driver does.
If yes what is the procedure. One starts by reading the docs. If necessary then one googles. -
BI JDBC Connection fails to connect to SQL Server 2000
Hello SDNs,
I have configured my JDBC connector to connect to MS SQL Server 2000(Third party in my case) using the document How to Configure UD connect on the J2EE server for JDBC Access to External Drivers.
I have given the following properties for my JDBC connector:
Driver Name : com.microsoft.jdbc.sqlserver.SQLServerDriver
URL : jdbc:microsoft:sqlserver://servername:1433;database=<databasename>
When i test the connection using the url: http://hostname:50000/TestJDBC_Web/TestJDBCPage.jsp
Here is the Error:
<b>Details:
com.sap.ip.bi.sdk.exception.BIConnectionFailedException: Cannot open the connection at com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcConnectionFactory.getConnectionEx(JdbcConnectionFactory.java:238) at com.sap.ip.bi.sdk.trialarea.connector.servlet.model.JDBCModel.getConnection(JDBCModel.java:797) at com.sap.ip.bi.sdk.trialarea.connector.servlet.model.JDBCModel.getTables(JDBCModel.java:132) at
com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcManagedConnection.(JdbcManagedConnection.java:118) ... 23 more Caused by: java.lang.ClassNotFoundException: com.microsoft.jdbc.sqlserver.SQLServerDriver Found in negative cache -
Loader Info -
ClassLoader name: [connector:default] Parent loader name: [Frame ClassLoader] References: common:service:http;service:servlet_jsp service:ejb common:service:iiop;service:naming;service:p4;service:ts service:jmsconnector library:jsse library:servlet common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl library:ejb20 library:j2eeca library:jms library:opensql common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore interface:resourcecontext_api interface:webservices interface:cross interface:ejbserialization common:library:bimmrcore;library:bimmrdb sap.com/cafcore sap.com/cafruntimeear library:tcconnconnectorframework library:sapxmltoolkit sap.com/com.sap.ip.bi.sdk.dac.connector.xmla.x library:com.sap.mw.jco library:com.sap.aii.proxy.framework library:com.sap.aii.util.misc library:com.sap.ip.bi.sdk.dac.connector.odbodll library:BI_JDBC library:bimmrcwm_1.0_library library:bimmrjmi library:com.sap.ip.bi.sdk library:MSSQL Resources: H:\usr\sap\BD2\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.ip.bi.sdk.dac.connector.xmla\connector\connectors\bi_sdk_xmla.rar\bi_sdk_xmla.jar H:\usr\sap\BD2\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\cafbwadapterassembly\connector\connectors\sap.com_cafbwadapterassembly.rar\lib\java\sap.comcafbwadapter~caf.bw.adapter.jar H:\usr\sap\BD2\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.ip.bi.sdk.dac.connector.sapq\connector\connectors\bi_sdk_sapq.rar\bi_sdk_sapq.jar H:\usr\sap\BD2\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.ip.bi.sdk.dac.connector.jdbc\connector\connectors\bi_sdk_jdbc.rar\bi_sdk_jdbc.jar Loading model: {parent,references,local} -
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:360) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:141) at com.sap.ip.bi.sdk.dac.connector.jdbc.impl.Connection.connectDB(Connection.java:365) ... 25 more</b>
Please let me know if any changes are required in Driver name and URL.
Your inputs will be highly appreciated.
Thanks,
Sireesha.B
Message was edited by:
sireesha BorraHi Sireesha,
Some insights.....while using JDBC connector .
For JDK 1.1 environments, access to the "current working directory" mustbe granted.
For Java 2 environments, access to the temporary directory specified by the VM configuration must be granted. The following is an example of permissions being granted in the file java.security.policy for the C:\TEMP directory:
// permissions granted to all domains grant { // Permission to create and delete temporary files. // Adjust the temporary directory for your environment. permission java.io.FilePermission "C:
TEMP
-", "read,write,delete"; };
Note 777304 - Problems with JDBC drivers when using BI UDI
Related notes -
834385 - 'Invalid operation: result set closed' Exception
834384 - Problems with selection in InfoPackage in UD Connect
777306 - MSSQL problem when using BI UDI
777305 - Problems with Unicode when using BI UDI
Fyi-
http://dev.mysql.com/downloads/index.html
Regards,
Anil -
JDBC - MS SQL Server 2005 with multible instances
I want to get data from a Microsoft SQL Server via JDBC. We have such a scenario and till now it works fine. Now we have a second instance at the sql server and we want to connect to this instance. I've found the following MSD article:
http://msdn2.microsoft.com/en-us/library/ms378428.aspx
<b>SQL Server 2000 and SQL Server 2005 allow for the installation of multiple database instances per server. Each instance is identified by a specific name. To connect to a named instance of SQL Server, you can either specify the port number of the named instance (preferred), or you can specify the instance name as a JDBC URL property or a datasource property. If no instance name or port number property is specified, a connection to the default instance is created. See the following examples:
To use a port number, do the following:
jdbc:sqlserver://localhost:1433;integratedSecurity=true;<more properties as required>;
To use a JDBC URL property, do the following:
jdbc:sqlserver://localhost;instanceName=instance1;integratedSecurity=true;<more properties as required>;</b>
Because the named instance has no explicit port I've tried to use the second one but this doesn't work. I've tried all possible combinations of these parameters but either I get an error or my adapter connects to the first instance
Any idea how I can connect to the second named instance?We have also a SQL server 2000 instance at the same server. Yesterday I have spoken with the sql server admin and he told me that he has disconnect the sql server 2000 databases whatever this means. :-D
Now all works fine. Thank you for your help
BTW I use the following connection string:
jdbc:sqlserver://my_db_server;instanceName=my_instance_name;DatabaseName=my_db_name -
Error when calling a XI-webservice from SQL-Server 2005
Hi all,
we have published a webservice with XI 7.0 (using the SOAP-Adapter) and try to call it from a stored procedure within SQL-Server 2005. Upon execution we receive the error
"<SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code>" and
"<SAP:Stack>Empty HTTP query received; message processing not possible </SAP:Stack>".
We are using the dll MSXML2.ServerXMLHTTP. The webservice is available and can be reached from other tools like SOAP-UI when using the same endpoint-URL. It is also possible to call the service from Visual-Basic using the same code.
Does anyone has any clue about what's causing this error?
Thanks in advance!It is clear that, PI service is working absolutely fine and the problem is calling it in your SP. I do not think you are calling a web service but actually sending a HTTP request to the server. An HTTP request and a SOAP call are different in terms of protocol. You would need to explore more on how to call web services from SQL SPs.. and the right place to search would be MS SQL Server Forums..!!
VJ -
App not versioned error in JDeveloper - ADF with SQL Server 2005
Hello All,
I am developing a sample ADF application. Database is MS SQL Server 2005 SP2. I get below error message. I am trying in parallel to google it... However trying here if any encountered such an issue and had resolved it.
Thanks in advance for your time.
Cheers,
Vagic.
[02:06:19 PM] Deploying Application...
<Feb 23, 2010 2:06:20 PM PST> <Warning> <J2EE> <BEA-160195> <The application version lifecycle event listener oracle.security.jps.wls.listeners.JpsAppVersionLifecycleListener is ignored because the application ExmReports is not versioned.>
<Feb 23, 2010 2:06:20 PM PST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1266962779600' for task '0'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:290)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:391)You might need to add the JDBC jar file for SQL Server to the classpath of the integrated WebLogic. See minute 8 here: http://download.oracle.com/otn_hosted_doc/jdeveloper/11gdemos/NBtoJDevProject/NBtoJDevProject.html
-
Deploy JDBC driver for SQL server 2005 on PI 7.1
How to deploy JDBC driver for SQL server 2005 on PI 7.1
We are in SAP NetWeaver 7.1 Oracle 10G
Third party system is SQL server 2005
There are different JDBC versions are available to download for SQL server 2005.
I am not sure about the applicable version for the PI 7.1 SP level. Again JMS Adapter needs to be deploy along with this.
Please helpHi,
Hope this How to Guide help you.
How To Install and Configure External Drivers for the JDBC & JMS Adapters from
www.sdn.sap.com/irj/sdn/howtoguides
Regards,
Karthick.
Edited by: Karthick Srinivasan on Apr 13, 2009 4:07 PM -
BI Publisher 11g - calling SQL Server 2005 stored procedure error
Hi experts
I have been calling succesfully an SQL server 2005 stored procedure for the data model of a BI publisher report in 10g, passing it a customerNo parameter.
EXEC [dbo].[usp_WelcomeLettersConsumerNo]
@CustomerNo = :sCustomerNo
However it does not work in 11g I get the error:
[Hyperion][SQLServer JDBC Driver][SQLServer]Incorrect syntax near the keyword 'is'.
which is frustrating as there is no 'is' in the statement (perhaps it is picking up :s?) - I wonder does anyone know if there has been a change in 11g that may be causing this?
cheers
TimHi experts
I have been calling succesfully an SQL server 2005 stored procedure for the data model of a BI publisher report in 10g, passing it a customerNo parameter.
EXEC [dbo].[usp_WelcomeLettersConsumerNo]
@CustomerNo = :sCustomerNo
However it does not work in 11g I get the error:
[Hyperion][SQLServer JDBC Driver][SQLServer]Incorrect syntax near the keyword 'is'.
which is frustrating as there is no 'is' in the statement (perhaps it is picking up :s?) - I wonder does anyone know if there has been a change in 11g that may be causing this?
cheers
Tim
Maybe you are looking for
-
I am having trubble with my HP downloded the latest android hp update and it has stop me from transfering my files to usb and will also will not let me go into the home in the setting. It has also change the icon for the seting to a wheel with teeth
-
only to find that the programs installed are not working and they have deactivted the already installed software and they are also not working. how do i revert the changes i hav done?..pls help. the computer does not boot, it does not even reach the
-
Re-arrange the flat file out put in APD
Hi Guys, I am loading data in APD,soruce is Query and target is Flat file.i want to re-arrange the out put file. Let me know what are the possible ways to re-arrange the columns in the out put flat file. Regards, Jayapal
-
MAB/802.1x and Alkatel IP Phones
Hi All We have a distributed deployment where Alkatel ip-touch phones are authentictaed via MAB. Alkatel ip touch phones has 802.1x enabled by default and the phone tries eapol first and then switch authenticates via MAB which is fine. Once authentic
-
Converting old Mac Word floppy discs to PC Word
I used to have a Mac in the '90s. I have about 10 floppy disks with mostly Word docs that I want to convert to PC format. I bought an external floppy drive from Best Buy (Dynex) and connected it to a friend's Powerbook. His Powerbook recognized the f