MS Sql server 2005 - Sa account locked out

hi Folks,
I'm trying to register a new datasource in cfadmin but I get
the following error, can anyone help?
Thankyou
java.sql.SQLException: [Macromedia][SQLServer JDBC
Driver][SQLServer]Login failed for user 'sa' because the account is
currently locked out. The system administrator can unlock it.
The root cause was that: java.sql.SQLException:
[Macromedia][SQLServer JDBC Driver][SQLServer]Login failed for user
'sa' because the account is currently locked out. The system
administrator can unlock it.

matthisco wrote:
> hi Folks,
>
> I'm trying to register a new datasource in cfadmin but I
get the following
> error, can anyone help?
>
> Thankyou
>
> java.sql.SQLException: [Macromedia][SQLServer JDBC
Driver][SQLServer]Login
> failed for user 'sa' because the account is currently
locked out. The system
> administrator can unlock it.
> The root cause was that: java.sql.SQLException:
[Macromedia][SQLServer JDBC
> Driver][SQLServer]Login failed for user 'sa' because the
account is currently
> locked out. The system administrator can unlock it.
http://www.google.com/search?hl=en&client=safari&rls=en&q=Login+failed+for+user+%27sa%27+b ecause+the+account+is+currently+&btnG=Search
==>
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=306429&SiteID=1
Please use google first.
Mack

Similar Messages

What windows account to use as proxy account to schedule a package to run in sql server 2005 job

I have successfully set up a credential and proxy in SQL Server 2005 to run a SSIS 2005 job under my windows account. The problem I got is the password of my account will expire sometime so the job execution will fail until I change the password
in the credential. I am thinking either to ask our IT administrator to set my account to password never expire or use a different account for the credential. I have very limited knowledge regarding windows security. So if I go the second option what account
should I use for the credential/proxy? I need to know about this before asking our IT admin.

It must be a domain wide service account (with a strong, non-expiring password), not a private account with just enough rights to run packages (this implies the account must be able to connect to remote data sources and shares). Oftentimes, such
an account also needs write access to the %temp% directory.
Arthur My Blog
Thanks. I will try to tell our admin see if it makes sense to him.

Getting data out of Oracle to SQL Server 2005

Hello,
I am new in Oracle and I have this question.
I need to transfer lots of data frequently at day from a large Oracle DB to a SQL Server 2005 Database.
Could you tell me what tools (including PL/SQL) ORACLE offers to reach this goal?
*.Dat files are still a way to perform this job or other method more performance (quickly and efficiently) are available?
Using MS SSIS is better ?
Thank for your help

I've done getting data out of Oracle to MS Access DB using heterogenous servicing.I hope that that would be the best way for your case too..
Check this out.
http://www.datadirect.com/developer/odbc/oracle_heterogeneous/index.ssp
Regards,
Bhagat

SQL 2012 DB Engine [Login failed: Account locked out] alerts not received from SCOM 2007 R2

Dear Experts,
In our SCOM 2007 R2 environment SQL 2012 DB Engine [Login failed: Account locked out] alerts not received but we are receiving the following alerts fr the DB instance.
1. Database Backup Failed To Complete
2. Login failed: Password expired
3. Log Backup Failed to Complete
4. Login failed: Password cannot be used at this time
5. Login failed: Password must be changed
6. IS Package Failed.
Why we are not receiving the "Login failed: Account locked out" ? Customers are asking the notification email alert for this Rule even I have checked the override settings everything is enabled by default same as above rules.
What can be the issue here ?
Thanks,
Saravana
Saravana Raja

Hi,
Could you please check the Windows security log for (MSSQLSERVER) event ID 18486? The rule should rely on this event.
Regards,
Yan Li
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Account locked out from RD server when no session is open?

