CF8 and MS SQL Server 2008

Hi,
I'm wondering if anyone else has run into this issue. We are porting an older CF app to CF8 and upgrading our db at the same time. Our old model is CF 6.1 using MS SQL Server 2005 and our new model is CF8 using MS SQL Server 2008.
I'm having the following issue....
We have an application form where people apply to jobs, they can either type their text in, or copy and paste (usually from MS Word). On the back end we use CF ToBase64 and then ToBinary functions to convert the data to store it in a Blob field in the db.
No code changes have been done.
If the user copies and pastes into the form field and it contains MS bullet points, in our old model they are stored correctly, under the new model they are not. When I look at that candidates data on the web page I see ? marks where the bullets should be. Querying the db field directly and doing the necessary conversions to get the data back into string format, I can see that the field actually contains question marks.
I have tried using Adobe's recommended change of using the CharsetDecode and CharsetEncode functions - these do not make any difference.
Has anyone else encountered this problem?

You may test encode / decode the input data (only testing the ToBase64 function), or may be just display the input, without encode base 64, to check the encoding management. I guess it comes from the input page.

Similar Messages

Install BI Tools with paid VS2008 Pro in workstation and paid Sql Server 2008 R2 in server?

My workstation has VS2008 Pro (paid) and Sql Express (free); our Windows Enterprise server has SQL Server 2008 R2 RTM (paid).
In other words, my workstation may not have a paid version of the sql server DB, but our server does. Is there a possibility that I can install the BI development tools in my workstation?
Thanks.
VM

Hi VM,
As you can see on the link below
http://msdn.microsoft.com/en-us/library/cc645993(v=sql.105).aspx#Dev_tools
The Business Intelligence Development Studio is not available on SQL Server 2008 Express Edition. So if you want to the BIDS tool is available on your workstation, then you need to change the edition from Express to other edition.
Besides, you can install SQL Server Data Tools - Business Intelligence for Visual Studio 2012 on your workstation, in this case, the BI development tools is available on your workstation. The SQL Server Data Tools - Business Intelligence for Visual Studio
2012 is available on the link below.
http://www.microsoft.com/en-in/download/details.aspx?id=36843
Regards,
Charlie Liao
TechNet Community Support

BO 3.2 and DB SQL Server 2008

Dear All,
We have installed MS SQL server 2008R2 on MS windows 2008R2. Now we are installing BOBJ data service 3.2 on another system with windows XP. While installing we are selecting the option connect to existing database.
But after providing connection parametres we are getting error as
Cannot open connection to the repository. The error message from the underlying DBMS is <ODBC call <SQLDriverConnect> for data source <localhost> failed: <MicrosoftODBC SQL Server DriverDBNETLIBSQL Server does not exist or access denied.>. Notify Customer Support.>. (BODI-20006)
Please advice
Best Regards,

Dear Jeff,
Settings of TC/IP in SQL server configuration manager is enabled
Dear manoj
SQL Server 2008 client is installed still the error.
By checking at command level its requesting password. But as soon as i enter the password iam getting the error
sqlcmd -S(servername\instance) -U(username)
Password: HResult 0xFFFFFFFF, Level 16, State 1
SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFF
FF].
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : A network-related or in
stance-specific error has occurred while establishing a connection to SQL Server
. Server is not found or not accessible. Check if instance name is correct and i
f SQL Server is configured to allow remote connections. For more information see
SQL Server Books Online..
Sqlcmd: Error: Microsoft SQL Server Native Client 10.0 : Login timeout expired.

Error access CF8 to Microsoft SQL Server 2008

Hello!
I have created a database in SQL Server 2008.
Further, in CF Administrator Add New Data Source - also there is an error.
Connection verification failed for data source: dbo.Articles
java.sql.SQLException: [Macromedia][SQLServer JDBC Driver]Error establishing socket to host and port: localhost:1433. Reason: Connection refused: connect
The root cause was that: java.sql.SQLException: [Macromedia][SQLServer JDBC Driver]Error establishing socket to host and port: localhost:1433. Reason: Connection refused: connect
Prompt how to solve this problem?

