Problems with SQLCMD prompt SQL Express 2008

"When attempting to run this installer (SQLCMD T-SQL execution command line utility), I get the DOS screen but not the 1> command prompt. If I leave the screen alone, the DOD command window closes after about 5 seconds.
"C:\Program Files\Microsoft SQL Server\90\Tools\binn\SQLCMD" -S "machine-name\SqlExpress""
nuno vieira
Hi All
Can someone help me please?
ive just got a new machine and not had this problem before, at one point the error which appeared briefly before the command prompt window disappeared said it was the namepipe, so i enabled this, that didnt work so i uninstalled, and reinstalled SQL Server 2005.
The next error message i received when the command prompt was closing was (in brief)
HRESULT 0xFFFFFFF Level 16, State 1
an error occurred whilst establishing a connection to the server
Sqlcmd: Error: Microsoft Native Client : Login timeout expired.
I have just updated to sql server 2008 and the same thing happened. I cant paste into the SQLCMD window and I havent got a 1> command prompt.
I tried to drop down into dos prompt and it wouldn't accept it said "the filename, directory name or volume syntax is incorrect".
I turned on iis, ive tried everything I can think of, i have come to the conclusion it must be something to do with the version of Windows Vista Home Premium I am running, I haven't had any problems on any other machines XP or Vista.
Any help would be gratefully accepted.
Cheers
sgblank

You haven't supplied an authentication context for your connection so you can't connect and it times out. Try the following at a command prompt:
Code SnippetSqlCML -S "machine-name\SQLEXPRESS" -E
This will log in using Windows Authentication.
Regards,
Mike