Windows 2008R2 DCs, two in one site, one in another
Windows 2008 functional level
I've had two instances in the past week where users, several hours after changing their passwords, had their accounts locked out. I used LockoutStatus to track down the DC where the event 4740/lockout happened, and then read the calling workstation
from there. In both cases, the user didn't have any active or idle session on the remote desktop server where the lock was being generated. I checked further with Process Explorer and I couldn't even find any processes running in their user context.
I would unlock the account, and in under a minute, there would be six bad password attempts (our GP setting) and the account would be locked out. I could repeat this process indefinitely.
In both instances, when I rebooted the RD VM, the issue went away and didn't return. In one case that was somewhat disruptive as it was an application server. In the second case it was a domain controller and had no user impact.
I've seen this before when a user has an orphaned RD session idle for months, or with badly behaved applications, but this seeming dissociation from any active user process is really odd.
LockoutStatus always shows the lastPasswordSet timestamp in sync, replication occurs within fifteen minutes, and repadmin shows me both the expected topology and no errors.
I'm at a total loss. What more can I check for?

Hi,
Do you have any updates?
Other than Remote Desktop sessions, please also check these things below:
Programs, services, schedule tasks, scripts, which could also store user credentials.
More information for you:
Troubleshooting Account Lockout
http://technet.microsoft.com/en-us/library/cc773155(v=WS.10).aspx
Best Regards,
Amy

SQL Server 2005 replaced with SQL Server 2014 trying to connect front end Access as guest (read only ODBC)

We have replaced a SQL Server 2005 with a SQL Server 2014 (new physical server.) Have the new server set up to use SQL Server login OR Windows user login. Had old server connecting (for a particular DB) to front end Access (2010 or 2013) as guest for
anyone logged into the Windows NT Network with a read only ODBC connection. Have the DB in the new server set to include guest as db_datareader (with only SELECT permission for the securables of each table and view being linked) but when any Windows user not
specifically listed as a SQL DB user tries to use the front end they get an error of:
Microsoft SQL Server Login
Connection failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][OCBC SQL Server Driver][SQL Server] Login failed for user {domain\user}.
After closing that pop-up window a server login window appears. Of course, since the guest user is not specifically listed as a user in the DB that fails also. It seems like there should be a very simple solution to this, but I can't seem to find it. I want
to allow anyone logged in on the Windows system (locally) to be able to open the MS Access file (on their work station machine) and run their own (read only; select) queries on the SQL Server database. Any suggestions?
Thanks a billion in advance ----

Thanks for the response Olaf. I have now spent weeks researching this. I realize that using the guest account in most situations is not advised. As mentioned, I have restricted the guest account to allow the db_datareader role only, and have explicitly denied
all other roles, as well as allowing select only, and still have no access for the guest account.
The suggested fix in the second link you provided, of using Windows groups is not plausible for my situation either. We are a scientific field research institution, with a few long term users and lots of users that may have Windows accounts for a few months,
and then they are gone. It would be a nightmare for the network tech to try to keep a group account up to date, and we need to give access (read only, of course) to anyone logged into the system. Realize that the ONLY access of any kind to this database is
thru MS Access ACCDB, using a (by default) read only OCDB connection.
This type of access is used particularly because researchers need to be able to set up their own queries, and the MS Access query interface is particularly convenient for people who are not themselves SQL experts, yet are trying to get some very advanced
levels of output. Putting the database online is not practical because then we are back to the need for a comprehensive query interface, and just picking up general subsets of the data online (from a basic web page search feature) would be out of the question,
since the result set would involve hundreds of thousands if not millions of records.
So - that said - what exactly would you suggest, assuming we don't have the funds to buy a whole new system, and have spent plenty of money with Microsoft's Enterprise level MS Office so that all work stations have MS Access, and Microsoft's SQL Server,
as well as running our network on Microsoft's network software.

SQL Server 2005 SP2 install on Vista