What is the solution?
I have the same thing with SQL Server 2008 64 bit. When i switch my datasource from SQL 2008 to SQL 2000 it works great otherwise it will not work. I have checked SQL Server 2008 that all the ports show 1433. I have been stuck on this for a while. I also checked the SQL Server Network Configuration / TCP/IP and i have nothing in the dynamic field and all the ports show 1433. If someone has allready figured this out it would be good to have a solution- Especially since coldfusion is supposed to connect to the database....
Thanks for any help.

HSODBC connectivity between ORACLE 10g and SQL Server 2008 R2

Hi,
I'm getting below error when using the DB link between Oracle (10.2.0.2 which is on Sun Sparc) and MS Sql server 2008 R2.
ERROR at line 1:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[Generic Connectivity Using ODBC][Microsoft][ODBC Driver Manager] Data source
name not found and no default driver specified (SQL State: IM002; SQL Code: 0)
ORA-02063: preceding 2 lines from SCOPEX.WORLD
My Config files:
On Sun Sparc 5.9 where Oracle server is running.
TelemetryDB1 =
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=172.16.6.48)(PORT=1522))
(CONNECT_DATA=(SID=TelemetryDB1))
(HS=OK)
Listener.ora file on Windows machine:
TelemetryDB1 =
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=tcp)(HOST=172.16.6.48)(PORT=1522))
(ADDRESS=(PROTOCOL=ipc)(KEY=PNPKEY))
SID_LIST_TelemetryDB1 =
(SID_LIST=
(SID_DESC=
(SID_NAME=TelemetryDB1)
(ORACLE_HOME=C:\oracle\product\10.2.0\db_1)
(PROGRAM=hsodbc)
Tnsnames.ora file:
TelemetryDB1 =
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=172.16.6.48)(PORT=1522))
(CONNECT_DATA=(SID=TelemetryDB1))
(HS=OK)
initTelemetryDB1.ora file under ORACLE_HOME\hs\admin\
HS_FDS_CONNECT_INFO = TelemetryDB1
HS_FDS_TRACE_LEVEL = OFF
We have created DNS with TelemetryDB1.
I'm getting the above error for DB links between Oracle 10.2 and SQL Server 2008 R2. But the same, when configured for MS SQL server 2000 works fine without any issues.
Please advise me to rectify the error. We've been working for the last couple of weeks.
Regards,
Sunil

Sunil,
You don't need an Oracle ODBC driver.
The way it works is that in the gateway init<sid>.ora file, in your case initTelemetryDB1.ora, the parameter HS_FDS_CONNECT_INFO points to a system DSN. This DSN should then be configured to use an ODBC driver to connect to the non-Oracle database. So, in your setup when you want to access the SQL*Server 2008 database then the DSN should use an ODBC driver that can connect to a SQL*Server 2008 database. If you still use the initTelemetryDB1.ora file for the connection then the TelemetryDB1 DSN should be configured to access the SQL*Server 2008 database.
However, there are a couple of problems with your actual setup -
- the configuration you have - 10.2 RDBMS on a Sun machine and HSODBC on Windows - is not supported. HSODBC should only be used from a RDBMS that is in the same ORACLE_HOME as HSODBC.
- 10.2 HSODBC is now desupported and has been replaced by the 11g Database Gateway for ODBC (DG4ODBC) and the configuration you want is supported. That is because unlike HSODBC the DG4ODBC gateway can be installed standalone with a RDBMS being installed.
I recommend that you download and install 11.20.2 DG4ODBC on your Windows machine in a new Oracle_home and access that from the 10.2 RDBMS on Sun - which is a supported configuration. But to do this, you will need to apply either the 10.2.0.4 or 10.2.0.5 patchset to your RDBMS.
There is more information in the following note available on My Oracle Support (MOS) -
Note.1083703.1 Master Note for Oracle Gateway Products
The 11.2.0.2 DG4ODBC can be downloaded from MOS as patch and for the gateways on Windows 32-bit you just need to download -
p10098816_112020_platform_4of6.zip
However, to check the HSODBC ou need to confirm that the DSN used by HSODBC points to a System DSN configured to access SQL*Server 2008.
Have a look at -
Note 109730.1 How to setup generic connectivity (HSODBC) for Windows NT
But remember this is not a supported version or configuration and you should be using Dg4ODBC.
Regards,
Mike

