Hi,
I have a DB which has its collation set to SQL_Latin1_General_CP1_CI_AS and i need to change it to Latin1_General_CI_AS,
does anyone have any idea how to do this?
i have tried right clicking on the DB and changing its collation in the options tab, but this only changes what the default is, so all the old columns still have the old collatin,
does anyone know how to change this?
Hello,
I've restored a SQL Server 2000 database with a Latin1_General_BIN collation from a .dmp file to a SQL Server 2005 server with a default collation of SQL_Latin1_General_CP1_CI_AS. When I try to change the database collation I get hundreds of the following error:
The object 'CK_PM10200_GLPOSTD_00AF8CF' is dependent on database collation. So, in this case, is it even possible to change the collation if there are objects in the database that are dependent on it?
Thanks,
Bruce
Hi,
Im creating a new named instance in SQL2005 , by default the instance created with Latin1_General_CI_AS? collation.
I want to change this collation to SQL_Latin1_General_CP1_CI_AS?, but sincerely I dont have a clue how to select it on the collation setting window :
http://img443.imageshack.us/my.php?image=collationyc2.gif
thanks for your help.
I need to change the default collation of all dbs on all my servers to SQL_Latin1_General_CP1_CI_AI from SQL_Latin1_General_CP1_CI_AS. We need to do compares and sorts and want to ignore accents -- something that wasn't clear when we built the servers. I know this has to do with "re-building databases" -- maybe even including the master -- but I'm not certain exactly what this means. Thanks!
View 1 Replies View RelatedHi.
I don't know how to change the collation in SQL Server 2000, my collation is Modern_Spanish_CI_AS, if somedoby knows the procedure to change the collation I would be thankful.
Thank you again and best regards.
Christian
Is it possible to change the collation of your instance?
As far as I know it is not possible to change the collation once SQL Server has been installed.
When I said that SQL needs to be reinstalled at work the guys sent me this link: [URL]....
I ran it exactly like that but the collation didn't change.
I have also restarted the services but the collation is still the same.
Am I running this code wrong or am I right about not being able to change the collation after installation?
Hello...
When I migrated data from one SQL Server to another I got collection problems because collation of the target server was different from the source one.
The best solution I thought about was to change collation of the database in target server to be equal to the server collation so that when a temporary table is created, and the collation used would be the server collation, no error would occur. All sounds logic, but, after I ran ALTER DATABASE command and changed the collation of the database, I verified that all varchar fields of all database tables retained the old collation, not the new database collation I set.
Is there any way to change the collation of all fields at once when I change the database collation?
Thanks for your help
Jaime
Hi!
I have a database in SQL Server 2005 Express edition in standard collation. And now I need to store data including letter "è" (I'm from Slovenia). Can please someone tell me how to change the collation in server and database, please?
Thanks in advanced,
d
Hi there,
We currently install some of client's databases on SQL Server 2000 with the collation set to Latin1_General_BIN but we have one client that was installed and now running on SQL_Latin1_General_CP1_CI_AS and I was wondering if we can change the collation on the database to Latin1_General_BIN?
Would this have any adverse affects on the DB or the data within it? Our strings are nvarchar.
Thanks for your help
I support an applicatoin where the vendor requires the use of the LATIN_1_GENERAL_BIN sort collation in their user databases. Origionally, when I installed the instance, I did not select this sort collation for the instance. I have since gone back and reinstalled SQL Server with the correct sort collation. After that, I restored the vendors databases from backups I took prior to reinstalling the instnace and they retained the LATIN_1_GENERAL_BIN collation (the correct one).
I also restored the MSDB database to get all of my jobs back. When I did this, MSDB took the old sort collation (SQL_LATIN_1_GENERAL_CPI_CI_AS). MSDB is the only database that has this collation and I'm getting errors in the agent log complaining of collation conflicts. I'm pretty sure the fact that the MSDB sort collation is different that all the other databases is the thing that's causing these error messages.
My question is this: Is there any way to change the sort collation of MSDB without reinstalling SQL server? This is a clustered environment and everytime I've reloaded SQL, it's been cumbersome and taken me at least 1 day's work.
Also, I know there's a rebuild master utility that will rebuild master, model and MSDB, but when I tried that last time it failed and I had to reinstall SQL anyway. Does anyone know of a way around this or have any tips on using the rebuildmaster utility in a clustered environment?
Many thanks,
I am trying to change the name collation of a SQL database as an update script I am running needs the main collation to be SQL_Latin1_General_CP1_CI_AS
I have tried going into Properties and options then changing the collation type but I get this error
"The Database could not be exclusively locked to perform the operation. ALTER DATABASE failed. The default collation of database 'nutri93' cannot be set to SQL_Latin1_General_CP1_CI_AS."
I have tried SQL scripts that I have found to take the database into a single user mode but still get the same errror.
Usually its this Database nutri93 could not be locked exclusively
How I can change the collation type? Currently the only option seems to be a complete hard install of SQL Management Studio
i would like to change all my dbs to have the same collation, i wasnt involved in the creation of these dbs and therefor cant judge if this will be a dangrous thing to do... but itll help to change when performing queries, arre there any dangers in doing this?
View 3 Replies View RelatedI currently have a server with the collation set to SQL_Latin1_General_CP1_CI_AS.
However, some of the databases within the server are set to Latin1_General_BIN, probably because they were restored from another server some time ago. Also, even within the databases that have Latin1_General_BIN, some of the columns are set to SQL_Latin1_General_CP1_CI_AS, very confusing to say the least.
What i would like to do is change the database collation settings for these databases to match the server setting. I would also like to change all of the tables within these databases to have the columns also set to the server collation settings.
I'm looking for the steps that i would need to take to make sure i don't mess anything up as these databases have there own sets of views and sp's that run each day.
Hi,I'm installing SQL2000 on a new cluster server.I selected a 'custom installation' and was presented with a'Collation settings' screen.I need it to be SQL_Latin1_General_CP1_CI_AS collationas I will be restoring databases with this collation.What should I choose from the 'Collation designator' and 'SQLCollations' box.Is it 'Dictionary order, case-insensitive, for use with 1252characters'?What will be the default? Will it be the same default as for the'typical' installation?Thanks
View 1 Replies View RelatedI'm importing data from a table on one database into a table in another database on the same instance. The FROM database is collated as "Latin1_General_CI_AS" and the TO database is collated as "SQL_Latin1_General_CP1_CI_AS".
When I then try joining on a common nvarchar column between the 2 tables, I get this error:
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Latin1_General_CI_AS" in the equal to operation.
Is there a way to change the collation of the incoming data as I'm inserting it into the TO table?
Can someone plz help me, how can i change the collation of an existing database?
Thank you in advnace
Thank you very much for your reply. I have one more question about collation. In my production server we have SQL_Latin1_General_CP1_CI_AS and on other server (from where i want to move database to prod server) the collation is Latin1_General_CI_AI . can i move the database form one server to another even if they have different collation. The both servers are sql server 2005 and the production server is standard edition and the other server is developer edition. I wanted to move the databases from developer edition. Could some body help me with this. Thank you very much.
Dear Members..
I am facing a problem with SQL server 2005 Secc. I have a Server with server collation Arabic_CI_AS. And i have a databse in it which has a collation SQL_Latin1_General_CP1256_CI_AS. The issue started with me when i am trying to create a Integrated seccuroty for some users in my firm. I have created a DatabaseRoll for in the database. There is no problem while creating it. I have added the user in the seccurity login on the server and then i added these users in the database Seccurity users. After that i applied the created roll to that users. It being created perfectly. But the issue is coming when i want to modify the seccurity policy (Seccurables) of any user from the database.
(Properties of Users --> Seccurables )
Its showing an error. as follows
------------------------------
Failed to retrieve data for this request. (Microsoft.SqlServer.Express.SmoEnum)
------------------------------
ADDITIONAL INFORMATION:
urn could not be resolved at level DatabaseRole.
------------------------------
I am not understanding why its coming with this situation.
==========================================================
Also sometimes its showing an error when i am trying to see the login prperties of that user in the database logins.
Server--> Seccurity --> Logins --> Properties --> Seccurables -->Err.
As follows
------------------------------------------
Failed to retrieve data for this request. (Microsoft.SqlServer.Express.SmoEnum)
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)
------------------------------
Cannot resolve the collation conflict between "SQL_Latin1_General_CP1_CI_AS" and "Arabic_CI_AS" in the UNION operation. (Microsoft SQL Server, Error: 468)
------------------------------
Hope some body can help me in this....
Thanks in Advance....
we have a problem with the collation of databases between sql server 7.0 and SQL SERVER 2005. The message that pops up is next:
"Mensagge. 468, level 16, state 9, Line 1
Problem of collation can not be solved between "Compatibility_52_c0a_30001" and "SQL_Latin1_General_CP1_CI_AS of UNION command.
Te script is lanch from sqlserver 2005, and it doesn´t work with UNION command but it works if you lanch them separately.
A few collation questions on SQL Server 2005 SP2, which I'll call SQLS.The default collation for SQLS is apparently SQL_Latin1_General_CP1_CI_AS.I wish to use a variation of this, SQL_Latin1_General_CP1_CS_AIcollation, but there is no such collation returned fromfn_helpcollations(). Also, if I try to use this collation ina CREATE DATABASE stmt, SQLS yells about it.I see that there is a Latin1_General_CS_AI. What effects are therein using this collation? The SQL_* collations are SQL collations,while non-SQL_* collations are Windows collations, yes? SQLS runsonly on Windows, so am I safe in using Latin1_General_CS_AI? Whatdoes the CP1 in the SQL collation signify? Am I asking for trouble?------------------------------------Assuming that I set Latin1_General_CS_AI (or any other case-sensitivecollation) at the database level, I believe my DDL/DML for that databasealso becomes case-sensitive. How can I specify that I want ONLY my dataaccess to be case-sensitive, and not my DDL/DML? I don't want to haveto remember to type "select * from MyCamelCase" when "mycamelcase"should work.Any help appreciated.A new SQLS DBA..aj
View 3 Replies View RelatedPls, any one help me regarding the how to change the collation name of the server in SQL server 2005.
In SQL server 2000 we can do with rebuildm.exe, like that is there any one.
Thanks in advance
Hello All-
Our production sql 2000 systems have collation setting as "SQL_Latin1_General_CP1_CI_AS". The new production db server[sql 2005] has been installed and configured with "SQL_Latin1_General_CP1_CI_AS" collation.
The issue is with the dev est servers. A few of them has been configured with collation "Latin1_General_CI_AS". Recently I have noticed a string comparison failed with collation related message due to the serverdb collation difference.
I have not come across any specific collation recommendation from Microsoft. Are there any specific recommendations from Msft on collation? I can forsee issues, if we have to perform any testsany feautre development on a production copy in dev est environments which involves string comparisons.
This issue is more important since we are on a Migration path which involves large some number of servers in dev est environments. My recommendation to the team at our place was to rebuild the already configured servers which has "Latin1_General_CI_AS" collation and change the server collation to "SQL_Latin1_General_CP1_CI_AS".
I would really appreciate if you could share your thoughts on this issue.
TIA,
Mkumar
Hello All-
Our production sql 2000 systems have collation setting as "SQL_Latin1_General_CP1_CI_AS". The new production db server[sql 2005] has been installed and configured with "SQL_Latin1_General_CP1_CI_AS" collation.
The issue is with the dev est servers. A few of them has been configured with collation "Latin1_General_CI_AS". Recently I have noticed a string comparison failed with collation related message due to the serverdb collation difference.
I have not come across any specific collation recommendation from Microsoft. Are there any specific recommendations from Msft on collation? I can forsee issues, if we have to perform any testsany feautre development on a production copy in dev est environments which involves string comparisons.
This issue is more important since we are on a Migration path which involves large some number of servers in dev est environments. My recommendation to the team at our place was to rebuild the already configured servers which has "Latin1_General_CI_AS" collation and change the server collation to "SQL_Latin1_General_CP1_CI_AS".
I would really appreciate if you could share your thoughts on this issue.
TIA,
Mkumar
Hi,
I'm installing SQL Server 2005 on windows 2003 R2.
Which Collation Designator is to be used so that the both English as well as Arabic characters can be stored simultaneously...?
That is "The collation settings designator which support both Arabic as well as English character set"...
Thanks,
Vivek
Scenario
Recently moved a SQL2000 database to SQL2005.
Collation on SQL 2000 database server was SQL_Latin1_General_CP1_CI_AS
Colaltion on SQL 2005 database server is Latin1_General_CI_AS
After restoring the SQL 2000 database on SQL 2005 we observed that the database collation was SQL_Latin1_General_CP1_CI_AS. We have altered the database collation to Latin1_General_CI_AS. We understand this will work for all new objects created on the database but existing objects (prior to the collation change) will continue to have the 'SQL_Latin1_General_CP1_CI_AS' collation.
What is the best method to change the collation of the older columns to 'Latin1_General_CI_AS' -
1) Run ALTER TABLE ALTER COLUMN <colname> <datatype> COLLATE Latin1_General_CI_AS <nullability>
on each varchar/char column
or
2) For each table
BCP out data
DROP TABLE
RECREATE TABLE (taking the new collation Latin1_General_CI_AS)
BCP in data
3) Other methods?
Thanks in advance
David.
Hi ,
We want to install 2 applications that run on SQL server 2005 but the requirement of database installation are different Collation setting ( One require Dictionary order, case-insensitive, for use with 1252 Character Set and other require Dictionary order, case-sensitive, for use with the 437 (US English) Character set).
So the question here could I install both two applications successfully on same platform ? and if yes how?
Thanks and regards,
Quinh
I need a SQL Server 2005 SP2 instance with a collation of SQL_Latin1_General_CP850_BIN2. After installing SP2, the collation is SQL_Latin1_General_CP850_BIN, and none of the patches I can find seem to want to work (they are all apparently written for SQL Server 2000).
Any assistance is greatly appreciated.
I have just upgraded to SQL Server 2005 from SQL Server 2000.In Microsoft SQL Server Management Studio, when I click on databaseproperties, I receive the following error:-Cannot resolve the collation conflict between"Latin1_General_CI_AS"and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.(Microsoft SQL Server, Error: 468)Some reference suggest that I can change the database collation byclicking database properties!What can I do?
View 21 Replies View RelatedI am using SQL Server 2008. In ServerProperty function, there are two properties called âCollationâ and âCollationIDâ. In some cases, I will only know the CollationID. Is it possible get the collation name from the CollationID? Is there a function called CollationNameFromID?
View 1 Replies View RelatedHow do you change the SA password in SQL Server 2005?
Thanks.
Doug
When I change the tcp/ip port to anything other than 1433 my SSIS nor DTS packages run successfully. Does the tcp/ip port have to be on 1433 for the SSIS or DTS packages to run successfully?
View 3 Replies View RelatedI have SQL Server 2005 installed on a machine that was recently upgraded to SP2 (build 3042). The server never had the replication feature installed on it. I attempt to add replication to it and I get an error because (I think) I am installing from the initial version media (CD-ROM, build 1399) and the setup appears to want an MSI file for SP2. Any help is appreciated.
I followed the exact procedures in online help How to: Change Components in an Existing Instance of SQL Server 2005 (Setup), but after I get the Ready to Update page, I get the error box:
An installation package for the product Microsoft SQL Server 2005 cannot be found. Try the installation again using a valid copy of the installation package SqlRun_SQL.msi.
Here is a partial output of the SQLSetupxxxx_ComputerName_Core.log file:
Action 17:44:25: ResolveSource.
Action start 17:44:25: ResolveSource.
MSI (c) (E4!D4) [17:44:25:200]: Resolving source.
MSI (c) (E4!D4) [17:44:25:200]: User policy value 'SearchOrder' is 'nmu'
MSI (c) (E4!D4) [17:44:25:200]: User policy value 'DisableMedia' is 0
MSI (c) (E4!D4) [17:44:25:200]: Machine policy value 'AllowLockdownMedia' is 0
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Media enabled only if package is safe.
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Looking for sourcelist for product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Adding {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}; to potential sourcelist list (pcode;disk;relpath).
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Now checking product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Media is enabled for product.
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Processing net source list.
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNNet 3: 2
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Processing media source list.
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Trying media source H:ServersSetup.
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 2203 2: H:ServersSetupSqlRun_SQL.msi 3: -2147287037
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi
MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Processing URL source list.
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNURL 3: 2
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi
MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: 3: SqlRun_SQL.msi
MSI (c) (E4:7C) [17:44:25:200]: User policy value 'SearchOrder' is 'nmu'
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Media enabled only if package is safe.
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Prompting user for a valid source.
MSI (c) (E4:7C) [17:44:25:200]: Machine policy value 'DisableBrowse' is 0
MSI (c) (E4:7C) [17:44:25:200]: Machine policy value 'AllowLockdownBrowse' is 0
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Browsing is enabled.
MSI (c) (E4:7C) [17:44:25:200]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Now checking product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Media is enabled for product.
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Processing net source list.
MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNNet 3: 2
MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Processing media source list.
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Trying media source SQLSTDSEL;.
MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: 3: SqlRun_SQL.msi
MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Processing URL source list.
MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNURL 3: 2
MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi
MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: 3: SqlRun_SQL.msi
MSI (c) (E4:7C) [17:44:44:388]: SOURCEMGMT: Trying source H:SetupSqlRun_SQL.msi.
MSI (c) (E4:7C) [17:44:44:388]: Cloaking enabled.
MSI (c) (E4:7C) [17:44:44:388]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (E4:7C) [17:44:44:403]: SOURCEMGMT: Resolved source to: 'H:Setup'
MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Now checking product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Media is enabled for product.
MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (c) (E4!D4) [17:44:44:403]: Note: 1: 1706 2: 3: SqlRun_SQL.msi
MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Failed to resolve source
MSI (c) (E4!D4) [17:44:44:419]: Transforming table Error.
MSI (c) (E4!D4) [17:44:44:419]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4!D4) [17:44:44:435]: Transforming table Error.
MSI (c) (E4!D4) [17:44:44:435]: Transforming table Error.
MSI (c) (E4!D4) [17:44:44:435]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4!D4) [17:44:44:435]: Transforming table Error.
MSI (c) (E4!D4) [17:44:44:435]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4!D4) [17:44:44:435]: Transforming table Error.
MSI (c) (E4!D4) [17:44:44:435]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4:7C) [17:44:44:435]: Transforming table Binary.
MSI (c) (E4:7C) [17:44:44:435]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (E4:7C) [17:44:44:450]: Transforming table Binary.
MSI (c) (E4:7C) [17:44:44:450]: Transforming table Binary.
MSI (c) (E4:7C) [17:44:44:450]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (E4:7C) [17:44:44:450]: Transforming table Binary.
MSI (c) (E4:7C) [17:44:44:450]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (E4:7C) [17:44:44:450]: Transforming table Binary.
MSI (c) (E4:7C) [17:44:44:450]: Note: 1: 2262 2: Binary 3: -2147287038
Error 1706. An installation package for the product Microsoft SQL Server 2005 cannot be found. Try the installation again using a valid copy of the installation package 'SqlRun_SQL.msi'.
MSI (c) (E4!D4) [17:45:02:731]: Transforming table Error.
MSI (c) (E4!D4) [17:45:02:731]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4!D4) [17:45:02:747]: Transforming table Error.
MSI (c) (E4!D4) [17:45:02:747]: Transforming table Error.
MSI (c) (E4!D4) [17:45:02:747]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4!D4) [17:45:02:747]: Transforming table Error.
MSI (c) (E4!D4) [17:45:02:747]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4!D4) [17:45:02:747]: Transforming table Error.
MSI (c) (E4!D4) [17:45:02:747]: Note: 1: 2262 2: Error 3: -2147287038
MSI (c) (E4!D4) [17:45:02:747]: Product: Microsoft SQL Server 2005 -- Error 1706. An installation package for the product Microsoft SQL Server 2005 cannot be found. Try the installation again using a valid copy of the installation package 'SqlRun_SQL.msi'.
Action ended 17:45:02: ResolveSource. Return value 3.
<EndFunc Name='ResolveInstallMediaPath' Return='1602' GetLastError='0'>
<EndFunc Name='BackToBootstrap' Return='1602' GetLastError='0'>
PerfTime Stop: BackToBootstrap : Fri Mar 21 17:45:02 2008
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='1602' GetLastError='0'>
Action ended 17:45:03: BackToBootstrap.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 2.
MSI (c) (E4:98) [17:45:03:013]: Doing action: UserExit
Action 17:45:03: UserExit.
Action start 17:45:03: UserExit.
MSI (c) (E4:98) [17:45:03:013]: Transforming table CustomAction.
MSI (c) (E4:98) [17:45:03:013]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (c) (E4:98) [17:45:03:028]: Transforming table CustomAction.
MSI (c) (E4:98) [17:45:03:044]: Transforming table CustomAction.
MSI (c) (E4:98) [17:45:03:044]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (c) (E4:98) [17:45:03:044]: Transforming table CustomAction.
MSI (c) (E4:98) [17:45:03:044]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (c) (E4:98) [17:45:03:044]: Transforming table CustomAction.
MSI (c) (E4:98) [17:45:03:044]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (c) (E4:7C) [17:45:03:044]: Transforming table Binary.
MSI (c) (E4:7C) [17:45:03:044]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (E4:7C) [17:45:03:059]: Transforming table Binary.
MSI (c) (E4:7C) [17:45:03:059]: Transforming table Binary.
MSI (c) (E4:7C) [17:45:03:059]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (E4:7C) [17:45:03:059]: Transforming table Binary.
MSI (c) (E4:7C) [17:45:03:059]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (E4:7C) [17:45:03:059]: Transforming table Binary.
MSI (c) (E4:7C) [17:45:03:059]: Note: 1: 2262 2: Binary 3: -2147287038
Action 17:45:03: UserExit. Dialog created
Action ended 17:45:04: UserExit. Return value 2.
Action ended 17:45:04: INSTALL. Return value 2.
MSI (c) (E4:98) [17:45:04:622]: Destroying RemoteAPI object.
MSI (c) (E4:64) [17:45:04:637]: Custom Action Manager thread ending.
Property(C): ProductCode = {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
Property(C): ProductLanguage = 1033
Property(C): Manufacturer = Microsoft Corporation
Property(C): ProductVersion = 9.2.3042.00
Property(C): MEDIAPACKAGEPATH = Setup
Property(C): ALLUSERS = 1
Property(C): NULLGUID = {00000000-0000-0000-0000-000000000000}
Property(C): ASPNetVersion = 2.0.50727
Property(C): ARPHELPLINK = http://go.microsoft.com/fwlink/?LinkId=52152
Property(C): ARPPRODUCTICON = ARPIcon.ico
Property(C): ARPNOREPAIR = 1
Property(C): ARPSYSTEMCOMPONENT = 1
Hi All,
My application supports both SQL Server 2005 and Oracle. Now, while chaging the password for the user WHOSE PASSWORD IS ALREADY EXPIRED .... the following code works fine for Oracle , but I dont know how to handle the same thing in SQL Server 2005.Please reply at your earliest.I am posting the code below which is creating the problem.
public static boolean changeExpiredPassword(User user, User newUser) throws SQLException, Exception
{
if (_logger.isDebugEnabled())
{
_logger.debug("changeExpiredPassword(User user=" + user + ", User newUser=" + newUser + ") - start");
}
boolean passwordChanged = false;
String url = null;
Properties dalProps = null;
Connection conn = null;
String sysIdentifier = null;
try
{
dalProps = DALManager.getInstance().getProperties();
url = dalProps.getProperty(DALConfigurator.URL);
if (url != null && url.indexOf("thin") > -1 && url.lastIndexOf(":") > -1)
{
int index = url.lastIndexOf(":");
sysIdentifier = url.substring(index+1, url.length());
url = "jdbcracleci" + sysIdentifier;
}
Properties props = new Properties();
props.put("user", user.getUsername());
props.put("password", user.getDecryptedPassword());
props.put("OCINewPassword", newUser.getDecryptedPassword());
if (DALManager.getInstance().isOracle() &&
url != null)
{
conn = DriverManager.getConnection(url, props);
if(conn != null && !conn.isClosed())
{
passwordChanged = true;
conn.close();
}
}
if (DALManager.getInstance().isSqlServer() &&
url != null) // This condition becomes true if we are connected to SQL Server 2005
{
/// Over here , the connection object is Returning the NULL value since the I have loaded the Properties ( props.put ) with Oracle specifice syntax it ( i.e. OCINewPassword ) . I dont know what to code if its connected to the SQL Server 2005 itstead of Oracle.
conn = DriverManager.getConnection(url,props); // This part fails
if(conn != null && !conn.isClosed())
{
UsersQueryModule.changePassword(user.getUsername(), user.getDecryptedPassword(), newUser.getDecryptedPassword(), false);
passwordChanged = true;
conn.close();
}
}
}
catch (SQLException e)
{
_logger.error("changeExpiredPassword(user=" + user + ", newUser=" + newUser + ")", e);
throw new AxisFault("Expired password cannot be changed. Possible cause may be TNS Name does not match with Oracle SID. Please consult the System Administrator.");
}
catch (Exception e)
{
_logger.error("changeExpiredPassword(user=" + user + ", newUser=" + newUser + ")", e);
throw e;
}
finally
{
if (conn != null && !conn.isClosed())
conn.close();
}
if (_logger.isDebugEnabled())
{
_logger.debug("changeExpiredPassword(User, User) - end - return value=" + passwordChanged);
}
return passwordChanged;
}