Hi,
I have all updates for Vista, tried to install SQL Server 2005 SP2, the following log file:
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version      : Professional (Build 6000)
Time            : Wed Mar 26 12:20:54 2008
USER-PC : To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.
Machine         : USER-PC
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLSupport_1.log
Machine         : USER-PC
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLNCLI_1.log
Machine         : USER-PC
Product         : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SqlWriter_1.log
Machine         : USER-PC
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLSupport_2.log
Machine         : USER-PC
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLNCLI_2.log
Machine         : USER-PC
Product         : Microsoft SQL Server 2005 Express Edition
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQL.log
Machine         : USER-PC
Product         : Workstation Components, Books Online and Development Tools
Warning         : Warning 28123.Warning: SQL Server Setup cannot install this feature because a different edition of this feature is already installed. For more information, see 'Version and Edition Upgrades' in SQL Server Books Online.
Machine         : USER-PC
Product         : Microsoft SQL Server 2005 Tools Express Edition
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_Tools.log
Setup succeeded with the installation, inspect the log file completely for status on all the components.
Time            : Wed Mar 26 12:23:51 2008
==============================================================
When I try to start SQL Server it times out. SQL Server Express is running ok.
Can you help me get this started?
Thank you,
Lucy

This is the previous errorlog:
2008-04-09 11:47:06.27 Server      Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
Mar 23 2007 16:28:52
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Evaluation Edition on Windows NT 6.0 (Build 6000: )
2008-04-09 11:47:06.27 Server      (c) 2005 Microsoft Corporation.
2008-04-09 11:47:06.27 Server      All rights reserved.
2008-04-09 11:47:06.27 Server      Server process ID is 240.
2008-04-09 11:47:06.27 Server      Authentication mode is WINDOWS-ONLY.
2008-04-09 11:47:06.27 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2008-04-09 11:47:06.27 Server      This instance of SQL Server last reported using a process ID of 4180 at 4/5/2008 11:17:36 AM (local) 4/5/2008 6:17:36 PM (UTC). This is an informational message only; no user action is required.
2008-04-09 11:47:06.27 Server      Registry startup parameters:
2008-04-09 11:47:06.27 Server      -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2008-04-09 11:47:06.27 Server      -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2008-04-09 11:47:06.27 Server      -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2008-04-09 11:47:06.32 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2008-04-09 11:47:06.32 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2008-04-09 11:47:06.50 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.
2008-04-09 11:47:06.55 Server      Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2008-04-09 11:47:06.64 Server      The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted. If you would like distributed transaction functionality, please start this service.
2008-04-09 11:47:06.64 Server      Database mirroring has been enabled on this instance of SQL Server.
2008-04-09 11:47:06.64 spid4s      Starting up database 'master'.
2008-04-09 11:47:06.80 spid4s      4 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:06.82 spid4s      0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:06.82 spid4s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2008-04-09 11:47:07.06 spid4s      SQL Trace ID 1 was started by login "sa".
2008-04-09 11:47:07.10 spid4s      Starting up database 'mssqlsystemresource'.
2008-04-09 11:47:07.13 spid4s      The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
2008-04-09 11:47:07.34 spid4s      Server name is 'USER-PC'. This is an informational message only. No user action is required.
2008-04-09 11:47:07.34 spid9s      Starting up database 'model'.
2008-04-09 11:47:07.53 spid9s      Clearing tempdb database.
2008-04-09 11:47:08.11 Server      A self-generated certificate was successfully loaded for encryption.
2008-04-09 11:47:08.11 Server      Server is listening on [ 'any' <ipv6> 1433].
2008-04-09 11:47:08.11 Server      Server is listening on [ 'any' <ipv4> 1433].
2008-04-09 11:47:08.17 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2008-04-09 11:47:08.17 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
2008-04-09 11:47:08.17 Server      Server is listening on [ ::1 <ipv6> 1434].
2008-04-09 11:47:09.12 spid9s      Starting up database 'tempdb'.
2008-04-09 11:47:09.47 spid12s     The Service Broker protocol transport is disabled or not configured.
2008-04-09 11:47:09.47 spid12s     The Database Mirroring protocol transport is disabled or not configured.
2008-04-09 11:47:09.53 spid12s     Service Broker manager has started.
2008-04-09 11:51:06.92 Server      CPU time stamp frequency has changed from 1662000 to 199683 ticks per millisecond. The new frequency will be used.
2008-04-09 11:55:07.29 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 11:55:07.29 Server      CPU time stamp frequency has changed from 199683 to 136029 ticks per millisecond. The new frequency will be used.
2008-04-09 12:23:09.84 Server      CPU time stamp frequency has changed from 136029 to 586928 ticks per millisecond. The new frequency will be used.
2008-04-09 12:59:13.12 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 13:07:13.85 Server      CPU time stamp frequency has changed from 586928 to 824822 ticks per millisecond. The new frequency will be used.
2008-04-09 13:47:17.50 Server      CPU time stamp frequency has changed from 824822 to 140502 ticks per millisecond. The new frequency will be used.
2008-04-09 14:07:19.33 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 15:07:24.80 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 15:11:25.16 Server      CPU time stamp frequency has changed from 140502 to 1413355 ticks per millisecond. The new frequency will be used.
2008-04-09 15:15:25.53 Server      CPU time stamp frequency has changed from 1413355 to 161989 ticks per millisecond. The new frequency will be used.
2008-04-09 15:19:25.89 Server      CPU time stamp frequency has changed from 161989 to 134822 ticks per millisecond. The new frequency will be used.
2008-04-09 16:23:31.73 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 17:23:37.20 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 18:11:41.58 Server      CPU time stamp frequency has changed from 134822 to 154257 ticks per millisecond. The new frequency will be used.
2008-04-09 18:23:42.67 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 18:23:42.67 Server      CPU time stamp frequency has changed from 154257 to 134721 ticks per millisecond. The new frequency will be used.
2008-04-09 18:35:43.79 Server      CPU time stamp frequency has changed from 134721 to 151448 ticks per millisecond. The new frequency will be used.
2008-04-09 18:43:44.51 Server      CPU time stamp frequency has changed from 151448 to 125134 ticks per millisecond. The new frequency will be used.
2008-04-09 19:15:47.35 Server      CPU time stamp frequency has changed from 125134 to 182297 ticks per millisecond. The new frequency will be used.
2008-04-09 19:23:48.08 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 19:27:48.45 Server      CPU time stamp frequency has changed from 182297 to 120770 ticks per millisecond. The new frequency will be used.
2008-04-09 19:47:50.27 Server      CPU time stamp frequency has changed from 120770 to 1370171 ticks per millisecond. The new frequency will be used.
2008-04-09 20:07:52.10 Server      CPU time stamp frequency has changed from 1370171 to 106932 ticks per millisecond. The new frequency will be used.
2008-04-09 20:23:53.56 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2008-04-09 20:35:54.65 Server      CPU time stamp frequency has changed from 106932 to 88924 ticks per millisecond. The new frequency will be used.
2008-04-09 20:51:56.11 Server      CPU time stamp frequency has changed from 88924 to 102106 ticks per millisecond. The new frequency will be used.
2008-04-09 20:59:56.84 Server      CPU time stamp frequency has changed from 102106 to 118592 ticks per millisecond. The new frequency will be used.

