MX7 SQL Server 2005 datasoucre error
Webserver is Windows 2003 RC2, MX7.02
SQL Server is Windows 2003 RC2, SQL Server 2005 (9.0.1399)
CF and SQL are on seperate machines
[edit: the fix]
OK, gotta love those netops guys.
So we were narrowing it down to server -> server
communication issues...specifically windows authentication.
We set up a SQL Server user on the SQL Server and set up the
datasource in coldfusion that used that SQL Server user (not
DOMAIN\user, just user) and skipped the whole System DSN on the
webserver and it works.
So the long and the short of it is that there seems to be
some network trust issue between our app server (cf) and our db
server (sql) and we are unable to set up datasources the way we
used to (from win2k/cf5 -> win2k3/sql2005). Oh well.
[/edit]
[Edit: additional info]
SQL Server logs give this error message:
Error: 18456, Severity: 14, State: 6.
I've looked up this error message on msdn (
http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx)
and they say it means "Attempt to use a Windows login name with SQL
Authentication"
I've made sure that SQL Server is running in "SQL Server and
Windows Authentication Mode" (and restarted). No change. Of course
Adobe says that you HAVE to use "SQL Server and Windows
Authentication Mode" and Microsoft say the fix to the error is to
chose "Windows Authentication Mode". Grrr.
I've tried changing the JDBC URL to the IP of the SQL Server
and I get the same error mesaage. I purposely fudge the IP and I
get a totally different "time out" error (duh ;^) So something
about the way Cold Fusion talks to SQL Server isn't quite right.
I feel dumb asking this, but is there any specific
documentation about connecting MX7 to SQL Server 2005? The
documenation on livedocs refers to SQL Server 2000 (I think...but
I'm sure it's not talking about 2005). I'm beginning to wonder if
there is some stupid little step that I missed somewhere along the
way when setting things up...*sigh*
[/Edit]
I get the following error when attempting to set up the
datasource in Coldfusion administrator:
Connection verification failed for data source: wamaxDS
com.microsoft.sqlserver.jdbc.SQLServerException: Login failed
for user 'UWT\cfusion2'.
The root cause was that:
com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for
user 'UWT\cfusion2'.
Now, I've got our production box which is running CF 5
connecting to the same database on the same SQL server and does NOT
get the 'Login failed for user' error...which leads me to believe
that it's not a simple permissions issue. To be clear my CF5 box
connects fine to the database. My CF7 box simply will not.
I've installed the latest JDBC drivers and set up a
datasource that generates the error above (I get the same error
when trying to set it up as "Microsoft SQL Server" with the obvious
exception of the driver in the error being different).
I've searched the forums and did the TCP/IP fix.
I've tried setting the ODBC DSN up in windows using "windows
authentication" and the "mixed mode"...I'm just lost here.
I've lost track of the combinations of things I've tried to
get this to work (ya know how you get into "try anything and pray
mode"?...that was me all day today).
Hopefully I've provided enough information to get someone
started on helping me. If I've left anything out, please chastise
me and then let me know what I need to let you know. Sorry if this
message is incoherent...my brain is mush *sigh*.
Hi,
I presume, this is how you have placed your code
Code Snippet
-- Retrive the product archive record
select * from dbo.api_userArchive where isActive = 1
Seems just fine. Could you post the error. Also try posting the entire code
HTH,
Suprotim Agarwal
http://www.dotnetcurry.com
Similar Messages
-
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 -
Error: [Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
hello,
our application vendors are receving the below errors while running their data load job.I spoke to our networking team member and he said everything looks good on the networking side .Can someone please help me with the below errors.we are using
Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64) Enterprise
Edition: Core-based Licensing (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1).
Windows OS:windows server 2008 R2 sp1
7280
6920
DBS-070401
6/5/2014 1:17:24 PM
|Data flow DIM_CONTRACT_SWAM_INIT_LOAD_DF|Loader Key_Generation_DIM_CONTRACT
7280
6920
DBS-070401
6/5/2014 1:17:24 PM
ODBC data source <HPWDBOE001> error message for operation <SQLExecute>: <[Microsoft][ODBC SQL Server
7280
6920
DBS-070401
6/5/2014 1:17:24 PM
Driver][DBNETLIB]ConnectionWrite (send()).
7280
6920
DBS-070401
6/5/2014 1:17:24 PM
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.>.
6760
6164
DBS-070401
6/5/2014 1:17:24 PM
|Data flow DIM_EMPLOYER_GROUP_SWAM_INIT_LOAD_DF|Reader TCRdr_9
6760
6164
DBS-070401
6/5/2014 1:17:24 PM
ODBC data source <serverName> error message for operation <SQLExecute>: <[Microsoft][ODBC SQL Server Driver]Protocol error in
6760
6164
DBS-070401
6/5/2014 1:17:24 PM
TDS stream
6760
6164
DBS-070401
6/5/2014 1:17:24 PM
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
6760
6164
DBS-070401
6/5/2014 1:17:24 PM
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.>.
I googled and found the below link the below link which asked me to enable named pipes.I enabled
namped pipes in the sql server Network configuration.I havent yet restarted the sql services as this is a prod box.I will do it later in the evening today.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/69149a71-3c15-4c95-9f95-a30db458abeb/sql-server-2005-communcations-errors-through-odbc?forum=sqldataaccess
Can someone help me with these errors.
Thanks
luckyThank you Erland.
I dont see any crash dumps in sql server.I checked the tcp chimney and its set to automatic.I am not knowing what to look at to resolve this issue.
if its the issue with the client API can i ask our vendor to check the client?
Our networking member gave the following report:
No problems on vlan 14 or your port the top is from the switch to your server then bottom is from my pc to your server
SP_DC_CORE_VSS# ping 10.10.12.228
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.12.228, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
SP_DC_CORE_VSS#
lucky -
Error"Failed to open the connection" - Named Instance of SQL Server 2005
"Failed to open the connection" error, when connecting to the Named Instance of SQL Server 2005
The report is throwing error, when changing the logon information dynamically through C#.
Code
string reportPath = @"D:\NET\TestReport\TestReport.rpt";
ReportDocument reportDocument = new ReportDocument();
reportDocument.Load(reportPath);
foreach(CrystalDecisions.CrystalReports.Engine.Table table in tables)
TableLogOnInfo tableLogonInfo = table.LogOnInfo;
tableLogonInfo.ConnectionInfo.ServerName = @"TestServer\Instance1"; //Connnecting to Named instance of SQL Server 2005
tableLogonInfo.ConnectionInfo.UserID = "sa";
tableLogonInfo.ConnectionInfo.Password = "password";
tableLogonInfo.ConnectionInfo.DatabaseName = "TEST_DB";
table.ApplyLogOnInfo(tableLogonInfo);
crystalReportViewer1.ReportSource = reportDocument;
Error Message
Failed to open the connection.
Failed to open the connection.
C:\DOCUME1\PUGALE1\LOCALS~1\Temp\{DF9593A5-5C80-4CBC-ABC3-EC4EF204A7EB}.rpt
The error is occuring only whenever i am connecting to the Named Instance of SQL Server 2005.
Thanks in Advance
Edited by: pugalendran p on Feb 2, 2009 10:32 AM
Edited by: pugalendran p on Feb 2, 2009 10:43 AMHi,
Following solution might help you to resolve the issue.
Solution1:
Issue happens because universe connection to the Database is not responding and the Data Source Name is not configured to write SQL Server 2005 database.
Resolution
Created new DSN connection under SYSTEM DSN to SQL Server 2005 Database.
Import the universe from the designer.
Go to File->Parameters.
Edit Connection.
On the Database Middleware Page expand SQl Server 2005->Select SQL Server 2005 driver.
Change the DSN to new DSN connection
Test the connection.
Save the Universe and Export it to the repository.
Solution2:
I am taking Oracle as an example over here.
This can be caused when the SQLNET.ora is located in a remote location using mapped drives.
Resolution
To resolve,
check the registry [HKLM\SOFTWARE\ORACLE] you should see a folder called HOME0
look for any paths that contain a mapped drive partition
Change the mapped drive letter to a UNC path (
server\folder)
Open a command prompt and do a tnsping using the tnsname and verify the location of the SQLNET.ora or TNSNAMES.ora
If the path is not updated to the new path
Reboot the server
Regards,
Sarbhjeet Kaur -
Error while installing SQL Server 2005 SP3
I have installed SQL Server 2005 Standand Edition (32-bit) on a standalone server machine running
Windows Server 2003 R2 Standard 64-bit with Service Pack 2. After installing SQL Server, when I tried installing the Service Pack 3 (as per application requirement) through local administrator account, I am repeatedly getting below error in
"C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB955706_SqlSupport.msi.log"
SECUREREPAIR: SecureRepair Failed. Error code: 4ec4E6A3388
MSI (s) (F8:40) [16:49:33:515]:
Error 1260. Windows cannot open this program because it has been prevented by a software restriction policy.
I have checked rights on the folders and also got the anti-virus (symantec) services stopped on the server. Still no success, can anyone help.I have installed SQL Server 2005 Standand Edition (32-bit) on a standalone server machine running
Windows Server 2003 R2 Standard 64-bit with Service Pack 2. After installing SQL Server, when I tried installing the Service Pack 3 (as per application requirement) through local administrator account, I am repeatedly getting below error in
"C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB955706_SqlSupport.msi.log"
SECUREREPAIR: SecureRepair Failed. Error code: 4ec4E6A3388
MSI (s) (F8:40) [16:49:33:515]:
Error 1260. Windows cannot open this program because it has been prevented by a software restriction policy.
I have checked rights on the folders and also got the anti-virus (symantec) services stopped on the server. Still no success, can anyone help.
Just to add: Have already referred
http://support.microsoft.com/kb/918357 -
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 While Installing IDES ECC6 with SQL Server 2005
Dear Experts,
I found an error while installing IDES ECC6 with SQL Server 2005. The error is raising at the stage of 17 of 24 processing the procedure of 195 of 197 (sap_z_set_permissions).
I have tried several times by configuring different type of activites but still i am facing the same problem at the same stage. Please help me in thig regard.
I herewith pasted hereunder log files information
Regards,
B.Sudharsan
ERROR 2008-01-17 18:38:47
FCO-00011 The step ExeProcs with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_MSS|ind|ind|ind|ind|2|0|MssProcs|ind|ind|ind|ind|1|0|ExeProcs was executed with status ERROR .
INFO 2008-01-17 18:40:05
An error occured and the user decide to stop.\n Current step "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_MSS|ind|ind|ind|ind|2|0|MssProcs|ind|ind|ind|ind|1|0|ExeProcs".
ERROR 2008-01-17 18:38:47
MDB-05053 Errors when executing sql command: <p nr="0"/> If this message is displayed as a warning - it can be ignored. If this is an error - call your SAP support.Sudarshan,
Occasionally, mid-way through the upgrade, DB permissions to users might change. Check to see, if the users SAP<SID>, OPS$ users have the DBA privilege. Re-assign the role and try continuing with the upgrade. -
Error when creating a FDM application on SQL Server 2005
Hi,
we are getting this error when creating a FDM application on SQL Server 2005
Error: EPMCSS-07003: Failed to validate identity. Invalid identity . Check identity.[SET_ROLES_LIST]
We are using Windows System Integration although we have also tested with sa user.
Any ideas?
ThanksBased on the error message it appears to be having a Shared Services issue. Verify that the "ADMIN" account is being used for the HSS connection and that you are using "ADMIN" to create the application and see if the same error is returned.
-
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 -
SQL Server 2005 Error Message - when Right Clicking a DB Properties
Hi
We are running SQL Server 2005 SP03, we have x15 databases (excluding SBO-COMMON, RSP, Coresuite), all x15 databases have Maintenance Plans setup, tasks ticked:
- Shrink Database
- Clean Up History
- Back up Database (Full)
- Maintenance Clean-up task
These Maintenance Plans have been running for over 5 months now, we have recently changed our VMware Virtual Server over to a Hosted VMware Virtual Server, now when I right click on a certain database and select "Properties" I get the following error message with SQL Server:
Property Owner is not available for Database '[Turquoise_Moon_Live]'. This property may not exist for this object, or may not be retrievable due to insufficient access rights. (Microsoft.SqlServer.Smo)
Could the Maintenance Plan be preventing me to run the Properties against a relevant DB (I have tested this by restoring a DB that doe not have a Maintenance Plan and the Properties works, tested this on SBO-COMMON and it works as well)
Can anyone agree with me or let me know what else might be the issue as I have checked the Server Roles & the Users Credentials for SQL and all seems well.
Regards
Kurt WaltersHi Gordon
This solution did not work, but I needed to delete the Maintenance Plans anyway to set it for 1 month instead of 2 Months. I am thinking as we have changed Domains, were the last one was IS Domain and the new one is Hosted Domain, the security issues are probably coming from this (as I am able to access the Properties of the IS Domain SQL Server even with the Maintenance Plans running).
Any thoughts on correcting this as we have changed Domains? (I have created a user as HOSTED\example, the old one was IS\example)
Regards
Kurt Walters -
SQL Server Error when tryingt to install the CMS DB on SQL Server 2005 x64
I am trying to install BOEXI R3 on w2k3 64-bit OS in a SQL Server 2005 x64 database, I am currently at the installation step where i Specify an exisiting CMS database. I created a System DSN and tested it, and it was successful. So when I got to the screen where I select my datasource I had to check use trusted connection because the datasource would not show up when Use DSN created by WOW64 option was checked. From there I could select the database I created. Oh yeah, I also made the application server local system account part of my DB admins group so it has full access to the database yet when I click next to connect I get a CMS Database Error: STU000226. here is what I have in my log:
ThreadID Message
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: findDFA_LLR: (CmdLineDir) C:Documents and SettingsgsdadminDesktopBOEXI and BSM AnalyticsBOEXI R3 Full Version from SAPpackagedbcheck
sqlrule.llr
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: Loading: database subsystem only
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: loading libary succeeded
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: DatabaseSubsystem::Init()
(Thu Apr 23 20:57:46 2009) 3024 3028 (.wireobinit.cpp:96): trace message: Creating the shared CWireObject::PropertyNameMap
(Thu Apr 23 20:57:46 2009) 3024 3028 (.wireobinit.cpp:118): trace message: Setting static property map
(Thu Apr 23 20:57:46 2009) 3024 3028 (.wireobinit.cpp:125): trace message: CWireObject::InitializeStaticPropertyMap() - reference count: 1
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: initializing subsystem succeeded
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: Loading: done loading subsystem - database subsystem only
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: DatabaseSubsystem::Connect()
(Thu Apr 23 20:57:46 2009) 3024 3028 (.DBConnectionManager.cpp:802): trace message: DBConnectionManager - Setting total target number of connections for pool 0 to 1.
(Thu Apr 23 20:57:46 2009) 3024 3028 (.SQLServerDatabase.cpp:119): trace message: SQLServer error found: ErrorMessage( (Microsoft)[ODBC Driver Manager] Data source name not found and no default driver specified), ErrorCode(0)
(Thu Apr 23 20:57:46 2009) 3024 3028 (.dbutils.cpp:820): trace message: Caught DatabaseSubystem Error: BusinessObjects Enterprise CMS: Unable to connect to the CMS system database "BOEXI_CMS". Reason: (Microsoft)[ODBC Driver Manager] Data source name not found and no default driver specified
(Thu Apr 23 20:57:46 2009) 3024 3028 trace message: DatabaseSubsystem::Shutdown()
(Thu Apr 23 20:57:46 2009) 3024 3028 (.wireobinit.cpp:175): trace message: CWireObject::TerminateStaticPropertyMap() - reference count: 1
(Thu Apr 23 20:57:46 2009) 3024 3028 (.wireobinit.cpp:182): trace message: Releasing
static property map
How do I get past this?The workaround was, I installed the SQL Server Client tools and created a System DataSource and then had to create a user DataSource (it is a quirk in the installer I guess) to get past this point in the installation. Now I have an even bigger problem. Everything but the CMS installed and the installer hung at the "Configuring the CMS" part. The installation finished but when I tried to log into the Central managment console I got this error:
Error: Server GSD-RRPT-RDC:6400 not found or server may be down (FWM 01003) null
I looked at the forums for the cause of this error and came to the conclusion that BOEXI does not support an installation on SQL Server 2005 when using Integrated Authentication to the SQL Server. See the engineers here disabled SQL Authentication for the SQL Server and will not allow it.
Is this true? Or is there a workaround to install the CMS using Integrated Authentication in the DataSource ?
Thanks. -
Hi All,
Here the linked server is created between sql server 2012 64 bit and sql server 2005 32 bit. I am getting the below error when i try to access linked server from third server. I have created linked from Instance 1 to Instance 2. When i access it from
instance 3 i am getting the below error. SPN setting has been done between these 2 servers. Also the option 'Trust the delegate' is enabled for the both the service account.
'Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
Appreciate your quick response.
Vikas.M.SHello,
Please read the following resources:
http://www.databasejournal.com/features/mssql/article.php/3696506/Setting-Up-Delegation-for-Linked-Servers.htm
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/ea26de43-4c6b-4991-86d7-e1578f107c92/linked-server-login-failed-for-user-nt-authorityanonymous-logon?forum=sqldataaccess
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Hi team,
I got below error message in SQL Server 2005 reporting service.
''The report server is not responding. Verify that report server is running and can be accessed from this computer'
also in reports, i am getting below error:
"The encrypted value for the "LogonCred" configuration setting cannot be decrypted. (rsFailedToDecryptConfigInformation)
Get Online Help
The report server has encountered a configuration error. See the report server log files for more information. (rsServerConfigurationError)
Get Online Help "
Please find below log:
<Header>
<Product>Microsoft SQL Server Reporting Services Version 9.00.4060.00</Product>
<Locale>en-US</Locale>
<TimeZone>Eastern Daylight Time</TimeZone>
<Path>F:\Program Files\Microsoft SQL Server\MSSQL.6\Reporting Services\LogFiles\ReportServer__07_28_2014_09_08_41.log</Path>
<SystemName>MFLDDDBS04</SystemName>
<OSName>Microsoft Windows NT 5.2.3790 Service Pack 2</OSName>
<OSVersion>5.2.3790.131072</OSVersion>
</Header>
w3wp!webserver!1!7/28/2014-09:08:41:: i INFO: Reporting Web Server started
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing ConnectionType to '1' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing IsSchedulingService to 'True' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing IsNotificationService to 'True' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing IsEventService to 'True' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing PollingInterval to '10' second(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing WindowsServiceUseFileShareStorage to 'False' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing MemoryLimit to '60' percent as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing RecycleTime to '720' minute(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing MaximumMemoryLimit to '80' percent as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing MaxAppDomainUnloadTime to '30' minute(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing MaxQueueThreads to '0' thread(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:41:: i INFO: Initializing IsWebServiceEnabled to 'True' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing MaxScheduleWait to '5' second(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing DatabaseQueryTimeout to '120' second(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing ProcessRecycleOptions to '0' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing RunningRequestsScavengerCycle to '60' second(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing RunningRequestsDbCycle to '60' second(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing RunningRequestsAge to '30' second(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing CleanupCycleMinutes to '10' minute(s) as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing WatsonFlags to '1064' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing WatsonDumpOnExceptions to 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException' as specified in Configuration
file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing SecureConnectionLevel to '0' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.
w3wp!library!1!7/28/2014-09:08:42:: i INFO: Initializing WebServiceUseFileShareStorage to 'False' as specified in Configuration file.
w3wp!resourceutilities!1!7/28/2014-09:08:42:: i INFO: Reporting Services starting SKU: Enterprise
w3wp!resourceutilities!1!7/28/2014-09:08:42:: i INFO: Evaluation copy: 0 days left
w3wp!library!1!7/28/2014-09:08:42:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information., CryptUnprotectData:
Win32 error:13;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information.
w3wp!library!1!7/28/2014-09:08:42:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.FailedToDecryptConfigInformationException: The encrypted value for the "LogonCred" configuration setting cannot be decrypted., ;
Info: Microsoft.ReportingServices.Diagnostics.Utilities.FailedToDecryptConfigInformationException: The encrypted value for the "LogonCred" configuration setting cannot be decrypted. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
The report server has encountered a configuration error. See the report server log files for more information.
at Microsoft.ReportingServices.Diagnostics.DataProtectionLocal.UnprotectData(Byte[] data, Int32 dwFlags, Boolean transitoryData)
at Microsoft.ReportingServices.Diagnostics.DataProtectionLocal.LocalUnprotectData(String data, Boolean transitoryData)
at Microsoft.ReportingServices.Diagnostics.RSConfiguration.DecryptCatalogData(String encryptedData, String element)
--- End of inner exception stack trace ---Hi Vivek,
In Reporting Services, values for LogonUser, LogonDomain, and LogonCred are created when the report server connection is configured to use a domain account. As to the error that “The encrypted value for the "LogonCred" configuration setting cannot be decrypted”,
we can know that it relates to the domain account for report server connection.
To fix this issue, we can refer to the following steps:
Log in to SQL Server Database Engine in SQL Server Management Studio.
Under Security folder, give sufficient permissions for your domain account.
Open your Reporting Services Configuration (go to Start -> All Programs -> Microsoft SQL Server 2005 -> Configuration Tools -> Reporting Services Configuration)
Navigate to the Database Setup tab, select ‘Service Credentials’ as the Credentials Type, then type your domain account and password in there. Press Apply.
Restart the Report Server services.
Reference:
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/2d05b404-83aa-4fb2-bba6-52b587e890ec/sql-2005-rs-configuration-tool-encryption-key-error
Hope this helps.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support -
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] -
SQL Server 2005 Management Studio Local Server Connection Error
Sir, as you can see in above image,,, I have installed SQL SERVER 2005 Management Studio Express of 64 bit.
And when i have tried to connect it to local server it shows me above error...... Please guide me how should i fix it?Check
http://sqlserver-help.com/2011/06/19/help-whats-my-sql-server-name/
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle
Maybe you are looking for
-
When attempting a reinstall of iTunes, I cant delete the file C\Program Files\Common Files\Apple\Internet Services\Shellstream.resources due to same error message as described above for iPod file; however i can't find it anywhere in the Task Manager
-
Can't make genius bar appointment
can't make genius bar appointment
-
Have to send mail CC and body with person details also?
Hi, I have requirement sending mail TO as wellas CC also. How can i send? TO:Project manager, CC:TeamLeader. In the body, Contact Person, Phone No: These details i have to send. Tell me the procedure to do in workflow? Early reply is highely appricia
-
Object-XML Binding: How do I map from java to enumerated xml tags
Hi. I'm new to Object-XML binding and toplink. XML that I'm trying to model in a schema has enumerated elements, e.g. </module_0></module_1><module_n> instead of many </module> elements. To simplify the schema I've opted to use </module> anyway with
-
5.1 output from Soundtrack Pro?
I have FCP Studio 2, and would like to get into 5.1 mixing in Soundtrack Pro. I know you need some sort of intermediary device to output through, but if anyone could give me some specifics that'd be great. I've seen "M-Audio 410 interface" pop up in