Upgrade sql server 2008 to 2008R2 and apply Service pack 3

Hello,
I have a two node cluster (sql server 2008). I would like to upgrade to SQL Server R2 and at the same time would like to patch to Service Pack 3. What would be the best way to accomplish this task with minimal downtime to the users?
This is my plan:
1. Detach any read only databases.
2. Upgrade to 2008 R2 (shared feature only) on passive node (node1).
3. Apply SP3 on passive node in step 2.
4. Swith active node to passive node (node2).
5. Upgrade to 2008 R2 (shared feature only) on node2.
6. Apply SP3 on node2.
7. Upgrade db (instance) on node2 to 2008 R2.
8. Upgrade db (instance) on node1 to 2008 R2.
9. Re-attach read only databases.
Is my procedures correct?
Thank you.

Hello,
Have you seen the following article before?
http://msdn.microsoft.com/en-us/library/ms191295(v=sql.105).aspx
You can slipstream SQL 2008 R2 + SP3.
http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server 2008 R2 on Windows 2012 R2

It appears I cannot install SS2008 R2 on WS2012 R2. I get the following:
'Your version of Microsoft SQL Server (2008 and 2008 R2) isn't compatible with this version of Windows.'
Can someone please confirm this and when this issue might be resolved?

Hello,
Please try a slipstream installation of SQL Server 2008 R2 + SP2 using the following article:
http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server 2008 R2 & 2008 R2 SP1 installation fails in Windows server 2012

Hi All,
I have a strange issue here. I have a Windows server 2012 VM where i want to deploy SQL 2008 R2 Enterprise edition.
When i Run the setup every thing goes fine and during the installation wizard i get this error " The Folder path Program files contains invalid characteristics. I get this error 3 - 4 times during the installation wizard and the installation fails.
Below is the screenshot for the same.
So i checked few articles regarding the compatibility issue and found the below article and upgraded my setup to SQL 2008 R2 SP1 using the below article.
http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
Again i still see the same above errors and with that a new error related to a MOF File.
Below are the contents of the error logs. Can some one assist on this issue.
======================================================
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): -2068052692
Exit facility code: 1212
Exit error code: 1324
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2015-01-15 13:53:03
End time: 2015-01-15 14:04:29
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\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.2500.0%26EvtType%3d0xA60E3551%400xD3BEBD98%401211%401
Machine Properties:
Machine name: ALPCLDSCOM01
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
Installation location: D:\SQLServer2008R2_SP1\x64\setup\
Installation edition: ENTERPRISE
Slipstream: True
SP Level 1
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: E2KLAB\SCOMAC
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Automatic
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE: D:\SQLServer2008R2_SP1\SP
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: E2KLAB\SCOMAC
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: E2KLAB\SCOMAC
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: E2KLAB\Gautamr,E2KLAB\SCOMAC,E2KLAB\SCOM Admins
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Feature: Full-Text Search
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: 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: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\sql_common_core_loc_Cpu64_1033_1.log
MSI error description: The folder path 'Program Files' contains an invalid character.
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\SystemConfigurationCheck_Report.htm
Gautam.75801