SQL Server 2005 Vista Problems

I have 3 databases in SQL Server 2005 that I want to connect
to. Everything works fine in XP, but when I try to set it up on
Vista I get all sorts of problems. All software is latest version
with all available updates installed.
After restarting the Vista computer, the first database I
select in CF administrator connects successfully, but the other two
return Connection Reset error. It doesn't matter which of the 3 I
select, just the first one connects.
However, whichever one it is that CF confirmed was
successful, when accessed from a CF page also returns Connection
Reset error.
The security settings in SQL Server are the same for each
database.
Anyone got any idea how to solve this problem??
Doug

The one that was connecting was connecting to port 1434. I
have now locked it down and only port 1433 is available. Now I get
the same error every time I try to make a connection:
Error establishing socket. Connection refused: connect
Apart from the port number (which was not 1433 on my old XP
computer) everything else is identical.
Is there some setting in Vista out of the box that has to be
changed to get CF to connect to SQL Server 2005?
Doug

How to calculate the HFM Cube size in SQL Server-2005

Hi
How to calculate the HFM Cube size in SQL Server-2005 ?
Below query used for Oracle. Then what is query for SQL Server?
SQL> select sum(bytes/1024/1024) from dba_segments where segment_name like 'FINANCIAL_%' and owner='HFM';
SUM(BYTES/1024/1024)
SQL> select sum(bytes/1024/1024) from dba_segments where segment_name like 'HSV FINANCIAL%' and owner='HFM';
SUM(BYTES/1024/1024)
Regards
Smilee

