Whenever an slowness issue came in sql server how should I start?
whenever a slowness issue or performance issue came in sql server how should I start?
Please guide.
Thanks
Hi Ajay,
All answer given above would be useful to you in some or the other scenario. if you are facing performance issue the approach you take determines how easily and quickly you can find solution.
First thing is know your system how it works for that you need to first baseline a system. A system with 70 % CPU utilization would not always be issue but for some environment it can be. If you know your system very well moment performance issue comes
you would know where is the problem. Wait stats alone is never helpful you must be able to correlate wait stats to what is going on your system. If you know which query is causing issue its easy to see execution plan and tune it. If issue is server wide it
can be due to missing index outdated stats slow disk subsystem etc. So first step is finding the cause. As Uri suggested wait stats are always helpful I use wait stats and refer to below whitepaper by Microsoft for SQL Server troubleshooting
http://technet.microsoft.com/en-us/library/dd672789%28v=sql.100%29.aspx
Remember important thing is knowing your system and that can come from base lining.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles
Similar Messages
-
SQL Server service not automatically starting (logon failure)
I just installed SQL Server 2012 on a machine. To run "SQL Server" as well as "SQL Server Agent" service I have created a domain account called SQLADMIN. This account is a service account and has no other rights like logon locally or
local administrator.
When the machine restarts, "SQL Server" service doesn't start automatically. When I click Start then it says "Logon Failure". Now if I simply enter the password again under tab "Log On" and then start service then it starts. Why
doesn't it start automatically?Hello,
Please read the following article about permissions required by service accounts.
http://msdn.microsoft.com/en-us/library/ms143504(v=sql.110).aspx#Serv_Perm
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
I do not see any special permission that is needed as per the article. For e.g. as per below:
SQL Server Service
Permissions granted by SQL Server Setup
SQL Server Database Engine:
(All rights are granted to the per-service SID. Default instance: NT SERVICE\MSSQLSERVER. Named instance: NT SERVICE\MSSQL$InstanceName.)
Log on as a service (SeServiceLogonRight)
Replace a process-level token(SeAssignPrimaryTokenPrivilege)
Bypass traverse checking (SeChangeNotifyPrivilege)
Adjust memory quotas for a process(SeIncreaseQuotaPrivilege)
Permission to start SQL Writer
Permission to read the Event Log service
Permission to read the Remote Procedure Call service
I am running Database Engine service as DOMAIN\SQLADMIN account which can Log On As A Service. Other 3 permissions mentioned in article are not given so let me assign it and then see how it goes.
Could this issue be due to some domain policy? Because there is another SQL Server machine which shows same behaviour. -
Hi Expert,
I have a problem when using SQL Server 2005.
I also use Windows Server 2008
My SQL Server Agent can't start.
When I try to start, I have message "The SQL Server Agent (MSSQLSERVER) service on Local Computer started and then stopped (object explorer).
Why does this problem happen?
Thanks
Regards,
Vicky Oktavianus> 2010-08-16 15:28:21 - ! [241] Startup error: Unable to initialize error reporting system (reason: The EventLog service has not been started)
> 2010-08-16 15:28:21 - ? [098] SQLServerAgent terminated (normally)
You seem to have an issue with your machine, I suggest you check further up in the event log for problems concerning the event log.
Uploading files here is not possible, open an OSS call (component BC-DB-MSS) and ask the support for help, there you can upload the file.
Markus -
What SQL server version should be installed in BW 3.5?
Dear all,
What SQL server version should be installed in BW 3.5?
1.Does it must install with enterprice version? Or can it use standand version?
2.SQL 2000 is ok? or must use SQL 2005?
3.x32 is ok? or must use x64?
Best regards!
Brian
Edited by: brian allen on Jun 24, 2009 9:22 AM> What SQL server version should be installed in BW 3.5?
>
> 1.Does it must install with enterprice version? Or can it use standand version?
Read the installation guide - Enterprise version only.
> 2.SQL 2000 is ok? or must use SQL 2005?
Both work but I would go for SQL 2005 (or even SQL 2008).
> 3.x32 is ok? or must use x64?
You should use 64bit wherever possible on new installations.
Makrus -
Issue with applying SQL Server 2014 CU6
Anyone had an issue like this when applying CU6... I have a single server/single instance 2014 installation running SQL SRVR, SSAS, SSRS, SSIS...
SSAS, SSRS, and SSIS all upgraded to 12.0.2480.0, but SQL Server did not. The summary file has the generic failure message below:
Instance MSSQLSERVER overall summary:
Final result: The patch installer has failed to update the shared features. To determine the reason for failure, review the log files.
Exit code (Decimal): -2061893565
Start time: 2015-03-13 10:56:18
End time: 2015-03-13 10:59:59
Requested action: Patch
After reboot everything came up fine, but now I am left wondering how to troubleshoot this. The detail log is huge and doesn't show a clear indication of what the issue might be. Anyone have any guidance on troubleshooting? I have searched
the web and found some results for earlier versions... but nothing terribly helpful.To close this out, I'd like to note that I finally was able to get to a meaningful error message:
"The User Data directory in the registry is not valid. Verify DefaultData key under the instance hive points to a valid directory. Error code: 0x851A0043"
The error resulted from an earlier relocation of the default data location. A registry entry for DefaultData in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQLServer was incorrectly pointing to an obsolete drive
letter. Correcting the drive letter was all that was needed. I am now successfully at version 12.0.2480.0. -
Having issues with getting SQL Server Express to start services and run.
Good afternoon everyone,
I have been working on a 2012 R2 server getting ready to move databases to new hardware. I had SQL Server Express 2008 R2 running on this server with no issues. I was handed another software package that ran SQL Express 2012 and had to for compatibility
reasons. I have had multiple versions run on Server 2012 before with no issues. This time, not so lucky. When the installer from the updated package put on SQL Express 2012 it completed with errors ( error log posted at the end of post) and
would not allow me to run software. I then tried the db that I had installed on 2008 R2 and it also gave the same error as the 2012 version. IN basic terms the required services attempted to start and shut back down again. I have received
Error 1068 about database handles and error %%945. I know this db has plenty of space and the permissions were added for the Admin account to access both db's. I then uninstalled both versions and tried again, with the same errors listed when
I tried to start the services. I am thinking that a clean install would fix the issue however I am not certain what files/folders/reg entries need to be deleted or modified. I have researched all the errors I can find, however I am very
new with SQL anything so I know I am missing something. I also do not have an "E:" drive on this server (not sure why it is going there). Input would be very welcome as I am not certain where to go from here.
Thanks,
Matt
Error Log follows, server and domain names have been blacked out with ****.
2015-04-15 11:57:55.16 Server Microsoft SQL Server 2012 (SP1) - 11.0.3128.0 (X64)
Dec 28 2012 20:23:12
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor)
2015-04-15 11:57:55.16 Server (c) Microsoft Corporation.
2015-04-15 11:57:55.16 Server All rights reserved.
2015-04-15 11:57:55.16 Server Server process ID is 4104.
2015-04-15 11:57:55.16 Server System Manufacturer: 'HP', System Model: 'ProLiant ML350p Gen8'.
2015-04-15 11:57:55.16 Server Authentication mode is WINDOWS-ONLY.
2015-04-15 11:57:55.16 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG'.
2015-04-15 11:57:55.17 Server The service account is 'NT AUTHORITY\LOCAL SERVICE'. This is an informational message; no user action is required.
2015-04-15 11:57:55.17 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\mastlog.ldf
2015-04-15 11:57:55.17 Server Command Line Startup Parameters:
-s "SQLEXPRESS"
2015-04-15 11:57:55.48 Server SQL Server detected 1 sockets with 6 cores per socket and 12 logical processors per socket, 12 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message;
no user action is required.
2015-04-15 11:57:55.48 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2015-04-15 11:57:55.48 Server Detected 8157 MB of RAM. This is an informational message; no user action is required.
2015-04-15 11:57:55.48 Server Using conventional memory in the memory manager.
2015-04-15 11:57:55.68 Server This instance of SQL Server last reported using a process ID of 7840 at 4/15/2015 11:57:47 AM (local) 4/15/2015 3:57:47 PM (UTC). This is an informational message only; no user action is required.
2015-04-15 11:57:55.68 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2015-04-15 11:57:55.69 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2015-04-15 11:57:55.72 Server Software Usage Metrics is disabled.
2015-04-15 11:57:55.73 spid5s Starting up database 'master'.
2015-04-15 11:57:55.79 spid5s 20 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2015-04-15 11:57:55.79 spid5s 0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2015-04-15 11:57:55.80 Server CLR version v4.0.30319 loaded.
2015-04-15 11:57:55.86 spid5s Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
2015-04-15 11:57:55.89 Server Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2015-04-15 11:57:55.91 spid5s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2015-04-15 11:57:55.91 spid5s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2015-04-15 11:57:55.94 spid5s SQL Trace ID 1 was started by login "sa".
2015-04-15 11:57:55.94 spid5s Server name is '********\SQLEXPRESS'. This is an informational message only. No user action is required.
2015-04-15 11:57:55.96 spid5s Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Binn\ftimport.dll'.
2015-04-15 11:57:55.96 spid5s Starting up database 'msdb'.
2015-04-15 11:57:55.96 spid9s Starting up database 'mssqlsystemresource'.
2015-04-15 11:57:55.96 spid5s Error: 17204, Severity: 16, State: 1.
2015-04-15 11:57:55.96 spid5s FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2015-04-15 11:57:55.96 spid5s Error: 5120, Severity: 16, State: 101.
2015-04-15 11:57:55.96 spid5s Unable to open the physical file "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
2015-04-15 11:57:55.96 spid5s Error: 17207, Severity: 16, State: 1.
2015-04-15 11:57:55.96 spid5s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf'.
Diagnose and correct the operating system error, and retry the operation.
2015-04-15 11:57:55.96 spid5s File activation failure. The physical file name "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf" may be incorrect.
2015-04-15 11:57:55.99 spid9s The resource database build version is 11.00.3000. This is an informational message only. No user action is required.
2015-04-15 11:57:56.02 spid12s A self-generated certificate was successfully loaded for encryption.
2015-04-15 11:57:56.03 spid12s Server is listening on [ 'any' <ipv6> 53345].
2015-04-15 11:57:56.03 spid12s Server is listening on [ 'any' <ipv4> 53345].
2015-04-15 11:57:56.03 spid12s Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQLEXPRESS ].
2015-04-15 11:57:56.03 spid12s Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$SQLEXPRESS\sql\query ].
2015-04-15 11:57:56.04 spid12s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806.
This is an informational message only. No user action is required.
2015-04-15 11:57:56.04 Server SQL Server is attempting to register a Service Principal Name (SPN) for the SQL Server service. Kerberos authentication will not be possible until a SPN is registered for the SQL Server service. This is an informational
message. No user action is required.
2015-04-15 11:57:56.04 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/********.****.local:SQLEXPRESS ] for the SQL Server service. Windows return code: 0xffffffff, state: 53.
Failure to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been
manually registered.
2015-04-15 11:57:56.04 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) [ MSSQLSvc/********.****.local:53345 ] for the SQL Server service. Windows return code: 0xffffffff, state: 53. Failure
to register a SPN might cause integrated authentication to use NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies and if the SPN has not been manually
registered.
2015-04-15 11:57:56.09 spid9s Starting up database 'model'.
2015-04-15 11:57:56.10 spid9s Error: 17204, Severity: 16, State: 1.
2015-04-15 11:57:56.10 spid9s FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2015-04-15 11:57:56.10 spid9s Error: 5120, Severity: 16, State: 101.
2015-04-15 11:57:56.10 spid9s Unable to open the physical file "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
2015-04-15 11:57:56.10 spid9s Error: 17207, Severity: 16, State: 1.
2015-04-15 11:57:56.10 spid9s FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\modellog.ldf'.
Diagnose and correct the operating system error, and retry the operation.
2015-04-15 11:57:56.10 spid9s File activation failure. The physical file name "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incorrect.
2015-04-15 11:57:56.10 spid9s Error: 945, Severity: 14, State: 2.
2015-04-15 11:57:56.10 spid9s Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2015-04-15 11:57:56.10 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
Hi HMLunger,
Did you install the SQL Server instance successfully? If not, please help to post the summary and detail logs for analysis. By default, the logs can be found in: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log.
However, if you fail to start SQL Server Express service after successfully installing SQL Server,
you might have to change the paths of the files by running the following scripts from the command prompt. For more details, please review this similar
thread.
NET START MSSQL$SQLEXPRESS /f /T3608
SQLCMD -S .\SQLEXPRESS
ALTER DATABASE model MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
ALTER DATABASE model MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
go
exit;
ALTER DATABASE msdb MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
ALTER DATABASE msdb MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
NET STOP MSSQL$SQLEXPRESS
In addition, you can follow the steps in this KB article to uninstall SQL Server.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support -
Good morning,
I'm experiencing the following issue when installing Microsoft SQL Server Express 2012 (with tools, SQLEXPRWT_x86_ENU.exe) on the laptop of my company;
Installation goes plain until around the end of the progress bar, it stops on the setup of
SqlEngineDBStartConfigAction_install_configrc_Cpu32
giving 7-8 times, even pressing "Cancel", the message "The requested control is not valid for this service";
After this, I receive one last message ""Could not find the database engine startup handle", then installation ends with failures, in particular the Database Engine and the Server Replication failed to be installed.
I've put in my SkyDrive the error log I received after the install;
I'm at full disposal if you need further information,
thank you in advance
Best regards
FrancescoWell, i just ran into this issue and the problem was lack of admin rights. It was my company's laptop so got the setup initiated by my company's IT team with admin rights. However, the upon completion of setup, i go the same error messages as stated above:
SqlEngineDBStartConfigAction_install_configrc_Cpu32
giving 7-8 times, even pressing "Cancel", the message "The requested control is not valid for this service";
After this, I receive one last message ""Could not find the database engine startup handle", then installation ends with failures, in particular the Database Engine and the Server Replication failed to be installed.
Also, if you open SQL Server Configuration, the status of the service is "Change Pending" and you would not be able to set the startup login type to Local Service/System/Network.
Then, I just got my account added as Local Admin and then tried to start the service and was able to.
However, I am not sure whether same was the case for you.
Please mark the answer as helpful if i have answered your query. Thanks and Regards, Kartar Rana -
PI 7.0 - jdbc receiver issue with MS SQL Server
Hello Experts,
I have a jdbc receiver scenario on PI 7.0 for just one table on MS SQL Server and I'm using the update_insert action.
When the entry does not exist it is created normally and returns insert_count=1 and update_count=0.
When the entry already exists, it's generated the statements for insert and for update (the 2 statements are visible on RWB) and returns insert_count=0 and update_count=0.
Any error occurs and in the RWB the log shows the request was processed with success.
I've already enabled the log for sql statements on the channel, but the statements are correct.
I've reviewed also the <key> tag on the mapping and it's ok.
Any suggestion to try fix this issue?
Thank you very much.Can you please check in the database the format of the specified fields in the update statement. Sometime we can have situations that the insert works but the subsequent update fails. An example:
Suppose key field1 value being passed from XI is '1234' in characters but in db it is stored as '00001234'.
Regards,
Indranil -
Visual Studio very slow to connect to SQL Server
Hi all,
I'm running a Windows 8.1 laptop, and have Visual Studio Ultimate 2013 as well as SQL Server Management Studio 2014 and SQL Server Express 2014. I also have a Windows Azure
SQL Server 2014 database server.
I set up all of this while living in North America - Quebec to be exact. While working from there, I had no trouble connecting to my database server, through Visual Studio or through SSMS.
I'm now living in France, and am having an extremely hard time accessing my databases. While connecting through Visual Studio, it takes 10-20 minutes of waiting before the connection is established with the server. This is true for both the Windows Azure database
server AND the SQL Server Express edition installed on the same laptop!
It makes absolutely no sense - how could it take so long to connect to a server installed on the *same* machine as the applications? What's even more strange, once the connection is established, all other actions happen instantly. There is no delay in communicating
with the server once the connection is set up - it seems like the problem is specifically with connecting to the server.
I've tried using the IP Address instead of localhost, I've also tried using the instance name of the SQL Server Express instead of localhost. Neither have solved the problem.
Can anyone help me with finding out why this is happening? Thanks!Hi all,
I'm running a Windows 8.1 laptop, and have Visual Studio Ultimate 2013 as well as SQL Server Management Studio 2014 and SQL Server Express 2014. I also have a Windows Azure
SQL Server 2014 database server.
I set up all of this while living in North America - Quebec to be exact. While working from there, I had no trouble connecting to my database server, through Visual Studio or through SSMS.
I'm now living in France, and am having an extremely hard time accessing my databases. While connecting through Visual Studio, it takes 10-20 minutes of waiting before the connection is established with the server. This is true for both the Windows Azure database
server AND the SQL Server Express edition installed on the same laptop!
It makes absolutely no sense - how could it take so long to connect to a server installed on the *same* machine as the applications? What's even more strange, once the connection is established, all other actions happen instantly. There is no delay in communicating
with the server once the connection is set up - it seems like the problem is specifically with connecting to the server.
I've tried using the IP Address instead of localhost, I've also tried using the instance name of the SQL Server Express instead of localhost. Neither have solved the problem.
Can anyone help me with finding out why this is happening? Thanks!
Hello,
Since this issue is not related to Visual Studio debugger tools, I will help you move this thread to Visual Studio General forum to get help about using Visual Studio.
Regards,
Carl
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
Issues using Oracle SQL server Developer migration work bench
Hi all,
We are trying to migrate the application databases from SQL server 2000 to Oracle 10g using Oracle SQL Developer 1.2.1.32.13:
Following is the list of issues that we faced while trying out this migration on dev environment.
1. The data migration was successful for only around 90 tables out of the total 166 tables present. No error message was logged for the rest of the tables but still it was completed.
2. Some of the tables which had got the data inserted did not have the full data. Only some of the rows were inserted for these tables. Error message was logged only for few of the rows and not all.
3. Few error messages were logged which said problems about “Inserting ' ' into column <tablename>.<columnname>”. There was no such constraint in the target database that the particular column can not be null or can not have only a space. Please check the logs for the same error messages.
4. The status box at the end of migration had shown only 3 errors.
5. The total data for migration was around 500MB. The time taken for migration was around 75 minutes. Are there any optimization techniques that will improve the performance?
Please note that there were no Foreign Key references for the source schema or target schema.
Any pointers/info/resolutions related to above mentioned issues will be much useful for us.
Thanks,Hi Adam,
There are 2 sets of scripts created for you.
1) For SQL Servers BCP to dump out the data to dat files
2) For Oracles SQL*Loader to load the dat files
You run the SQL Server BCP scripts on the machine with SQL Server.
The dat files will be dumped out on that server.
You can then move the dat files to your Oracle server.
Then run the Oracle SQL*Loader scripts to load the dat files into Oracle.
Give it a go and follow the doc and viewlets.
Your Questions:
So the datadump from the source location would be saved on my local disk?it will be saved on the same machine you run the bcp scripts from. Usually the same machine SQL Server is on, because you require SQL Server BCP tool.
So once it is migrated to the destination database will that dump be created automatically? Or do I need to modify the script to take care of this?I dont know what you mean by this, hopefully above clears things up.
The only modifications you need to make to the scripts are adding in the databasename username password servername. These are outlined in the scripts themselves. I would want to do something fancy like dump the dat files to a different directory, then you can modify the scripts, but you should understand what they do first.
Most people would have 500MB of space on their discs , so I can see the problem creating these dat files . The same goes for your 30 GB database.
I hope this helps, but as always you wont get a good idea of how it works until you give it a go.
Regards,
Dermot. -
Firewall issue with centralized SQL server - port 52384
Hi,
I have dedicated, centralized MS SQL 2012 server for our internal infrastructure with few instances. There is dedicated named instance SC for SC Family Products running on TCP port 1435. Also Server Browser running on UDP 1434 is enabled. I'm trying to install
SCOM 2012 R2. I got to the step Configure the Operational Database and here, I encountered a problem. I try to connect to my SQL server and put into
Server name and instance name SQL\SC and into SQL Server port 1434 or 1435, it doesn't connect. If I turn off firewall on SQL server, it connects without problems. On SQL server, I already have allowed incoming communication on ports UDP 1434
and also TCP 1433-1436. Than, I found out, that I need to allow in TCP 135 so I did it. It didn't work. Than I allowed TCP 49154-49157 for reporting services - it still didn't work. Last thing I allowed (using Microsoft Network Monitor) was TCP port 52384
and suddenly, it worked .
I know what UDP 1434 and TCP 1433-1436 are for. Also, I understand why I have to open 135 and 49154-49157. But I am pretty confused by the port 52384 - what is it for ? Why it isn't mentioned in documentation ? I am pounding with this problem for a while,
and also, I found out, that my SC VMM is not working, if I do not allow all of these ports - so, probably not only used by SCOM ?
Can anyone explain what's that port for ? Or why it's not enough to open 1434, 1433-1436, 135 and 49154-49157 ?
Thanks
TomasHi,
I didn't install SCOM yet. I am stuck at installation, till I figure out why port 52384 needs to be opened.
1. My SQL Server Configuration Manager is set like this:
Protocols for SC - TCP/IP Enabled
IP2
Active : Yes
Enabled : Yes
IP Address : ipv4 ip address of server
TCP Dynamic Ports : (blank)
TCP Port : 1435
So, that should be ok, right?
2. If I turn off firewall on SQL, everything connects ok - so based on that, I suppose that SCOM server firewall is configured ok . It's issue on SQL.
On SQL server, I have these inbound rules:
COM+ Network Access (DCOM-In) - TCP 135 enabled
HTTP/HTTPS - TCP 80,443 enabled
SCOM Reporting - TCP 49154-49157 enabled
SQL UDP ports - UDP 1433-1437 enabled
SQL TCP ports - TCP 1433-1435 enabled
SCOM 52384 - TCP 52384 enabled <- this is the port I don't understand, why it should be opened
If I disable any of these rules, my connection will not pass. I figured out those ports using Microsoft Network Monitor on SQL server.
3. Those databases do not exist yet. I am stuck at 3th step of Operations Manager Setup - at Configure the operational database.
There are fields Server name and instance name, SQL Server port, Database name, Database size, Data file folder, Log file folder
. First two are writable and the rest is greyed out. If I don't turn off firewall and I don't enable all rules from point 2 on SQL server and than put in the SQL server name with instance (SQL\SC) and port 1434 (or 1435) it gives
me red cross, and rest of the page stays greyed out - so, it's unable to connect. If I turn off firewall, or enable all the rules in previous point (2) I am able to change name of the database, database size, data/log file folder. But if I disable any
of those ports, it stays greyed out - I am concerned about port 52384, why it should be opened? What is it for? Why it isn't mentioned in any documentation? Or am I doing something wrong?
Thanks
Tomas -
Issue with Microsoft SQL Server, according to SAP (LMB)
We are upgrading our SAP Solution Manager and ran into a problem. SAP has passed it on to Microsoft because it appears to be an issue with our MS SQL data base. So we get a question back from Microsoft that says - -
First, you are running SAPJVM1.4 and for a 1.4 environment the 1.2
version of the Microsoft SQL Server driver must be used.
So how can I find the version number for our Microsoft SQL Server driver ?? Thanks, Jim WellsThat is a difficult topic. Some articles:
http://blogs.msdn.com/b/sqlcat/archive/2010/10/26/how-to-tell-which-version-of-sql-server-data-access-driver-is-used-by-an-application-client.aspx
http://technet.microsoft.com/en-us/library/ms181099.aspx
http://www.mssqltips.com/sqlservertip/2198/determine-which-version-of-sql-server-data-access-driver-is-used-by-an-application/
Kalman Toth Database & OLAP Architect
IPAD SELECT Query Video Tutorial 3.5 Hours
New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012 -
Issue in Migrating Sql Server Database 2012 to Sql Azure
Hi All
I am facing following issue while Deployed MS SQL Server 2012 Database to SQL Azure.
TITLE: Microsoft SQL Server Management Studio
One or more unsupported elements were found in the schema used as part of a data package.
Error SQL71564: The element Extended Property: [dbo].[Accounts_Login].[MS_SSMA_SOURCE] is not supported when used as part of a data package (bacpac).
Error SQL71564: The element Extended Property: [dbo].[Company_Master].[MS_SSMA_SOURCE] is not supported when used as part of a data package (bacpac).
Error SQL71564: The element Extended Property: [dbo].[Message_Master].[MS_SSMA_SOURCE] is not supported when used as part of a data package (bacpac).
Error SQL71564: The element Extended Property: [dbo].[Requests_Master].[MS_SSMA_SOURCE] is not supported when used as part of a data package (bacpac).
Error SQL71564: The element Extended Property: [dbo].[Twitter_Master].[MS_SSMA_SOURCE] is not supported when used as part of a data package (bacpac).
Error SQL71564: The element Extended Property: [dbo].[Users_Master].[MS_SSMA_SOURCE] is not supported when used as part of a data package (bacpac).
(Microsoft.SqlServer.Dac)
Error SQL71564: The element Extended Property: xxx is not supported when used as part of a data package (bacpac).
Thanks & Regards Ravi ShankarHello,
Extended Properties are not supported in SQL Azure.
To work around this issue, you can use Generate Scripts Wizard to generate script which are compatible with SQL Database and can be compiled on SQL Database without any further modifications. For example, in Choose Script Options, click on the Advanced button
and, set Script Extended Properties = False.
Reference:http://social.technet.microsoft.com/wiki/contents/articles/994.develop-and-deploy-with-windows-azure-sql-database.aspx
Regards,
Fanny Liu
Fanny Liu
TechNet Community Support -
Issues in Connecting SQL Server 2008 to BI om Solaris
Hi ,
I am trying to Connect a Standalone SQL Server to a BI System on UNIX Via UD Connect . Both SQL Server and BI System are on the Same Network ( Subnet ) .
I have Deployed the JDBC Drivers in BI Via Visual Administrator
PATH :- Server --> Services --> JDBC Connector
Then , in VIsual Admin in CONNECTOR COntainer , I copied the SDK_JDBC and Created another Connector SDK_JDBC1 which Connects to SQL Server
In the Properties I have Maintained the Following Parameters :-
DriverName :- com.microsoft.jdbc.sqlserver.SQLServerDriver
URL :- jdbc:microsoft:sqlserver://<SQLServer_HOST>:1433;DatabaseName=<SID>
User :- Username which Authenticates to SQL Server and NOT WINDOWS
Password :- Password Of the User
I have not BOUNCED the JAVA Stack .
Now , when I test the Connection via URL http://<FQDN>/TestJDBC_Web/TestJDBCPage.jsp
and I Select SDK_JDBC1 , I get the Following Errors .
I am giving extract of Error of BI_SDK_Trace.log and DefaultTrace Log
Trace of BI_SDK_Trace.log :- #1.#0003BAE27F27001F0000007500006DD100049C78328E98DE#1297939965056#com.sap.ip.bi.sdk.dac.connector.relational.CommonConnection#sap.com/com.sap.ip.bi.sdk.dac.connector.checkj#com.sap.ip.bi.sdk.dac.connector.relational.CommonConnection#Guest#0##n/a##0d131de63a8411e097c90003bae27f27#SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#/Applications/BI/UDI#Plain###Class Not Found: com.microsoft.jdbc.sqlserver.SQLServerDriver#
#1.#0003BAE27F27001F0000007900006DD100049C78328FE6CC#1297939965133#com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcManagedConnection#sap.com/com.sap.ip.bi.sdk.dac.connector.checkj#com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcManagedConnection#Guest#0##n/a##0d131de63a8411e097c90003bae27f27#SAPEngine_Application_Thread[impl:3]_29##0#0#Error#1#/Applications/BI/UDI#Java###com.sap.ip.bi.sdk.exception.BIResourceException: Class DriverName is not found
[EXCEPTION]
#1#com.sap.ip.bi.sdk.exception.BIResourceException: Class DriverName is not found at com.sap.ip.bi.sdk.dac.connector.jdbc.impl.Connection.connectDB(Connection.java:314)
at com.sap.ip.bi.sdk.dac.connector.jdbc.impl.Connection.connect(Connection.java:99)
at com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcManagedConnection.<init>(JdbcManagedConnection.java:118)
at com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcManagedConnectionFactory.createManagedConnection(JdbcManagedConnectionFactory.java:112)
at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:338)
at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:262)
at com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcConnectionFactory.getConnectionEx(JdbcConnectionFactory.java:233)
at com.sap.ip.bi.sdk.trialarea.connector.servlet.model.JDBCModel.getConnection(JDBCModel.java:796)
at com.sap.ip.bi.sdk.trialarea.connector.servlet.model.JDBCModel.getTables(JDBCModel.java:132)
at com.sap.ip.bi.sdk.trialarea.connector.servlet.controller.Control2.doPost(Control2.java:25)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Caused by: java.lang.ClassNotFoundException: com.microsoft.jdbc.sqlserver.SQLServerDriverFound 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:signature_lib;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
library:tcconnconnectorframework
library:com.sap.ip.bi.sdk.dac.connector.odbodll
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
sap.com/caf~core
sap.com/cafruntimeear
library:bimmrcwm_1.0_library
library:bimmrjmi
library:com.sap.ip.bi.sdk
library:MSS_DRIVER
library:SYSTEM_DRIVER
library:ORA_DRIVER
Resources:
/usr/sap/TP1/JC00/j2ee/cluster/server0/apps/sap.com/cafbwadapterassembly/connector/connectors/cafbwadapterassembly.rar/sap.comcafbwadaptercaf.bw.adapter.jar
/usr/sap/TP1/JC00/j2ee/cluster/server0/apps/sap.com/com.sap.ip.bi.sdk.dac.connector.xmla/connector/connectors/bi_sdk_xmla.rar/bi_sdk_xmla.jar
/usr/sap/TP1/JC00/j2ee/cluster/server0/apps/sap.com/com.sap.ip.bi.sdk.dac.connector.sapq/connector/connectors/bi_sdk_sapq.rar/bi_sdk_sapq.jar
/usr/sap/TP1/JC00/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:309)
... 25 more
Trace of Defaultlog
#1.#0003BAE27F27001F0000007800006DD100049C78328FDED9#1297939965140#System.err#sap.com/com.sap.ip.bi.sdk.dac.connector.checkj#System.err#Guest#0##n/a##0d131de63a8411e097c90003bae27f27#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain###Feb 17, 2011 4:22:45 PM ....connector.jdbc.JdbcManagedConnection [SAPEngine_Application_Thread[impl:3]_29] Error: com.sap.ip.bi.sdk.exception.BIResourceException: Class DriverName is not found
[EXCEPTION]
com.sap.ip.bi.sdk.exception.BIResourceException: Class DriverName is not found at com.sap.ip.bi.sdk.dac.connector.jdbc.impl.Connection.connectDB(Connection.java:314)
at com.sap.ip.bi.sdk.dac.connector.jdbc.impl.Connection.connect(Connection.java:99)
at com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcManagedConnection.<init>(JdbcManagedConnection.java:118)
at com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcManagedConnectionFactory.createManagedConnection(JdbcManagedConnectionFactory.java:112)
at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:338)
at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:262)
at com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcConnectionFactory.getConnectionEx(JdbcConnectionFactory.java:233)
at com.sap.ip.bi.sdk.trialarea.connector.servlet.model.JDBCModel.getConnection(JDBCModel.java:796)
at com.sap.ip.bi.sdk.trialarea.connector.servlet.model.JDBCModel.getTables(JDBCModel.java:132)
at com.sap.ip.bi.sdk.trialarea.connector.servlet.controller.Control2.doPost(Control2.java:25)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
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:signature_lib;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
library:tcconnconnectorframework
library:com.sap.ip.bi.sdk.dac.connector.odbodll
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
sap.com/caf~core
sap.com/cafruntimeear
library:bimmrcwm_1.0_library
library:bimmrjmi
library:com.sap.ip.bi.sdk
library:MSS_DRIVER
library:SYSTEM_DRIVER
library:ORA_DRIVER
Resources:
/usr/sap/TP1/JC00/j2ee/cluster/server0/apps/sap.com/cafbwadapterassembly/connector/connectors/cafbwadapterassembly.rar/sap.comcafbwadaptercaf.bw.adapter.jar
/usr/sap/TP1/JC00/j2ee/cluster/server0/apps/sap.com/com.sap.ip.bi.sdk.dac.connector.xmla/connector/connectors/bi_sdk_xmla.rar/bi_sdk_xmla.jar
/usr/sap/TP1/JC00/j2ee/cluster/server0/apps/sap.com/com.sap.ip.bi.sdk.dac.connector.sapq/connector/connectors/bi_sdk_sapq.rar/bi_sdk_sapq.jar
/usr/sap/TP1/JC00/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:309)
... 25 more
Regards,
Ashish .A. PoojaryAbove was the BI_SDK_Trace.log , Now I am Attching the DEFAULT TARCE LOG
#1.#0003BAE27F27002E0000009400006DD100049C77692A35B4#1297936586257#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#sap.com/com.sap.ip.bi.sdk.dac.connector.checkj#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#Guest#0##n/a##2f2451773a7c11e08cfe0003bae27f27#SAPEngine_Application_Thread[impl:3]_34##0#0#Error#1#/System/Server/WebRequests#Plain###application [TestJDBC_Web] Processing HTTP request to servlet [Control 1] finished with error.
The error is: java.lang.NoClassDefFoundError: null
Exception id: [0003BAE27F27002E0000009200006DD100049C77692A2CE6]#
#1.#0003BAE27F27001F0000007400006DD100049C78328E976D#1297939965056#System.err#sap.com/com.sap.ip.bi.sdk.dac.connector.checkj#System.err#Guest#0##n/a##0d131de63a8411e097c90003bae27f27#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain###Feb 17, 2011 4:22:45 PM ...connector.relational.CommonConnection [SAPEngine_Application_Thread[impl:3]_29] Error: Class Not Found: com.microsoft.jdbc.sqlserver.SQLServerDriver
#1.#0003BAE27F27001F0000007800006DD100049C78328FDED9#1297939965140#System.err#sap.com/com.sap.ip.bi.sdk.dac.connector.checkj#System.err#Guest#0##n/a##0d131de63a8411e097c90003bae27f27#SAPEngine_Application_Thread[impl:3]_29##0#0#Error##Plain###Feb 17, 2011 4:22:45 PM ....connector.jdbc.JdbcManagedConnection [SAPEngine_Application_Thread[impl:3]_29] Error: com.sap.ip.bi.sdk.exception.BIResourceException: Class DriverName is not found
[EXCEPTION]
com.sap.ip.bi.sdk.exception.BIResourceException: Class DriverName is not found
at com.sap.ip.bi.sdk.dac.connector.jdbc.impl.Connection.connectDB(Connection.java:314)
at com.sap.ip.bi.sdk.dac.connector.jdbc.impl.Connection.connect(Connection.java:99)
at com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcManagedConnection.<init>(JdbcManagedConnection.java:118)
at com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcManagedConnectionFactory.createManagedConnection(JdbcManagedConnectionFactory.java:112)
at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:338)
at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:262)
at com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcConnectionFactory.getConnectionEx(JdbcConnectionFactory.java:233)
at com.sap.ip.bi.sdk.trialarea.connector.servlet.model.JDBCModel.getConnection(JDBCModel.java:796)
at com.sap.ip.bi.sdk.trialarea.connector.servlet.model.JDBCModel.getTables(JDBCModel.java:132)
at com.sap.ip.bi.sdk.trialarea.connector.servlet.controller.Control2.doPost(Control2.java:25)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
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:tc~sec~ssl
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:signature_lib;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:bi~mmr~core;library:bi~mmr~db
library:tc~conn~connectorframework
library:com.sap.ip.bi.sdk.dac.connector.odbodll
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
sap.com/caf~core
sap.com/caf~runtime~ear
library:bi~mmr~cwm_1.0_library
library:bi~mmr~jmi
library:com.sap.ip.bi.sdk
library:MSS_DRIVER
library:SYSTEM_DRIVER
library:ORA_DRIVER
Resources:
/usr/sap/TP1/JC00/j2ee/cluster/server0/apps/sap.com/caf~bw~adapter~assembly/connector/connectors/caf~bw~adapter~assembly.rar/sap.com~caf~bw~adapter~caf.bw.adapter.jar
/usr/sap/TP1/JC00/j2ee/cluster/server0/apps/sap.com/com.sap.ip.bi.sdk.dac.connector.xmla/connector/connectors/bi_sdk_xmla.rar/bi_sdk_xmla.jar
/usr/sap/TP1/JC00/j2ee/cluster/server0/apps/sap.com/com.sap.ip.bi.sdk.dac.connector.sapq/connector/connectors/bi_sdk_sapq.rar/bi_sdk_sapq.jar
/usr/sap/TP1/JC00/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:309)
... 25 more -
Issues while readin SQL server via ODBC connection
Hi Experts,
I havea SQL server db as a source. I have configured the Datastore using ODBC connection. Developed a job which simply reads a table and populates into a flat file. when we run the job, it doesnt show any progress, it just stops after a log message "initializing data store, processing job" . I looked at the job logs file on the Job server, its incomplete as well.
One thing is that, im able to see the data when i go under data store and view data option for that particular table. My other jobs works just fine with oracle data base sources. We restarted the BODS server as well, but it doesnt help. Any idea on what might be going on ?.
Thanks for your time.
Regards,
NarayananHi Narayanan ,
There are two steps:
1) Set up the ODBC connection correctly on your Linux server
http://wiki.sdn.sap.com/wiki/display/EIM/ToconfigureDataDirectODBConLinuxand+Unix
(test with isql command line if connection on that server to the SQL Server is working)
2) Select ODBC connection in the datastore and then put the name of the connection you defined. (do not choose Database - SQL Server)
Norbert
Maybe you are looking for
-
Shutting down programmes and rebooting computer did not help. Launching web links from Live Mail has never been a problem before. Error message reads " There was a problem sending the command to the program"
-
The sign in box to buy a song keeps popping up even though i am typing in the right password
-
Hi. I need a driver for printer Hp scanjet N 6350.
I need a driver for installing to my iMac, i cany find officially driver Hp Scanjet N 6350. Please help me
-
How to Test Cliams Work Flow during run time in SWDD Tcode
Hi Gurus, I want to test my Claim Work Flow(WS99900044) in SWDD Tcode by Hard coding values to Work Flow Container Elements. How can I do this, kindly pls advice me.
-
Deploying on Weblogic 8.1 SP3 failed
Hi, I'm trying to deploy my application to weblogic 8.1 SP3 server, but I get the following error.. Servlet: "Faces Servlet" failed to preload on startup in Web application: "...". javax.servlet.ServletException at weblogic.servlet.internal.ServletSt