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
Tomas

Hi,
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 

Similar Messages

  • 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

  • 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

  • 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 Wells  

    That 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 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.

  • PeopleTools 8.49 PeopleSoft Database Cannot Connect with MS SQL Server 2005

    Folks,
    Hello. I am working on PeopleSoft PIA. My system is Windows Server 2003, MS SQL Server Express 2005 Standard, PeopleTools 8.49. I am setting up PeopleSoft Database \PsMpDbInstall\setup.exe and got the errors as follows:
    Error: Setup fails to connect to SQL Server. The default settings SQL Server does not allow remote connection.
    Then I type in "sqlcmd" in Command Prompt and got the same error as follows:
    Name Pipe Provider: Could not open a connection to SQL Server. MS SQL Native Client: the default settings SQL Server does not allow remote connection.
    In order to fix SQL Server 2005 remote connection problem, I have done the 3 steps as follows:
    Step 1: In SQL Server Surface Area Connection, enable local and remote connection, TCP/IP and Name Pipes, SQL Server browser Startup type "automatic" and status "running".
    Step 2: Create exception for SQL Server 2005 and SQL Server browser Service in Windows Firewall.
    Step 3: Add the default SQL Server Port 1433 into Windows Firewall.
    But the above 3 steps cannot resolve SQL Server Express 2005 remote connection problem. Can any folks help to resolve this problem ?
    Thanks.

    Folks,
    Management Studio can connect with SQL Server 2005 successfully.
    I have turned off Windows Server 2003 firewall completely. But "sqlcmd" in Command Prompt still connect with SQL Server 2005 because its remote connection is not allowed.
    Is the "not allow remote connection" problem caused by Windows Firewall or SQL Server 2005 itself ?
    Thanks.

  • How to sql server port number to scom inventory

    can some one help me how to add sql server port number to scom inventory 

    To open a port in the Windows firewall for TCP access
    On the
    Start menu, click Run, type WF.msc, and then click
    OK.
    In the
    Windows Firewall with Advanced Security, in the left pane, right-click
    Inbound Rules, and then click New Rule in the action pane (upper right corner).
    In the Rule Type dialog box, select
    Port, and then click Next.
    In the Protocol and Ports dialog box, select
    TCP. Select Specific local ports, and then type the port number of the instance of the Database Engine, In my case we are using the default which is
    1433. Click Next.
    In the Action dialog box, select
    Allow the connection, and then click Next.
    In the Profile dialog box, I am going to Leave
    Domain turned on and turn private and public off. Then click
    Next.
    In the Name dialog box, type "Allow SQL 1433 Inbound” and for a description I am putting in the same. Then click
    Finish.
    Also you can refer below link
    http://blogs.technet.com/b/danstolts/archive/2011/06/08/how-to-open-firewall-port-1433-for-sql-server-database-engine-for-use-with-scom-or-anything-else.aspx
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"

  • How to get JDev 10.1.2/ADF working with MS SQL Server Identity Column

    Hello JDevTeam & JDevelopers,
    I want to use JDev/ADF with a MS SQL Server 2005 database that contains tables employing IDENTITY Columns.
    Using JDev/ADF and DBSequence with an Oracle database employing before triggers/sequences accomplishes what I am trying to do except I want to accomplish the same thing using a MSSQL Server 2005 database. Unfortunately I cannot change the database.
    I have been able to select records but I am unable to insert records (due to my lack of knowledge) when using MS/SQL Server Identity Columns with JDev/ADF.
    The following are the steps taken thus far.
    Step1: Create table named test in the 2005 MSSQL Server (see script below).
    Step2: Register 3rd Party JDBC Driver with JDeveloper; Using use Tools/Manage Libraries. Create a new entry in User Libraries with the following;
         Library Name     = Ms2005Jdbc
         Class Path     = C:\dev\Ms2005Jdbc\sqljdbc_1.0\enu\sqljdbc.jar
         (note: Latest TYPE 4 JDBC driver for Microsoft SQL Server 2005 - free at http://msdn.microsoft.com/data/ref/jdbc/)
    Step3:Create New Database Connection;
         Connection Name = testconn1
         Type = Third Party JDBC Driver
         Authentication Username = sa, Password = password, Check Deploy Password
         Connection
              Driver Class = com.microsoft.sqlserver.jdbc.SQLServerDriver     
              Library = Ms2005Jdbc     
              Classpath = C:\dev\Ms2005Jdbc\sqljdbc_1.0\enu
              URL = jdbc:sqlserver://192.168.1.151:1433;instanceName=sqlexpress;databaseName=test
         Test Connection = Success!
    Step5: Create a new application workspace using Web Application default template
    Step6: In Model project, Create new Business Components Diagram.
    Step7: Create new Entity Object. Goto to connections/testconn1, open tables and drag table test onto the diagram.
    Step8: Generate Default Data Model Components by right-clicking on Entity Object. Except all the defaults.
    When I test the Appmodule I select the view object and can scroll through all the records without error. If I try to insert a record, I get JBO-27014: Attribute testid in test is required.
    Going back to the EntityObject I deselect the Mandatory attribute and re-run the test. Now when I try to insert it accepts the value for testname but it does not update the PK testid like it would using an "JDev/ADF/DBSequence/Oracle database/before trigger/sequence" solution.
    Going back to the EntityObject and selecting refresh on insert does not solve this problem either. Changing the URL connection string and adding "SelectMethod=cursor" did not help and changing the SQl Flavor to SQLServer produced errors in the Business Components Browser. I've tried overriding isAttributeChanged() and other things as well.
    I am totally stuck! Can anyone provide a solution?
    Thanks for you help,
    BG...
    Create table named test
    use [testdb]
    go
    set ansi_nulls on
    go
    set quoted_identifier on
    go
    create table [test](
         [testid] [int] identity(0,1) not null,
         [testname] [nvarchar](50) collate sql_latin1_general_cp1_ci_as not null,
    constraint [pk_test] primary key nonclustered
         [testid] asc
    )with (pad_index = off, ignore_dup_key = off) on [primary]
    ) on [primary]

    Figured it out!
    When using the MS SQL Server 2000 Database with the MS JDBC 2000 Driver you specify the SQL Flavor to SQLServer. However setting the SQL Flavor to SQLServer with MS SQL Server 2005 Database and the MS JDBC 2005 Driver will *** fail ***.
    When working with the MS SQL Server 2005 Database and the MS JDBC 2005 Driver you set the SQL Flavor to SQL92 and the Type Map to Java.
    If using a named instance like I am you would specify the URL = jdbc:sqlserver://<db host ip address>:<listening port>;instanceName=<your instance name>;selectMethod=cursor;databaseName=<your database name> (note: leave out the < >)
    The 2005 Driver Class is different then the 2000 and is specified as com.microsoft.sqlserver.jdbc.SQLServerDriver
    Note: In a default MS SQL Server 2005 installation the listening port will change *** everytime *** the host is restarted! You can override this though.
    For the primary key you need to deselect the Mandatory attribute in the EntityObject editor.
    Set Refresh on insert/update = no.
    Set Updateable = never.
    Now my Primary Keys which get their values from the Identity Column are working with ADF in a predictable way.
    Simple enough but I have been away from this stuff for awhile.
    BG...

  • Need help on resolving the issue with adobe output server - error MSG256 & MSG 210 not in .ini file

    Hi,
    I am using adobe output designer 5.5 for designing the label template and using the Adobe output server for printing process.
    In the Jfmerge.ini we given the condition "DiscardUnknownFields=Yes" for ignoring the unwanted fields in the .dat file.
    During the process, I faced some issue with the output server in printing the labels.
    When the .dat file is placed in the Data folder of adobe, the label is not getting printed in the printer.
    The file is move to the error folder and an error file is getting generated which contains the error message as given below:
    090826 02:59:02 D:\Program Files\Adobe\Central\Bin\jfmerge: [256]** Message Msg256 not in .ini file **
    090826 02:59:02 D:\Program Files\Adobe\Central\Bin\jfmerge: [210]** Message Msg210 not in .ini file **
    2009/08/26 02:59:02 D:\Program Files\Adobe\Central\Bin\jfserver.exe: [314]Agent exit message: [210]** Message Msg210 not in .ini file **
    The output server is a new installtion and I verified the Jfmerge.ini file. It contains the message details of Msg256 and Msg210.
    I also verified the license and it is a valid licence.
    Kindly help me out in solving this issue.
    Thanks
    Senthil

    I assume this is too late to help you, but other might need a hint.  I had the same problem, and found some possible causes that I posted on http://codeznips.blogspot.com/2010/02/adobe-output-server-message-msg210-not.html.
    It is quite likely that you are missing some double quotes around the path specifying the ini file (-aii), if its installed under "Program Files".
    Hope this helps anyone....
    Vegard

  • Problem using DG4ODBC with named SQL Server instance

    I am running DG4ODBC on a 64 bit LINUX machine with the Microsoft SQL Server driver installed. I have successfully tested this with a SQL Server instance that was not named (GENERALI_DSN).The named instance gives the following when trying to query:
    ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
    [unixODBC][Microsoft][SQL Server Native Client 11.0]Login timeout expired {HYT00}[unixODBC][Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF].  {08001,NativeErr = -1}[unixODBC][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. {08001,NativeErr = -1}
    ORA-02063: preceding 2 lines from DEVMISC
    odbc.ini
    [GENERALI_DSN]
    Driver                  = SQL Server Native Client 11.0
    Server                  = CLTDMJCWBYZ.eu.scor.local
    User                    = everest
    Password                = everest
    Database                = Everest_Generali
    [DEVMISC_DSN]
    Driver                  = SQL Server Native Client 11.0
    Server                  = [USVCLTDEVSQL02\DEVMISC]
    User                    = link_user
    Password                = password1
    Database                = DBA
    initDG4ODBC2.ora
    # HS init parameters
    HS_FDS_CONNECT_INFO = DEVMISC_DSN
    HS_FDS_TRACE_LEVEL = DEBUG
    HS_FDS_SHAREABLE_NAME = /usr/lib64/libodbc.so
    # ODBC specific environment variables
    set ODBCINI=/home/oracle/.odbc.ini
    listener.ora
    SID_LIST_LISTENER_GW =
       (SID_LIST =
          (SID_DESC =
           (SID_NAME=DG4ODBC)
          (ORACLE_HOME=/home/oracle/product/11.2.0)
          (ENV=LD_LIBRARY_PATH=/usr/lib64:/home/oracle/product/11.2.0/lib:/opt/micro
    soft/sqlncli/lib)
          (PROGRAM=dg4odbc)
          (SID_DESC =
           (SID_NAME=DG4ODBC2)
          (ORACLE_HOME=/home/oracle/product/11.2.0)
          (ENVS=LD_LIBRARY_PATH=/usr/lib64:/home/oracle/product/11.2.0/lib:/opt/micr
    osoft/sqlncli/lib)
          (PROGRAM=dg4odbc)
    LISTENER_GW =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = TCP)(HOST = usvcltprdoragw)(PORT = 1521))
    tnsnames.ora
    DG4ODBC =
       (DESCRIPTION=
          (ADDRESS=(PROTOCOL=tcp)(HOST=usvcltprdoragw)(PORT=1521))
          (CONNECT_DATA=(SID=DG4ODBC))
          (HS=OK)
    DG4ODBC2 =
       (DESCRIPTION=
          (ADDRESS=(PROTOCOL=tcp)(HOST=usvcltprdoragw)(PORT=1521))
          (CONNECT_DATA=(SID=DG4ODBC2))
          (HS=OK)
    I can't figure out why the named instance does not work but the other one does. Any help would be greatly appreciated!

    Did you check with the ODBC test utility isql (it is installed by default when you install the unixODBC Driver manager) if your ODBC driver can connect at all to that named instance? I have some doubts that it will work either as there was a blog commented by a MS engineer:
    Introducing the new Microsoft ODBC Drivers for SQL Server - Microsoft SQLNCli team blog - Site Home - MSDN Blogs
    who states that named instance connections are not supported using that driver.
    - Klaus

  • MCTS 70-466 Implementing Data Models and Reports with Microsoft SQL Server 2012

    I am searching for training kit for Exam 70-466 (Implementing Data Models and Reports with Microsoft SQL Server 2012) but I think is not published yet. I was expecting its release in Jan or Feb 2014. Would any one can tell me its release date or any place
    where I can find this book.
    Thanks
     

    Hi Azhar lqbal Gondal,
    According to your description, since the issue regards training and certification,
     I suggest you post the question in the Learning forums at
    http://social.technet.microsoft.com/Forums/en-US/home?category=learning. It is appropriate and more experts will assist you. If you have a specific technical question about Microsoft SQL Server,
     you can visit and post your question on  the SQL Server Forum.
    There is some detail about Exam 70-466 Implementing Data Models and Reports with Microsoft SQL Server 2012, you can review the following articles.
    Exam content can be found here:
    http://www.microsoft.com/learning/en-us/exam-70-466.aspx
    http://borntolearn.mslearn.net/certification/database/w/wiki/525.466-implementing-data-models-and-reports-with-microsoft-sql-server-2012.aspx#fbid=Mn-t6aRhs-H
    Regards,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Anyone successfully set up connection pool in s1as with ms sql server 2000?

    As subject. Since I have seen a lot of posts about the NoSuchMethodException issue with various dbms providers, and the only "official information" I found thru different forums, google, different sun/javasoft sites and forums are this:
    http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fsunone%2F8172&zone_32=NoSuchMethodException&wholewords=on
    Which is wonderfully vague and provide not-so-much useful information...
    As for the information and suggestion posted by other forum members, most or all of them have experience with setting up Oracle, DB2, mySQL, etc., not aimed for MS SQL Server 2000 (you may think, I am just asking for it running MS SQL server with Java... oh well, not my choice)
    I still haven't seen any positive feedbacks on how this exception was caused and how to resolve it. I have literally exhausted all leads on how to fix this issue, so right now I'm only interested to know whether anyone in the forum actually have a successful connection pool set up with MS SQL server 2000.
    My platform:
    w2k sp3
    SunOne app server, update1, JDK 1.4.1
    latest MS SQL 2000 JDBC driver
    This fails with the NoSuchMethodException error:
    try {
    InitialContext ic = new InitialContext();
    DataSource ds = (DataSource) ic.lookup("test_db");
    con = ds.getConnection();
    System.out.println( "con is created -> " + con );
    } catch (Exception ex) {
    System.out.println( "failed -> " + ex.getMessage() );
    This works just fine:
    try {
    Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
    con = DriverManager.getConnection("jdbc:microsoft:sqlserver://xxx.xxx.xxx.xxx:1433;DatabaseName=testdb;SelectMethod=cursor", "username", "password");
    System.out.println( "con is created -> " + con );
    } catch (Exception ex) {
    System.out.println( "failed is fucked -> " + ex.getMessage() );
    thanks,
    --kuan

    Hi,
    Thanks for pointing out that article, I did not find it previously. After following the directions in the artile and your advise, now dbping seems to be able to connect to SQL server.
    Thank you very much.
    --kuan                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • Problem with NW04s SR2 installation with MS SQL Server 2000 SP4

    I’m struggling with the NW04s installation with MS SQL Server 2000.
    The installation stops at the step “Create/modify database schema SAPJ2EDB”.
    The following error/info from log file,
    INFO       2007-06-06 12:02:33 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step doConfiguration of component |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_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|NW_MSS_SRVCFG|ind|ind|ind|ind|6|0.
    INFO       2007-06-06 12:02:35 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step doTempdb of component |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_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
    INFO       2007-06-06 12:02:36 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step doSwitch of component |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_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
    INFO       2007-06-06 12:02:36 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step doTempDBAnalyze of component |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_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
    INFO       2007-06-06 12:02:37 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step doTempDBBeforeRestart of component |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_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
    INFO       2007-06-06 12:02:38 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step doRestartServer of component |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_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
    INFO       2007-06-06 12:02:58 [ianxbservi.cpp:697]
               CIaNtServices::stop(const map<iastring,iastring>&)
    The service 'MSSQLSERVER' stopped successfully on host 'GBCZ672C'.
    INFO       2007-06-06 12:03:10 [ianxbservi.cpp:632]
               CIaNtServices::start(const map<iastring,iastring>&)
    The service 'MSSQLSERVER' started successfully on host 'GBCZ672C'.
    INFO       2007-06-06 12:03:21 [ianxbservi.cpp:632]
               CIaNtServices::start(const map<iastring,iastring>&)
    The service 'SQLSERVERAGENT' started successfully on host 'GBCZ672C'.
    INFO       2007-06-06 12:03:21 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step doTempDBAfterRestart of component |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_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
    INFO       2007-06-06 12:03:22 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step doChangeTempSetNewSize of component |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_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
    INFO       2007-06-06 12:03:39 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step CheckParameters of component |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_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0.
    INFO       2007-06-06 12:03:39 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step CreateDirectories of component |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_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0.
    INFO       2007-06-06 12:03:40 [iaxxgenimp.cpp:632]
               showDialog()
    Execute step CreateDatabase of component |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_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0.
    ERROR      2007-06-06 12:03:40 [iaxxgenimp.cpp:731]
               showDialog()
    FCO-00011  The step CreateDatabase 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_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0|CreateDatabase was executed with status ERROR .
    ERROR      2007-06-06 12:03:40
               lib=iamodmssql module=CIaNtMssDmo
    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.
    INFO       2007-06-06 12:04:04 [iaxxgenimp.cpp:774]
               showDialog()
    An error occured and the user decided to retry the 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_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0|CreateDatabase".
    ERROR      2007-06-06 12:04:05 [iaxxgenimp.cpp:731]
               showDialog()
    FCO-00011  The step CreateDatabase 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_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0|CreateDatabase was executed with status ERROR .
    Please let me know if you can help or if there is any other way around.
    Many Thanks in advance.
    Ritin Jain

    Hi All,
    I was not able to solve the problem with MS SQL 2000, but I was able to resolve the issue with MS SQL 2005.
    You have to chhose the following settings while instalation,
    Service Account - Select one of the following options:
    1) Use the built-in System account for each service and choose Local system or Network Service.
    2) Use a domain user account, and enter the user name and password.
    Under Start services at the end of setup make sure that SQL Server and SQL Server Agent are selected.
    Authentication Mode      
    1) Select Mixed Mode (Windows Authentication and SQL Server Authentication).
    This mode is required for a Java or ABAP+Java system.
    If you choose this mode, you have to set the password for the sa login.
    Note: The password for the sa login must comply with the Windows password policy.
    Collation Settings      
    1) Select SQL collations (used for compatibility with previous versions of SQL Server).
    2) From the drop-down list select Binary order based on code point comparison, for use with the 850 (Multilingual) Character Set.
    I hope this helps!

  • Credentials issue with MS SQL Express 2014

    Hello,
    I have kind of simple issue but I failed to resolve it. Here's the issue:
    I have SQL Server Express 2014 installed on my PC. I have to use SQL Server authentication. As 'sa' I created login and user e.g. user1. Then as user1 I created DB e.g. db1 and a few tables. Now I could login into db1 as user1 using SQL Server authentication.
    This db1 will be used by application e.g. app1. This app1 has configuration file that has all credentials and other connection string things. Well when I start that application it throws error "Can't connect to database". Then I look into log and
    see this: Error: 18456, Severity: 14, State: 8. Login failed for user 'user1'. Reason: Password did not match that for the login provided .  Then I could disable credential check in configuration file of app1 and then I don't have problem to start app1.
    Then I tried to created ODBC connection and use the same credentials and I succeed to connect. Could some give the idea what could be wrong and I can't connect to db1 from my app1? Thanks

    Reset the password of the login, i have already this problem.
    Not forget the connection string syntaxe, do not make the space after and before (=) example :
    Server=myServerAddress;Database=myDataBase;User
    Id=myUsername;
    Password=myPassword;
    Thanks for suggestion ... but could you please tell me why  to reset login password ( I could use this password successfully when login from Studio i.e. it's correct.
    Could you please give me sqlcmd example how to connect to my db1 using connection string. That way I should be able to check which users are capable to login.
    N.B. I am planning to play with Trusted Connection because Shanky_621 suggested that value 'false' (like in my case means Windows Authentication). In my case user1 is not Windows user .. it's SQL Authentication user.
    Thanks

  • 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

Maybe you are looking for