Similar Messages

  • Problem accessing SQL Express 2008 R2 after VS package install

    I've written an application package in Visual Studio 2010 which requires SQL Express 2008 R2. I've also created a separate setup package and set SQL Express as a prerequisite. Everything runs as expected except that after the install on target machine
    I do not have adequate permissions in SQL to attach the database or set up the user via SQLCMD script. This happens on WIN 7 and up. I know it is a permissions issue with the default install of SQL but do not know how to otherwise perform the install and make
    it work. Looking for someone to walk me through and resolve this issue.

    Hi Zanith,
    Actually this forum is to discuss the VS IDE issue.
    >> Everything runs as expected except that after the install on target machine I do not have adequate permissions in SQL to attach the database or set up the user via SQLCMD script
    Based on your description, the important issue would be related to the permission, as my understanding, it would be related to the SQL Server setup or configuration.
    So my suggestion is that you’d better post this issue to the SQL Server forum.
    https://social.technet.microsoft.com/Forums/en-US/home?forum=sqlgetstarted
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/home?forum=sqlexpress
    I also found two cases about the SQL Server permission issue.
    Reference:
    http://stackoverflow.com/questions/9185142/sql-server-2008-r2-express-permissions-cannot-create-database-or-modify-users
    http://serverfault.com/questions/53645/don-t-have-permission-to-access-sql-server-express-2008
    Best Regards,
    Jack
    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.

  • Client access from W7 to Server 2008 with SQL Express 2008 R2 not possible anymore (since installing yesterdays patches)

    Hi everyone!
    We are suddenly having Problems to access our SQL Express Server from our Clients (SBS 2008 with W7 clients).
    Till yesterday evening everything was working fine. At night we installed the latest MS patches für our Server 2008 (SBS2008).
    Since then we are not able to connect to the SQL Express Server over the Network. Locally (on the Server) it runs fine.
    Switching the Windows Firewall off on the Server also lets the clients connect ...
    The Windows Firewall still has all the ports open needed for SQL Server, we havn't changed anything.
    All the incoming rules that worked for years are still there (untouched).
    We just deinstalled all the latest patches, but problem still is here ... not sure if this was just a coincidence ...
    Any ideas what could be the Problem?
    Thanks in advance for your help
    Best regards
    Thomas

    Check firewall rules
    enable traffic on TCP 1433 and UDP 1434 (if isn't a named instance) or check sql using ports.
    Check Sql Server Browser in Configuration Manager and also net protocols.
    let's know about it
    Best regards,
    P.Ceglie
    Questo post è fornito "così com'è". Non conferisce garanzie o diritti di alcun tipo. Ricorda di usare la funzione "segna come risposta" per i post che ti hanno aiutato a risolvere il problema e "deseleziona come risposta" quando
    le risposte segnate non sono effettivamente utili. Questo è particolarmente utile per altri utenti che leggono il thread, alla ricerca di soluzioni a problemi similari. ENG: This posting is provided "AS IS" with no warranties, and confers no rights.
    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Could you please confirm that the Service Pack 3 will install on SQL Express 2008 R2 SP2 With Advanced Services.

    We are using SQL server  Express 2008 R2 SP2 With Advanced Services.Its a 64 bit server.We want to Patch Service Pack 3 On express edition. Could you please
    tell us whether  the Service Pack 3 will install on SQL Express 2008 R2 SP2 With Advanced Services or not
    Could you please suggest me on this.
    Sainath Kompelly

    No, you cannot install SP3 on Express edition as Microsoft did not release it for Express Edition as noted here: http://blogs.msdn.com/b/sqlreleaseservices/archive/2014/09/26/sql-server-2008-r2-service-pack-3-has-released.aspx.
    You can see that Express edition is missing from the list of supported editions in the details section here: http://www.microsoft.com/en-us/download/details.aspx?id=44271
    Satish Kartan www.sqlfood.com

  • Mobile Client 7.0 SP04 with SQL Express 2008 R2

    Does anyone know if you can install SQL Express 2008 R2 with MSA 70. sp04 on Windows XP?
    Any help / advice would be appreciated
    regards
    Barry

    Hi Barry,
    You will find SwitchDB.exe in %mobilerootdir%\Bin.Net folder. And running it is fairly simple once you have the IDES .car file present in DVD structure(you may search all *.car files). Copy that .car file onto your local disk.
    After the IDES DB is attached ,you may run ides_empty_logins.sql also located in Bin.Net path.
    Regards,
    Rohit

  • SQL Express 2008 R2 Error:15209 - An error occurred during encryption

    I am trying to install SQL Server Express 2008 R2 but it keeps failing .
    The computer is Windows 7 x64, all the latest service packs and updates installed. 
    The application is by Greatland, called Yearli (formerly called WinFiler). 
    Last year’s WinFiler, which was installed on this PC, used SQL 2008 Express (x86). 
    This year’s version is using R2 and attempted to install a new database. 
    I have since uninstalled last year’s database.
    When I run the Yearli install, it first attempts to install SQL Express 2008 R2, but the install fails with this error at the end of ERRORLOG:
    Error: 15209, Severity: 16, State: 1. "An error occurred during encryption."
    I have been researching this for days.  What I have done so far, based on MSKB and other user posts, is the following:
    Changed the account for the SQL service from Local System to NETWORK SERVICE. 
    Add NETWORK SERVICE to the “Protect” folder with Full permission added.
    Neither of these have worked.  SQL appears to be installed, but the service will not start.
    In the Windows System log I get this message:
    The SQL Server (WFP_SS8E) service terminated with service-specific error The specified resource name cannot be found in the image file..
    In the Windows Application log I get this message:
    FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf'. Diagnose and correct the operating system error,
    and retry the operation.
    The App log error is interesting because there is no E: drive on the system.
    SFC /Scannow came up clean.
    I don’t have any other ideas, so if anyone else does, I’d appreciate it.

    SQL appears to be installed, but the service will not start.
    In the Windows System log I get this message:
    The SQL Server (WFP_SS8E) service terminated with service-specific error The specified resource name cannot be found in the image file..
    In the Windows Application log I get this message:
    FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf'. Diagnose and correct the operating system error,
    and retry the operation.
    Hi dfosbenner,
    According to your description, SQL Server fails to start and you get the error message (Operating system error 2……) in Windows Application log. To work around this issue, you might have to change the path of the files by running the following scripts from
    the command prompt. The example is to put MSDB files in C drive, you can change the path of the files to other drives.
    NET START MSSQL$SQLEXPRESS /f /T3608
    SQLCMD -S .\SQLEXPRESS
    ALTER DATABASE msdb MODIFY FILE ( NAME = MSDBData, FILENAME = 'C:\MSDBData.mdf');
    ALTER DATABASE msdb MODIFY FILE ( NAME = MSDBLog, FILENAME = 'C:\MSDBLog.ldf');
    go
    exit;
    NET STOP MSSQL$SQLEXPRESS
    For more details, please review the following thread.
    https://social.msdn.microsoft.com/Forums/sqlserver/en-US/54bbcac3-41c5-4a5d-a4f6-2669e538dc82/sqlserver-2008-express-install-error?forum=sqlexpress
    Thanks,
    Lydia Zhang

  • SQL Express 2008 R2 will not start on Windows 7 Home

    Ok, This used to work, and then over night my system rebooted and now I cannot start SQL Express 2008 R2 after I have unistalled, and re-installed.   Cleared out the folders and the certificates, changed the Named Pipes configuration and all to
    no avail.   Here is my log file.
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    2014-06-14 08:45:18.18 Server      Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
        Jun 17 2011 00:54:03
        Copyright (c) Microsoft Corporation
        Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
    2014-06-14 08:45:18.18 Server      (c) Microsoft Corporation.
    2014-06-14 08:45:18.18 Server      All rights reserved.
    2014-06-14 08:45:18.18 Server      Server process ID is 8924.
    2014-06-14 08:45:18.18 Server      System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '700Z3A/700Z4A/700Z5A/700Z5B'.
    2014-06-14 08:45:18.18 Server      Authentication mode is MIXED.
    2014-06-14 08:45:18.18 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.ACT7\MSSQL\Log\ERRORLOG'.
    2014-06-14 08:45:18.18 Server      This instance of SQL Server last reported using a process ID of 2820 at 6/14/2014 8:32:55 AM (local) 6/14/2014 1:32:55 PM (UTC). This is an informational message only; no user action is required.
    2014-06-14 08:45:18.18 Server      Registry startup parameters:
         -d C:\Program Files\Microsoft SQL Server\MSSQL10_50.ACT7\MSSQL\DATA\master.mdf
         -e C:\Program Files\Microsoft SQL Server\MSSQL10_50.ACT7\MSSQL\Log\ERRORLOG
         -l C:\Program Files\Microsoft SQL Server\MSSQL10_50.ACT7\MSSQL\DATA\mastlog.ldf
    2014-06-14 08:45:18.18 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-06-14 08:45:18.18 Server      Detected 8 CPUs. This is an informational message; no user action is required.
    2014-06-14 08:45:18.21 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.
    2014-06-14 08:45:18.23 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.
    2014-06-14 08:45:18.25 spid7s      Starting up database 'master'.
    2014-06-14 08:45:18.28 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'ACT7'.
    2014-06-14 08:45:18.29 spid7s      SQL Trace ID 1 was started by login "sa".
    2014-06-14 08:45:18.29 spid7s      Starting up database 'mssqlsystemresource'.
    2014-06-14 08:45:18.30 spid7s      The resource database build version is 10.50.2500. This is an informational message only. No user action is required.
    2014-06-14 08:45:18.32 spid7s      Server name is 'MARTINDAHL-PC\ACT7'. This is an informational message only. No user action is required.
    2014-06-14 08:45:18.32 spid10s     Starting up database 'model'.
    2014-06-14 08:45:18.32 spid7s      Informational: No full-text supported languages found.
    2014-06-14 08:45:18.32 spid7s      Starting up database 'msdb'.
    2014-06-14 08:45:18.33 Server      Error: 17190, Severity: 16, State: 1.
    2014-06-14 08:45:18.33 Server      Initializing the FallBack certificate failed with error code: 1, state: 1, error number: -2146893802.
    2014-06-14 08:45:18.33 Server      Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
    2014-06-14 08:45:18.33 Server      Error: 17182, Severity: 16, State: 1.
    2014-06-14 08:45:18.33 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
    2014-06-14 08:45:18.33 Server      Error: 17182, Severity: 16, State: 1.
    2014-06-14 08:45:18.33 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
    2014-06-14 08:45:18.33 Server      Error: 17826, Severity: 18, State: 3.
    2014-06-14 08:45:18.33 Server      Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2014-06-14 08:45:18.33 Server      Error: 17120, Severity: 16, State: 1.
    2014-06-14 08:45:18.33 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
    -=-=-=-=-=-=-=-=-=-=
    I am logged into either the Administrator Account or my Account in which I am in the Adminstrator Group or an Admin.   My OS is Windows 7 Home Premium Edition, so I cannot clear out the MSSQL groups and things I have seen online.  Since this
    is Express, there is limited capabilities with the config tool.  
    I have tried to change the log in as in the SQL Configuration tool and every item I check, Local Service, Local System, Network Service all give the same error,
    "Cannot Find Object or Property. [0x80042004]
    SInce I have Home Premium, MMC will not load the snap in for Local Users and groups to check out these items.
    A check of the net user shows only the Administrator, Guest and my local login in Admin Account.  net localgroups show these items.
    *Administrators
    *Distributed COM Users
    *Event Log Readers
    *Guests
    *HomeUsers
    *IIS_IUSRS
    *IIS_WPG
    *Performance Log Users
    *Performance Monitor Users
    *SQLServer2005SQLBrowserUser$MARTINDAHL-PC
    *SQLServerFDHostUser$MartinDahl-PC$ACT7
    *SQLServerMSSQLServerADHelperUser$MARTINDAHL-PC
    *SQLServerMSSQLUser$MartinDahl-PC$ACT7
    *SQLServerSQLAgentUser$MARTINDAHL-PC$ACT7
    *Users
    The command completed successfully.
    I checked the SSL and Force Encryption is set to no and the certificates have been cleared.  
    I am not sure how to solve this problem.   Please help.   Thanks, in advance. 

    I created a new Administrator account on the machine, mdahl.   I then started the SQL Configuration Tool and changed the log on to this new account.  Same problem.   Here is the SQL Log.
    2014-06-14 11:24:15.83 Server      Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
        Jun 17 2011 00:54:03
        Copyright (c) Microsoft Corporation
        Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
    2014-06-14 11:24:15.83 Server      (c) Microsoft Corporation.
    2014-06-14 11:24:15.83 Server      All rights reserved.
    2014-06-14 11:24:15.83 Server      Server process ID is 11448.
    2014-06-14 11:24:15.83 Server      System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '700Z3A/700Z4A/700Z5A/700Z5B'.
    2014-06-14 11:24:15.83 Server      Authentication mode is MIXED.
    2014-06-14 11:24:15.83 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.ACT7\MSSQL\Log\ERRORLOG'.
    2014-06-14 11:24:15.83 Server      This instance of SQL Server last reported using a process ID of 5952 at 6/14/2014 11:21:35 AM (local) 6/14/2014 4:21:35 PM (UTC). This is an informational message only; no user action is required.
    2014-06-14 11:24:15.83 Server      Registry startup parameters:
         -d C:\Program Files\Microsoft SQL Server\MSSQL10_50.ACT7\MSSQL\DATA\master.mdf
         -e C:\Program Files\Microsoft SQL Server\MSSQL10_50.ACT7\MSSQL\Log\ERRORLOG
         -l C:\Program Files\Microsoft SQL Server\MSSQL10_50.ACT7\MSSQL\DATA\mastlog.ldf
    2014-06-14 11:24:15.83 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-06-14 11:24:15.83 Server      Detected 8 CPUs. This is an informational message; no user action is required.
    2014-06-14 11:24:15.87 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.
    2014-06-14 11:24:15.88 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.
    2014-06-14 11:24:15.90 spid7s      Starting up database 'master'.
    2014-06-14 11:24:15.91 spid7s      1 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
    2014-06-14 11:24:15.91 spid7s      0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
    2014-06-14 11:24:15.91 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2014-06-14 11:24:15.92 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'ACT7'.
    2014-06-14 11:24:15.93 spid7s      SQL Trace ID 1 was started by login "sa".
    2014-06-14 11:24:15.93 spid7s      Starting up database 'mssqlsystemresource'.
    2014-06-14 11:24:15.93 spid7s      The resource database build version is 10.50.2500. This is an informational message only. No user action is required.
    2014-06-14 11:24:16.03 spid7s      Server name is 'MARTINDAHL-PC\ACT7'. This is an informational message only. No user action is required.
    2014-06-14 11:24:16.03 spid10s     Starting up database 'model'.
    2014-06-14 11:24:16.03 spid7s      Informational: No full-text supported languages found.
    2014-06-14 11:24:16.03 spid7s      Starting up database 'msdb'.
    2014-06-14 11:24:16.03 Server      Error: 17190, Severity: 16, State: 1.
    2014-06-14 11:24:16.03 Server      Initializing the FallBack certificate failed with error code: 1, state: 1, error number: -2146893802.
    2014-06-14 11:24:16.03 Server      Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
    2014-06-14 11:24:16.03 Server      Error: 17182, Severity: 16, State: 1.
    2014-06-14 11:24:16.03 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
    2014-06-14 11:24:16.03 Server      Error: 17182, Severity: 16, State: 1.
    2014-06-14 11:24:16.03 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
    2014-06-14 11:24:16.03 Server      Error: 17826, Severity: 18, State: 3.
    2014-06-14 11:24:16.03 Server      Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
    2014-06-14 11:24:16.03 Server      Error: 17120, Severity: 16, State: 1.
    2014-06-14 11:24:16.03 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
    Also, the link you provided is to Windows Vista, not Windows 7 Home Premium.  However, I did look at the registry setting they said to look at in the link.
    Locate the following registry subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
    Under the ProfileList subkey, delete the subkey that is named <var>SID</var>.bak.
    Note <var>SID</var> is a placeholder for the security identifier (SID) of the user account that is experiencing the problem. The <var>SID</var>.bak subkey should contain a ProfileImagePath registry entry that points to the original profile
    folder of the user account that is experiencing the problem.
    Exit Registry Editor.
    Looking into my registry for my ProfilesList as mentioned. I have these items.
    S-1-5-19 Folder with Default (Value not set), Flags (REG_DWORD) 0x0000000, ProfileImagePath (REG_EXPANDS_SZ) C:Windows\ServiceProfiles\LocalService, State (REG_DWORD) 0x0000000
    S-1-5-20 Folder with Default (Value not set), Flags (REG_DWORD) 0x0000000, ProfileImagePath (REG_EXPANDS_SZ) C:Windows\ServiceProfiles\NetworkService, State (REG_DWORD) 0x0000000
    Then I have an item for each of my three accounts, Administrator, Martin Dahl, and mdahl, All admin Accounts, which has no sid.bak, but a Sid, so not sure how this link helps me either.   Still looking for assistance.  Still not starting.

  • SQL Express 2008 R2 and SQL 2005 Server SP1 in single Windows 2003 server

    Hi,
    I am using a Windows Server 2003 R2 Enterprise Ed SP2 OS with SQL 2005 SP1 intallled on it for our Nav 5 database.
    As my backup software requires SQL Express 2008 R2 as default daabase, is it possible to install this in the same server with the SQL 2005 currently running on it? Would there be any impact on the existing SQL 2005 and the application and the Navision database
    on it?
    Appreciate your help.
    Sharon Lo

    Hi,
    I am using a Windows Server 2003 R2 Enterprise Ed SP2 OS with SQL 2005 SP1 intallled on it for our Nav 5 database.
    As my backup software requires SQL Express 2008 R2 as default daabase, is it possible to install this in the same server with the SQL 2005 currently running on it? Would there be any impact on the existing SQL 2005 and the application and the Navision database
    on it?
    There is no issue with installing multiple versions of SQL Server on a machine.I have SS 2005 ,2008 R2 and 2012 all on same machine and they work just fine. You can install all version instances side by side and all will work independently from
    each other.
    Now issue which might cause problem  your SQL Server 2005 is SP1 which is a Blunder IMO. Please ASAP patch it to SP4 because you are running very old version of 2005 which is unsupported by Microsoft and also SP4 includes MANY fixes for SQLServer
    2005. Applying SP4 will fix many issues and will bring you under Microsoft support.
    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

  • SQL Express 2008 to 2012 express upgrade not working

    I'm trying to upgrade an older version of SQL Express 2008 to 2012 by first upgrading to (what I think is) 2008 SP3 (10.0.5500.0).
    The upgrade to 2008 SP3 says it has completed and the version of the browser and client etc are showing as 10.3.5500.0 but the SQL Server version is still showing as 10.0.2531.0 in the errorlog. When I run the 2012 install exe (11.0.2100.60) it is failing
    on "SQL Server 2008 Service Pack 2 or later is required"
    I'm not very experienced when it comes to SQL so any help would be appreciated.

    You are probably using a regular version of SP3 to upgrade. Express edition has a separate download which included service packs.
    Please download the appropriate package from this link, provide the same instance name which you want to upgrade (as if you were to install a new instance with that name) and setup will run in upgrade mode". It will apply SP3 on existing express instance. 
    http://www.microsoft.com/en-in/download/details.aspx?id=27597
    Let me know if you need help selecting the right exe from the above link. 
    HTH
    This posting is provided “AS IS” with no warranties, and confers no rights.
    If this reply answers your question, please mark it as Answered for others to find it easily.
    If this reply help you resolving the problem, please vote the post as Helpful.

  • Problem with dashboard prompt initial value (OBIEE 11g)

    Hi alli,
    I have a problem with dashboard prompt and session variable in OBIEE 11g.
    I have declared a session non-system variable which I set/change with dashboard prompt. At login the variable is initialized in initialization block that gets a value from an SQL select statement.
    When I change the value in prompt, the session variable changes accordingly, as it should (change is made by calling function NQSSetSessionValue() within javascript function). While I am in my dashboard, cruising around pages the variable stays the same, and when I return to the page that has prompt on it, the correct value is shown. Everything works fine.
    The problem occures when I go to Catalog (in presentation services) to create some new Answers. When I return back to the same page in dashboard (which has a prompt), the prompt selected value and session variable are set back to the default value. It looks like the initialization block is executed again.
    My prompt is configured like this:
    - Choice List Values: SQL Results
    - Default selection: Variable Expression (@{biServer.variables['NQ_SESSION.VariableName']} )
    - Set a variable: Presentation Variable
    Is there a way to stop the initialization block from executing again? Isn't it logical that the initialization block executes only at login, when the session variable is empty? I don't need it to execute every time i come to the dashboard.
    Thanks in advance,
    Marko
    Edited by: markor on 14.3.2011 8:58

    How and where do you use the nqssetvalue() function.
    I tried it in several places but it doesn't work.
    Can you help me, please!
    Thanks

  • Cannot find service {0}. Parameter name: SQLWriter SQL Express 2008 R2 SP2

    Hi, installing SQL Express 2008 R2 SP2 onto Windows Server 2012 R2.   I had previously removed SQL Express 2012 due to failed install due to incompatibility with our SAN.   (I had uninstalled it via Programs & Features,
    and also by following Shanky's tips. http://social.technet.microsoft.com/wiki/contents/articles/24364.sql-server-troubleshooting-could-not-find-database-engine-startup-handle-error-during-installation.aspx).
    This is what's in Detail log: 
    014-10-07 13:12:00 Slp: Parameter 5 : SqlEngineConfigAction_install_confignonrc
    2014-10-07 13:12:00 Slp: Parameter 6 : 0x50806C41
    014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
    2014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
    2014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL
    Server.reg_
    2014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
    2014-10-07 13:12:02 Slp: Cannot find service {0}.
    The SqlEngineConfigAction_install_confignonrc part is what is in the background before the
    Cannot find service {0}. Parameter name: SQLWriter pops up.
    And in Event Viewer:
    Log Name:      Application
    Source:        Microsoft-Windows-RestartManager
    Date:          10/7/2014 1:11:48 PM
    Event ID:      10010
    Task Category: None
    Level:         Warning
    Keywords:     
    User:          SYSTEM
    Computer:     
    Description:
    Application 'C:\31f53f2e988a36f2c31e\x64\setup100.exe' (pid 688) cannot be restarted - Application SID does not match Conductor SID..
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-RestartManager" Guid="{0888E5EF-9B98-4695-979D-E92CE4247224}" />
        <EventID>10010</EventID>
        <Version>0</Version>
        <Level>3</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2014-10-07T20:11:48.532980400Z" />
        <EventRecordID>4538</EventRecordID>
        <Correlation />
        <Execution ProcessID="732" ThreadID="2548" />
        <Channel>Application</Channel>
        <Computer></Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <UserData>
        <RmUnsupportedRestartEvent xmlns="http://www.microsoft.com/2005/08/Windows/Reliability/RestartManager/">
          <RmSessionId>0</RmSessionId>
          <Pid>688</Pid>
          <FullPath>C:\31f53f2e988a36f2c31e\x64\setup100.exe</FullPath>
          <DisplayName>Managed SQL Server Installer</DisplayName>
          <AppVersion>0</AppVersion>
          <AppType>5</AppType>
          <TSSessionId>2</TSSessionId>
          <Status>67108865</Status>
          <Reason>1</Reason>
        </RmUnsupportedRestartEvent>
      </UserData>
    </Event>
    Found one article saying you can get this if previous version not fully removed, and to do a repair of the previous version, but as I said I uninstalled it and followed all steps for cleanup, so nothing to repair. 

    Here is the ERRORLOG file from C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log.  At the bottom I am seeing the error you said before was a SAN issue.  I had hoped that issue was only with
    SQL 2012, but it appears it is even with 2008?
    If that is still the issue, I'm trying to understand if by the articles, if the SAN conflict is an OS issue or an SQL issue?   In other words, is it because the OS is Server 2012?   Or would this still occur if I install SQL
    2008 on Server 2008 R2?    I don't know that they will be willing to upgrade the SAN, and I don't really want to fool with a .VHD (virtual disk) as a workaround speaks of.
    If you're asking if I did this from your article:  select startup account for Database Engine services as NT Authority\SYSTEM 
    , I don't recall what I did this last time.  I was doing that the last few days, but I think I didn't switch it to that once, just to see if I would have success.  I don't know if that was this last time or not when I switched it. 
    Is there anywhere I can check that after the fact?
    014-10-08 12:53:09.84 Server      Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64)
     Jun 28 2012 08:36:30
     Copyright (c) Microsoft Corporation
     Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
    2014-10-08 12:53:09.84 Server      (c) Microsoft Corporation.
    2014-10-08 12:53:09.84 Server      All rights reserved.
    2014-10-08 12:53:09.84 Server      Server process ID is 2640.
    2014-10-08 12:53:09.84 Server      System Manufacturer: 'IBM', System Model: 'IBM System x -[7870AC1]-'.
    2014-10-08 12:53:09.84 Server      Authentication mode is WINDOWS-ONLY.
    2014-10-08 12:53:09.84 Server      Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2014-10-08 12:53:09.84 Server      This instance of SQL Server last reported using a process ID of 2848 at 10/8/2014 10:56:44 AM (local) 10/8/2014 5:56:44 PM (UTC). This is an informational message only; no user action is required.
    2014-10-08 12:53:09.84 Server      Registry startup parameters:
      -d c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
      -e c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
      -l c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2014-10-08 12:53:09.84 Server      Command Line Startup Parameters:
      -m SqlSetup
      -f
      -Q
      -q SQL_Latin1_General_CP1_CI_AS
      -T 4022
      -T 4010
      -T 3659
      -T 3610
      -T 902
      -d c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\master.mdf
      -l c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\mastlog.ldf
    2014-10-08 12:53:09.86 Server      Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically. 
    After the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
    2014-10-08 12:53:09.86 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-10-08 12:53:09.86 Server      Detected 16 CPUs. This is an informational message; no user action is required.
    2014-10-08 12:53:10.00 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2014-10-08 12:53:10.01 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.
    2014-10-08 12:53:10.01 Server      Lock partitioning is enabled.  This is an informational message only. No user action is required.
    2014-10-08 12:53:10.03 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.
    2014-10-08 12:53:10.05 Server      Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No
    user action is required.
    2014-10-08 12:53:10.06 spid7s      Warning ******************
    2014-10-08 12:53:10.06 spid7s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2014-10-08 12:53:10.06 spid7s      Starting up database 'master'.
    2014-10-08 12:53:10.08 spid7s      Error: 5178, Severity: 16, State: 1.
    2014-10-08 12:53:10.08 spid7s      Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\master.mdf' because it was originally formatted with sector size 4096 and is now on a volume with sector
    size 2097152. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
    2014-10-08 12:53:10.09 spid7s      Error: 5178, Severity: 16, State: 1.
    2014-10-08 12:53:10.09 spid7s      Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\master.mdf' because it was originally formatted with sector size 4096 and is now on a volume with sector
    size 2097152. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
    2014-10-08 12:53:10.09 spid7s      Error: 5178, Severity: 16, State: 1.
    2014-10-08 12:53:10.09 spid7s      Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\mastlog.ldf' because it was originally formatted with sector size 4096 and is now on a volume with
    sector size 2097152. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
    2014-10-08 12:53:10.09 spid7s      Error: 5178, Severity: 16, State: 1.
    2014-10-08 12:53:10.09 spid7s      Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\mastlog.ldf' because it was originally formatted with sector size 4096 and is now on a volume with
    sector size 2097152. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.

  • SQL express 2008 r2 on windows server 2003

    install ends with the following error :
    "MsiEnumRelatedProducts failed to enumerate products with UpgradeCode='{1B117BA7-5BC1-419E-820E-7D4F3F412C7B}'. Error code: 1610."

    Hi Hadi,
    Did you reinstall your SQL Express 2008 R2 or you did a fresh installation? According to the error message "MsiEnumRelatedProducts failed to enumerate products with
    UpgradeCode='{1B117BA7-5BC1-419E-820E-7D4F3F412C7B}'. Error code: 1610." , this issue is probably caused by that you tried to install SQL Server Express 2008 R2 with some components which had been installed.
    So if you are going to reinstall the SQL Server 2008 R2, please try to remove the old SQL Server by the following steps, and reinstall the SQL Server Express 2008 R2
    again:
      1. Make sure you have administrative rights on the computer.
      2. Uninstall the existing SQL Server 2008 and all the components from the control panel.
      3. Backup the registry.
      4. Delete the following keys in regedit:
            --HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server
            --HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
     5. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall  and delete all the sub-keys referencing SQL Server.
     6. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and delete all the keys referencing SQL Server.
     7. Rename all the SQL Server folders in the computer.
     8. Reboot the machine
      9. Install SQL Server again.
    To further investigation, please collect the error messages logged into the setup log files which are located in the %Program files%\Microsoft SQL Server\100\Setup
    bootstrap\Log\ folder.
    You can send the logs to sqltnsp AT Microsoft.com (Please replace AT with @) with this format:
    #Sample
    Subject: MSDN/TechNet forum question: <Thread Title>
    Attachments: <files>
    Hi Grace,
    ThreadURL:<URL>
    <Additional information>
    #End
    For more information about how to View and Read SQL Server Setup Log Files, please see
    http://msdn.microsoft.com/en-us/library/ms143702.aspx.
    If you have any other questions, please feel free to ask.
    Thanks,
    Grace

  • I have problem with login in sql Server give me support .pre login handshake

    I have problem with login in sql Server give me support .pre login handshake

    The following threads are on the same topic:
    http://www.sql-server-performance.com/forum/threads/pre-login-handshake-error-when-connecting-to-db.687/
    http://stackoverflow.com/questions/12308340/sql-server-2000-connection-error-pre-login-handshake
    http://dbaspot.com/sqlserver-server/458011-error-occurred-during-pre-login-handshake-microsoft-sql-server-error-10054-a.html
    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

  • SQL Express 2008 Management Studio : licensed under 'Microsoft Public License 4

    Please help me to provide answer of the following question:
    Is "SQL Express 2008 Management Studio" licensed under 'Microsoft Public License 4'?
    Awaiting for your reply.
    Thanks

    Hi Anindita Roy,
    Thank you for your post.
    For more detailed information regarding to the license issue, please call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. For international customers, please use the Guide
    to Worldwide Microsoft Licensing Sites to find contact information in your locations.
    Thanks,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • Problem with connect to sql server ..

    I have problem with connect to sql server2005
    i use jpa(hibernate) and jsf
    javax.servlet.ServletException: javax.persistence.PersistenceException: org.hibernate.exception.JDBCConnectionException: Could not open connection
    javax.faces.webapp.FacesServlet.service(FacesServlet.java:606)
    root cause
    javax.faces.el.EvaluationException: javax.persistence.PersistenceException: org.hibernate.exception.JDBCConnectionException: Could not open connection
    javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:102)
    com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
    javax.faces.component.UICommand.broadcast(UICommand.java:315)
    javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794)
    javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259)
    com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81)
    com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
    com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
    javax.faces.webapp.FacesServlet.service(FacesServlet.java:593)
    root cause
    javax.persistence.PersistenceException: org.hibernate.exception.JDBCConnectionException: Could not open connection
    org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1361)
    org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1289)
    org.hibernate.ejb.AbstractEntityManagerImpl.throwPersistenceException(AbstractEntityManagerImpl.java:1371)
    org.hibernate.ejb.TransactionImpl.begin(TransactionImpl.java:60)
    servlet.PrzychodniaBean.dodaj(PrzychodniaBean.java:30)
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    java.lang.reflect.Method.invoke(Unknown Source)
    org.apache.el.parser.AstValue.invoke(AstValue.java:262)
    org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:278)
    com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105)
    javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
    com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
    javax.faces.component.UICommand.broadcast(UICommand.java:315)
    javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794)
    javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259)
    com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81)
    com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
    com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
    javax.faces.webapp.FacesServlet.service(FacesServlet.java:593)
    root cause
    org.hibernate.exception.JDBCConnectionException: Could not open connection
    org.hibernate.exception.internal.SQLStateConversionDelegate.convert(SQLStateConversionDelegate.java:131)
    org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:47)
    org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:125)
    org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:110)
    org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.obtainConnection(LogicalConnectionImpl.java:304)
    org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.getConnection(LogicalConnectionImpl.java:169)
    org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction.doBegin(JdbcTransaction.java:67)
    org.hibernate.engine.transaction.spi.AbstractTransactionImpl.begin(AbstractTransactionImpl.java:160)
    org.hibernate.internal.SessionImpl.beginTransaction(SessionImpl.java:1263)
    org.hibernate.ejb.TransactionImpl.begin(TransactionImpl.java:57)
    servlet.PrzychodniaBean.dodaj(PrzychodniaBean.java:30)
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    java.lang.reflect.Method.invoke(Unknown Source)
    org.apache.el.parser.AstValue.invoke(AstValue.java:262)
    org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:278)
    com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105)
    javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
    com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
    javax.faces.component.UICommand.broadcast(UICommand.java:315)
    javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794)
    javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259)
    com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81)
    com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
    com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
    javax.faces.webapp.FacesServlet.service(FacesServlet.java:593)
    root cause
    java.sql.SQLException: No suitable driver found for jdbc:sqlserver://localhost;databaseName=MIS
    java.sql.DriverManager.getConnection(Unknown Source)
    java.sql.DriverManager.getConnection(Unknown Source)
    org.hibernate.service.jdbc.connections.internal.DriverManagerConnectionProviderImpl.getConnection(DriverManagerConnectionProviderImpl.java:173)
    org.hibernate.internal.AbstractSessionImpl$NonContextualJdbcConnectionAccess.obtainConnection(AbstractSessionImpl.java:276)
    org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.obtainConnection(LogicalConnectionImpl.java:297)
    org.hibernate.engine.jdbc.internal.LogicalConnectionImpl.getConnection(LogicalConnectionImpl.java:169)
    org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction.doBegin(JdbcTransaction.java:67)
    org.hibernate.engine.transaction.spi.AbstractTransactionImpl.begin(AbstractTransactionImpl.java:160)
    org.hibernate.internal.SessionImpl.beginTransaction(SessionImpl.java:1263)
    org.hibernate.ejb.TransactionImpl.begin(TransactionImpl.java:57)
    servlet.PrzychodniaBean.dodaj(PrzychodniaBean.java:30)
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    java.lang.reflect.Method.invoke(Unknown Source)
    org.apache.el.parser.AstValue.invoke(AstValue.java:262)
    org.apache.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:278)
    com.sun.faces.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:105)
    javax.faces.component.MethodBindingMethodExpressionAdapter.invoke(MethodBindingMethodExpressionAdapter.java:88)
    com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
    javax.faces.component.UICommand.broadcast(UICommand.java:315)
    javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:794)
    javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:1259)
    com.sun.faces.lifecycle.InvokeApplicationPhase.execute(InvokeApplicationPhase.java:81)
    com.sun.faces.lifecycle.Phase.doPhase(Phase.java:101)
    com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:118)
    javax.faces.webapp.FacesServlet.service(FacesServlet.java:593)
    note The full stack trace of the root cause is available in the JBoss Web/7.0.13.Final logs.
    persistance.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">
    <persistence-unit name="PrzychodnieLekarskiePU" transaction-type="RESOURCE_LOCAL">
    <class>model.Przychodznia</class>
    <properties>
    <property name="hibernate.connection.username" value="a"/>
    <property name="hibernate.connection.password" value="a"/>
    <property name="hibernate.connection.url" value="jdbc:sqlserver://localhost;databaseName=MIS"/>
    <property name="hibernate.connection.driver_class" value="com.microsoft.sqlserver.jdbc.SQLServerDriver"/>
    <property name="hibernate.dialect" value="org.hibernate.dialect.SQLServerDialect"/>
    <property name="javax.persistence.jdbc.url" value="jdbc:sqlserver://localhost;databaseName=MIS"/>
    <property name="javax.persistence.jdbc.user" value="a"/>
    <property name="javax.persistence.jdbc.password" value="a"/>
    <property name="javax.persistence.jdbc.driver" value="com.microsoft.sqlserver.jdbc.SQLServerDriver"/>
    </properties>
    </persistence-unit>
    </persistence>
    Edited by: 985713 on 2013-02-02 07:12
    Edited by: 985713 on 2013-02-02 07:37

    it works ok : I don't known where is error in jpa .. ?
    public class MyConnection {
         public static Connection getConnection () throws SQLException{
              String url = "jdbc:sqlserver://ABADDON1;databaseName=MIS";
              String user = "a";
              String pass = "a";
              DriverManager.registerDriver(new com.microsoft.sqlserver.jdbc.SQLServerDriver());
              Connection conn = DriverManager.getConnection(
                        url,user,pass);
              System.out.println("OK");;
              return conn;
    try {
                   conn = MyConnection.getConnection();
                   } catch (SQLException ex) {
                        System.out.println("Error: " + ex.getErrorCode()
                                  + ex.getMessage());
                   }

Maybe you are looking for