Hi Alberto,
Still the same issue.
I installed the SQL 2008 R2 without SP1 and changed the service accounts to system account and repaired the .NET using the .NET Repair tool
Also changed the installation directory to D:\ Drive this time. Still same issue.
log file:
===============
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): -2068052692
Exit facility code: 1212
Exit error code: 1324
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2015-01-15 22:55:37
End time: 2015-01-15 23:07:32
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SQLSysClrTypes_Cpu64_1.log
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.2500.0
Machine Properties:
Machine name: ALPCLDSCOM01
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 1
Installation location: D:\SQL Server 2008 R2 Datacenter edition for only Windows server 2008 R2\x64\setup\
Installation edition: ENTERPRISE
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Automatic
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: False
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
FTSVCPASSWORD: *****
HELP: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: D:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: D:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: D:\Program Files\Microsoft SQL Server\
INSTANCEID: MSSQLSERVER
INSTANCENAME: MSSQLSERVER
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSVCACCOUNT: NT AUTHORITY\SYSTEM
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: E2KLAB\Gautamr
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 1
UIMODE: Normal
X86: False
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Feature: Full-Text Search
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: 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: Failed: see details below
MSI error code: 1324
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
MSI error description: The folder path 'Program Files (x86)' contains an invalid character.
Configuration status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SystemConfigurationCheck_Report.htm
Any other suggestion i can try ?
Gautam.75801

Windows Installer - SQL Server 2008 Express Errors

I am working with an application that was developed for an XP machine. One of my peers took the old Windows application and using Visual Studio 2010 upgraded the application to work on a Windows 7 machine. We are creating the installer (.exe
and .msi) files within Microsoft Visual Studio 2010, but we are having different issues on different machines that we try to run the setup.exe file on.
On our company computers with Windows 7, the setup.exe file runs and works properly.
On our customers computer with Windows 7, received the following error: "an error occurred attempting to install SQL Server 2008 Express Service Pack 1."
On non-company/non-customer machines, we tried two Windows 7 machines. One machine had no issues and everything installed perfectly and the other received this error: "Component SQL Server 2008 Express has failed to install."
User pressed Yes to reboot the computer.
After the reboot, the setup.exe file was run and there were no more errors. The application was installed properly.
Within the Installer we have four boxes checked under Properties - Prerequisites:
Microsoft .NET Framework 4 (x86 and x64)
Microsoft .NET Framework 4 Client Profile (x86 and x64)
SQL Server 2008 Express
Windows Installer 3.1
If anyone can help with why the installer is causing issues on some computers and not on others as well as why the issues by computer are different that would be very helpful!
Thank you!

Hi,
Please refer to this article for troubleshooting installation of
SQL Server Express:
http://social.technet.microsoft.com/wiki/contents/articles/1146.sql-server-express-troubleshoot-installation.aspx
Check Summary.txt in the <SQLInstallFolder>\100\Setup Bootstrap\Log and see if you need to apply the Hotfix in the
KB 957453.
Thanks.
Tracy Cai
TechNet Community Support

SQL Server 2008 R2 Setup Very Slow

Hi,
We have a multi-node SQL Server 2008 R2 Failover Cluster.
I've noticed that the SQL Server 2008 R2 Setup is extremely slow and that it appears to only be using 1 of the 128 "CPUs" (i.e. in Task Manager).
We use this for creating new cluster groups and alike.
Is this tool only single threaded and is there a way to increase the performance? Our CPUs are 2.something GHz, we have 512GB of RAM and fast local disks.
Thanks

Hello,
What happen if you slipstream the SQL Server 2008 R2 with the latest SQL Server 2008 R2 service pack? Maybe SQL Server setup does better after the slipstream process.
http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
http://msdn.microsoft.com/en-us/library/dd638062(v=sql.105).aspx (Slipstream a SQL Server 2008 R2
Update)
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server 2008 compatibility with SAP PI 7.0