What is your objective? The subcube in HFM is a concept which applies to the application tier - not so much to the database tier. The size of the subcube is the unique number of data strips (data values for January - December inclusive, for example) for the given entity, currency triplet or Parent.Child node. You have to account for parent accounts and customs which don't exist in the database but are generated in RAM in the application tier.
So, if your objective is to find the largest subcubes, you could do this by querying the database and counting the number of records per entity/value (DCE tables) or parent.child entity combination (DCN tables). I'm not versed in SQL, but I think the script below would just tell you the schema size and not the subcube sizes.
Check out Accelatis.com for a third party software product that can do this for you. The feature is called the Subcube Analyzer and was written by the same team that wrote HFM, so they ought to know how this works :-)
--chris

Creating MS SQL Server 2005 Analysis Services OLAP connection

Hello,
I am trying to add an OLAP data source in BI Publisher (which is part of the OBIEE 11.1.1.5.0 suite I have installed). However, the connection never seems to create - I don't get an error or a success message when I test the connection. However, if I cancel out of the create connection screen, I get this error: "Your request was denied as you have no permission to access the data.". This is odd since the credentials I am using have admin rights to the OLAP cube I am attempting to connect to.
SETUP
OBIEE 11.1.1.5.0 x86_64 bit Linux
MS SQL Server 2005 Analysis Services running on Windows Server Enterprise (32 bit) 2007 SP2
Windows users are able to connect to the Windows/SQL server via Excel 2007 and its built-in Analysis Services "Other Data Sources" option. Authentication is done via Windows Active Directory LDAP
QUESTIONS
1) In the BI Publisher connection screen, can I enter my AD username/password, or because I am connecting from a Linux Server, do I need to authenticate via a different method?
2) In the connection string, the initial catalog I am attempting to connect to has spaces in its name. Could this be an issue?
3) Given the "no permission to access data" message I am getting, is it possible I am reaching the SQL Server but need to set up a local database, non-AD account to access the OLAP catalog?
4) Are there any logs in the OBIEE server that I can check for more details?
Thanks!

Post Author: Sam Naghshineh
CA Forum: Olap
With the new productivity pack for Business Objects Enterprise XI R2 (Service Pack 2) you can access SSAS 2005 through the new OLAP tool called Voyager. The productivity pack is due out sometime in the next few weeks.
Hope this helps.

Weblogic 8.1 SP4 & SQL Server 2005 - Moving to Prod - Will we have issues?