Hi All
Scenario is like this:
XI is fetching data from SQL Server.
Previously we were using SQL Server 2005 and XI was successfully fetching data from it.
Communication channel setting:
JDBC Driver : com.microsoft.sqlserver.jdbc.SQLServerDriver
Connection : jdbc:sqlserver://10.10.100.180;user=abc;password=xyz;database=CUSTOMER
Two days back SQL team uninstalled SQL Server 2005 and installed SQL Server 2008
After doing this XI stopped fetching data from SQL and error is "Error during database connection to the database URL 'jdbc:sqlserver://10.10.100.184;user=sqluser;password=india123;database=CUST_HO' using the JDBC driver 'com.microsoft.sqlserver.jdbc.SQLServerDriver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:sqlserver://10.10.100.184;user=sqluser;password=india123;database=CUST_HO': com.microsoft.sqlserver.jdbc.SQLServerException: The server version is not supported. The target server must be SQL Server 2000 or later."
Please help me how to solve this problem.
Regards
Dheeraj Kumar

Hi Prateek
As far as i know if i will load JDK5 then netweaver will not work. i asked to basis person too he also told me the same thing.
We even tried to load another driver got from microsoft website - sqljdbc_2.0.1803.100_enu.exe
after updating this driver i got error - "Error during database connection to the database URL 'jdbc:sqlserver://10.10.100.184;user=sqluser;password=india123;database=CUST_HO' using the JDBC driver 'com.microsoft.sqlserver.jdbc.SQLServerDriver': 'com.sap.aii.adapter.jdbc.sql.DriverManagerException: Cannot establish connection to URL 'jdbc:sqlserver://10.10.100.184;user=sqluser;password=india123;database=CUST_HO': UnsupportedClassVersionError: com/microsoft/sqlserver/jdbc/SQLServerDriver (Unsupported major.minor version 50.0)'"
Regards
Dheeraj kumar

Siebel 8.1 and MS SQL Server 2000

I am upgrading our Siebel 7.8 instance running on MS SQL Server 2000 to Siebel 8.1 and MS SQL Server 2008. My original intent was to upgrade the database first (so that we would be runing Siebel 7.8 on MS SQL Server 2008), and then upgrade the application to 8.1.
I have been running into resource issues with regard to the SQL Server upgrade. My question is:
Can Siebel 8.1.1 run on MS SQL Server 2000?
Thanks.
-- Ken