Ok,
Can't track down our account holder this afternoon to create a case, so i'll just throw it out there for now.
Our whole system is running swimmingly on SP4 with BEA SQL Server Driver connecting to SQL Server 2005 (9.0.3042).
Its been through QA, now its in the training environment...
Pool Config
<JDBCConnectionPool
DriverName="weblogic.jdbc.sqlserver.SQLServerDriver"
Name="myPool" PasswordEncrypted="{3DES}jkjkjkj/GFg="
Properties="user=XXXXXX;*SendStringParametersAsUnicode*=false;*portNumber*=1433;*databaseName*=XXXXXXXXXX_mo;*serverName*=XXXXXXXXXXX"
Targets="xxxxxxxx" TestConnectionsOnCreate="true"
TestConnectionsOnRelease="true" TestConnectionsOnReserve="true"
TestTableName="SQL SELECT 1" URL="jdbc:bea:sqlserver://XXXXXXXXXXXXXX:1433"/>
I see alot of posts about people using 2005 on SP6, and there is even a patch out there to go ontop of that....
[http://commerce.bea.com/d2d/wlplat81sp6_sqlserver2005_patch.jsp]
And in the official docs it says 2005 is only supported in SP6.
[http://edocs.beasys.com/wls/docs81/jdbc_drivers/mssqlserver.html#1074559]
We are using the standard non-XA version of the drivers.
So my questions are
* Why is it working on SP4?
* Do i need to worry about it moving to production using SP4?
Thanks
Mike

Hi. We don't update docs well... You should have zero problems. I might
recommend contacting official support to get the latest version of our
JDBC driver package, but it may not be necessary.
Joe

Unable to connect SQL server 2005 databse with JSF applications !

Hello guys!
Help me out to connect SQL server 2005 Databse with JSF applications using JDBC-ODBC bridge. I'm working with Netbeans 6.1 IDE.
I tried for the basic applications but instead got this error:
"unable to deploy jdbc drivers to the <project>domain/lib"
Please help me out with working sample codes that connects MS SQL server 2005 DB with JSF!!
Thank you guys!

1) don't use the bridge driver
2) don't do database access from JSF
3) learn how to use your application server
4) learn how to use your IDE

How can I login to my MS SQL Server 2005 if I forgot my login password

Hi,
I am using SQL Server 2005 at home.
My problem is I forgot my password to log in to my server.
I only remember user name is 'sa'.
I haven't used it for two to three months. So I forgot password.
Previously, When I used sql server 2000, my login is as windows login. so no problem.
But this time, I set seperate log in and I got this problem.
Any help will be appreciated.
Thanks
George

I hope the following article will help: http://blogs.msdn.com/raulga/archive/2007/07/12/disaster-recovery-what-to-do-when-the-sa-account-password-is-lost-in-sql-server-2005.aspx
Please let us know if you have any further problems or questions.
Thanks,
-Raul Garcia
SDE/T
SQL Server Engine

Error while installing SQL Server 2005 SP3

I have installed SQL Server 2005 Standand Edition (32-bit) on a standalone server machine running
Windows Server 2003 R2 Standard 64-bit with Service Pack 2. After installing SQL Server, when I tried installing the Service Pack 3 (as per application requirement) through local administrator account, I am repeatedly getting below error in
"C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB955706_SqlSupport.msi.log"
SECUREREPAIR: SecureRepair Failed. Error code: 4ec4E6A3388
MSI (s) (F8:40) [16:49:33:515]:
Error 1260. Windows cannot open this program because it has been prevented by a software restriction policy.
I have checked rights on the folders and also got the anti-virus (symantec) services stopped on the server. Still no success, can anyone help.

I have installed SQL Server 2005 Standand Edition (32-bit) on a standalone server machine running
Windows Server 2003 R2 Standard 64-bit with Service Pack 2. After installing SQL Server, when I tried installing the Service Pack 3 (as per application requirement) through local administrator account, I am repeatedly getting below error in
"C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Redist9_Hotfix_KB955706_SqlSupport.msi.log"
SECUREREPAIR: SecureRepair Failed. Error code: 4ec4E6A3388
MSI (s) (F8:40) [16:49:33:515]:
Error 1260. Windows cannot open this program because it has been prevented by a software restriction policy.
I have checked rights on the folders and also got the anti-virus (symantec) services stopped on the server. Still no success, can anyone help.
Just to add: Have already referred
http://support.microsoft.com/kb/918357

Error when creating a FDM application on SQL Server 2005

Hi,
we are getting this error when creating a FDM application on SQL Server 2005
Error: EPMCSS-07003: Failed to validate identity. Invalid identity . Check identity.[SET_ROLES_LIST]
We are using Windows System Integration although we have also tested with sa user.
Any ideas?
Thanks

Based on the error message it appears to be having a Shared Services issue. Verify that the "ADMIN" account is being used for the HSS connection and that you are using "ADMIN" to create the application and see if the same error is returned.

MS Sql server 2005 - Sa account locked out

Similar Messages

Maybe you are looking for