Hi
You can migrate your 7.8 to MSSQL 2008 as this is a supported platform.
Usually in an upgrade you will upgrade your development db platform as a source of your 8.1 upgrade process.
For information, a reference document is the Siebel System Requirements and Supported Platforms aka SRSP
[SRSP 7.8|http://download.oracle.com/docs/cd/E11886_01/V7/CORE/SRSP_78/SRSP78.pdf]
[SRSP 8.1| http://download.oracle.com/docs/cd/E11886_01/V8/CORE/SRSP_81/SRSP_81.pdf]
Please refer to the online version as this document is frequently updated.
Enjoy
Evtloglvl

JTDS not connecting with SQL Server 2008 R2 SP2 + SSL with Java 6 U34-35

Environment:
Windows 7 Pro 32-bit
SQL Server 2008 R2 SP2 (Forced Encryption = Yes, No Certificate provided to server)
Java 6 Update 27-35 and Java 7 Update 2-7
jTDS 1.2.2 and 1.2.6
Under the following setup, our Java application is able to connect to the SQL Server database:
- SQL Server 2008 R2 SP2
- Java 6 Update 27-33 or Java 7 Update 2-5
just switching the JVM to the following would cause the application to be unable to connect to the database:
- Java 6 Update 34 or 35, or Java 7 Update 6 or 7
Browsing through the Java 6 Update 34 release notes, it looks like nothing big was changed, so I'm wondering what has changed with Java 6 U34 and Java 7 U6. I was also looking through a packet sniffer, and indeed the behavior of Java 6 Update 33 and lower was different from Java 6 Update 34 (although I couldn't understand the messages being passed, the number of connections and messages were different).
* This is different from the issue with Java 6 Update 29-30 and Java 7 wherein they were patched for the BEAST SSL vulnerability. That was fixed with the SP2 patch for SQL Server 2008 R2, and for SQL Server 2008 you'd need a hotfix aside from SP3. After patching the server with those updates, Java 6 Update 29-33 and Java 7 U1-5 should be able to connect to the database.
* If I do switch off Force Encryption, all Java versions are able to connect to the database.
Edited by: user1357749 on Oct 12, 2012 1:20 AM

Hi,
It's four months later, but my colleague and I have reproduced the same behavior in both our commercial product, and a very simple example class. It's exactly as you describe it, where the latest versions of both Java 6 and 7 (and several previous versions) hang during the first jTDS SQL query to the DB (immediately after the SSL and handshake). It also happens with the Microsoft JDBC driver.
If you disable the BEAST SSL fix (-Djsse.enableCBCProtection=false), then the connections work without any problems. So, while this is different from the original BEAST SSL problem and subsequent fix, it really seems like some additional changes were made to the fix in a later Java release that broke things.
My colleague has filed a bug with Oracle, and is awaiting a response. We also filed a bug at the jTDS project (#690 - http://sourceforge.net/p/jtds/bugs/690/) that has simple reproduction steps. A contributer at the jTDS project agrees that this seems to be a problem with the JRE, and is not specific to jTDS.
I hope that Oracle will address this issue soon. We need to periodically update the JRE due to vulnerabilities, and we need to have SSL for our JDBC connections for security reasons. This bug puts us and others in a difficult position.

Creating dynamic database connection (SQL server 2008) from Adf application

Hello,
I am creating an ADF Fusion Application. I use Jdev. 11.1.2.3.0 , WebLogic 10.3 and MS SQL server 2008 database. My question is that how can I create a database connection configuration file, now I connect to the database through hard coding, there should be a way to do this with sql server I think.
my database name is : testDatabase
my database username is : testUser
my database password is : testPassword
Anybody can help me please.
Thanks,
Shahe

Hello Frank,
The database schema is the same for all the users, but the location of the database differs, for example: I have set the hostname of the database to localhost because the database is installed on the local pc, but to other clients the database is installed on a managed server so in the hostname I should put the server's ip address or name. So I need an external file where I can set these options.
Thanks,
Shahe

Disaster Recovery-MS SQL Server 2008 License

We are planning to build a Disaster Recovery environment for Production Environment. Technology used: SharePoint Foundation2010, MSBI and MS Sql Server 2008 Standard.
Current Production Server has SQL Server2008 standard (Core license) installed in it.
Do we need separate MS SQL Server 2008 licence for Disaster Recovery (DR) Server in order to keep the DR and Production database running in both the environments simultaneously.
We don't want to keep database down in DR environment as this impacts our code deployment process.
Each time code gets deployed to Production, we will have to follow few extra steps to keep DR and Production in sync.
Example:
1. Bring up the MS SQL Server database in DR environment
2. Deploy the solution and bring down the DR database.
Please suggest...

We are planning to build a Disaster Recovery environment for Production Environment. Technology used: SharePoint Foundation2010, MSBI and MS Sql Server 2008 Standard.
Current Production Server has SQL Server2008 standard (Core license) installed in it.
Do we need separate MS SQL Server 2008 licence for Disaster Recovery (DR) Server in order to keep the DR and Production database running in both the environments simultaneously.
We don't want to keep database down in DR environment as this impacts our code deployment process.
Each time code gets deployed to Production, we will have to follow few extra steps to keep DR and Production in sync.
Example:
1. Bring up the MS SQL Server database in DR environment
2. Deploy the solution and bring down the DR database.
Please suggest...
Yes you will need license for SQL server in DR environment.
Licensing is wast and non technical question so it will be best answered by Licensing expert.
For more detailed information regarding to the license issue, please call 1-800-426-9400Call: 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00
P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. For international customers, please use the Guide to Worldwide Microsoft Licensing Sites to
Find contact information in your locations.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

CF8 and MS SQL Server 2008

Similar Messages

Maybe you are looking for