Upgrading A Database (good Practice)
Mar 5, 2008
hi experts,
i have a postcode database that i need to update. the database cnotains of 6tables, the file i ahev has all the information at once, so i have to organize it and insert records into the appropriate tables.
this is the first time i'm doign this so i would like to know what the best way to do? do i need to create a stored procedure or a script, or may be something special and efficient that i do not know yet.
any advise will be very appreciated
thanks in advance
View 1 Replies
ADVERTISEMENT
Nov 20, 2007
I know that <asp:SqlDataSource> is fast, but is it a good practice to use this. The sqldatasource is right there in the aspx page and the SQL for sqldatasource is also right there.Does that not break the 3 tier model, as normally we call a database layer and we have all the SQL's there. In one of the code in saw the following. I don't know if it is a good practice to do something like this. <asp:DropDownList ID="CountryDropDownList" runat="server" DataSourceID="SqlDataSource2" DataTextField="PickListLabel" DataValueField="PickListValue" OnDataBound="hidePanel"> </asp:DropDownList><asp:SqlDataSource ID="SqlDataSource2" runat="server" ConnectionString="<%$ ConnectionStrings:webrepos %>" SelectCommand="SELECT [PickListLabel], [PicklistValue] FROM [PickList_Values] WHERE (([ObjectName] = @ObjectName) AND ([FieldName] = @FieldName)) ORDER BY [AbbrCode]"> <SelectParameters> <asp:Parameter DefaultValue="Account" Name="ObjectName" Type="String" /> <asp:Parameter DefaultValue="Country__c" Name="FieldName" Type="String" /> </SelectParameters> </asp:SqlDataSource>
View 5 Replies
View Related
Dec 2, 2005
Hi just new here in the forum i have a question
is it a good practice to use autoincrement fields in an access database for master and detail? and for unique record identification. if not please tell why..
im currently using access and with autoincrement for unique record identification and for master and detail.. then there is a possibilities to transfer from access to mssql. will i encounter problems when migrating since i am using an autoincrement fields
in mssql is there an autoincrement fields like access?
dont be harsh ok.. just anoob trying to learn. :eek:
View 6 Replies
View Related
Jan 9, 2004
I would like to have a stored procedure executed once a week via a DTS package. The data I would like inserted into Table_2, which is the table where the DTS is being executed on, comes from a weekly dump from Oracle into a Table_1 via another DTS package.
I would like to only import data since the last import so I was thinking of my logic to be like this:
INSERT INTO Table_2
(Field1, Field2, ... , FieldN)
VALUES (SELECT Field1, Field2, ... , FieldN FROM Table_1 WHERE ThisDate > MAX(Table_2.ThatDate))
Does this make sense? Or do you all suggest a different mannger of accomplishing this?
View 8 Replies
View Related
Oct 11, 2006
I'm sure this has been asked plenty of times before, so I'm after a link to a good answer.
I have tens of thousands of milk crates, holding dozens of different types of milk in hundreds of locations. I am used to working with objects but not databases. For this situation however I want the security of SQLServer transactions to track, for example, when a robot moves a crate from one location to another.
I am thinking of using SQLServer as a store. On startup I want to get my ecosystem of objects out of the store. While I am running, I'll just use objects. When I change an object property I want it to securely persist. I don't want to snapshot the whole menagerie of object states, just update the values that changed. Which will sometimes include the addition or deletion of objects. How do I do this? Is there an example somewhere that does this (or approximately this)?
I use VB and have Visual Studio 2005. (Which, by the way, is stunning. I thought all that "you will use less time and code more and better" talk was just hype. But its for real. Amazing product.)
tia
John
View 1 Replies
View Related
Mar 25, 2008
Hi All,
I need to send out email when error occurs in the package. Is it a good practice to put the send email task in the event handler? Then MaximumErrorCount is set to 1. But for some reason, some time I saw more than one email are sent out. Please advise. Thanks
View 6 Replies
View Related
Jan 24, 2007
Good Morning,
I work for a company that has sees alot of people come and go. The one thing I have noticed is that people use their admin accounts to log into SQL and create sp, views and databases.When the user leaves I am stuck with all these objects that are owned by somone no longer working for the company.
So my question to you guys is: What is the best practice to use in creating new objects?
Thanks for your guru-ness!
View 3 Replies
View Related
Nov 17, 2006
Can you tell me what is the best practice for SQL database migration fromone DB server, to another one, new DB server. The old DB server will beremoved.1. Backup from old and restore all databases on the new server2. Export data and copy/import on a new server3. Something else...Thanks in advance for any good advice...Regards
View 2 Replies
View Related
Oct 23, 2007
can we upgrade a sqlce forgotten password database to sql server for mobile database on our desktop
Thanks & Regards
Mukesh Gupta
View 1 Replies
View Related
Sep 26, 2007
Hi,
I'm currently building a database that is going to have at least 6 different types of users accessing it via a web application.
A user will have different information collected about them. A few of of the users will have the same or similiar information collected about them.
I will be using role based authentication.
Now my query is this;
Scenario 1:
Would it be a good idea to keep all the users common information in one table. Ie. thier username,email,password,name. Then create a tblDetails for each type of user that would contain the different data. That way i can just check one table to verify thier login credentials.
OR
Scenario 2:
Would it be best to create a seperate table for each type of user and then log them in based on the credentials stored in each type of users respective table.
Hope this is clear. I'm leaning towards scenario 1, although I've used scenario 2 before. Just wondering which would be preferred.
Cheers
RobC
View 2 Replies
View Related
Mar 13, 2006
Hi,
I am new to working with Database using .net C#. i will really appreciate if someone can point me to a link where i can find best practices of working with sql express database with my c# web service applications.
preferably i would like to have answers for:
- to have one db or to have one for testing and one real db?
- db security
- use windows authentication or db user authentication
etc.
View 1 Replies
View Related
Sep 11, 2007
I'm not sure this is the exact forum in which to ask this question, so if there is a more appropriate forum, please point me in that direction.
Basically I'm looking for advice and best practices for dealing with an upgrade plan for a hosted database. Here is the situation:
- Hosted software application (.Net)
- Uses SQL Server 2005
- When we upgrade the software application to a new version, there will be schema and data changes that need to be applied to the database
- For the software application, we have considered upgrading an offline machine and then switching old one instantaneously.
- For the database, I'm trying to figure out if we can keep everything live for upgrades, or if we should have a small amount of scheduled downtime to upgrade.
So we have identified 2 basic directions:
1) Keep the database live and apply the new script changes just after the application software is upgraded. This means zero downtime, but we'd have to design and test our application to be backward compatible, so that the new version of the application code could handle both the new schema design, and the old schema design. It seems that this option would add a huge amount of complexity because we would essentially be testing a 3rd app/schema combination.
2) Take a small amount of scheduled downtime and upgrade the application code and database all at once.
Obviously option #2 is the most desirable from a development process point of view, and #1 is the most desirable option from a business point of view (zero downtime).
So, I'm looking for some advice on this. Do most people take the whole system down? Are there 100% live systems that deal with this? Are there other approaches I'm not considering?
Any information would be greatly appreciated. Thanks.
View 4 Replies
View Related
Dec 29, 2007
Hey I was wondering if you
all could help me with my database. I am very noobish as databasing and I am
not sure what I have is good or bad. This is very long since I tell you basically
what my whole site does/will do. This is in hopes that it will give you a
better understanding of how many database will work.
Japanese WebSite
Purpose of the site:
This sites intention is to help people learn the 2 basic
Japanese character sets Hiragana and Katakana.
Hiragana is usually used for Japanese words and contains 46 basic characters,
plus a set of special characters. Katakana is usually used for foreign words
and also contains 46 basic characters plus a special set of characters.
Hiragana and Katakana are written differently when they are written with Japanese
characters. However if you right them in romaji (this is basically writing words
as if you where writing English and does not involve using characters. This is
used for foreigners while they are learning how to write the Japanese
characters).
Hiragana and Katakana are pronounced exactly the same.
This site will use a quiz style format. The user will first choose from the set
of Hiragana characters then the Katakana characters. Once chosen the website
will randomly choose a character and display the Japanese symbol of it. The user will then write the romaji
representation in the text box provided.
It will be then checked
and if the user is right they will get a new symbol. If they are wrong they
will have try again. The purpose for
this is for the user to get use to see how the character looks like but at the
same time writing in romaji what will be easier for them. This should make it
easier for them the next time they see the character to know how to say it.
Version 1
The site will go through many versions. This version I am
focusing on using C#,asp and ms sql. Later on in future versions ajax and
javascrip will be introduced and parts will be changed. Version 1 also uses CSS
and html.
Version 1 will contain these features.
1. A
practice section. A user will go through a wizard like setup that will first
let them choose from the basic 46 Hiragana characters (the other special
characters will be added later). They will then go to the next setup and choose
from the 46 basic Katanana characters. After they go to another section that
asks them how many repetitions they want to go through. If the user is a member(free membership) they
will have the option to save their settings that will be stored and later
available on the front page called quick links. The next page of the wizard is
actually going through the quiz. Once they are done they will see a summary of
how many they got right,wrong and how many they needed assistance on. At this
point they will be able to view a chart to see their progress(current chart
showing there last attempt, a week one
and a month one). These charts will be either made using c# or ms sql(I saw a
something that says you can make something like that but have not confirmed
it). I may do both ways for a learning experience.
2. A Registration form, login and logout.
3. Quick
link. Quick link will be for registered members so they don’t have to go
through the wizard every time to make their practice quiz up. A user will go
through the wizard once and choose what they want and save it. Quick link will be on all the pages in the
form of mostly likely a grid view. A user will be able to store 3-5 different quiz’s
(in the future maybe more). A user can then click on the quick link and it will
just take them to the quiz. The user will also will be able to update their
quiz through the grid view. This will take them to the start of the wizard and
they can go through it again and then just save over it. They will also be able
to delete there quick links through the grid view.
Currently done
Half of step 1 has been completed. Currently a user can
go through the wizard and select what they want and choose how many repetitions
and go through the quiz. However the summary and charts are not done.
Future versions.
Design will be a major part of it since I have not
focused on this at all. Also since I wanted to experiment with dynamic controls
I made all the checkboxes for the selections dynamically. This caused a problem
that a user must hit a save button since the controls have to get recreated and
updated.
I think normally this might not have been a problem but
since I since I am using a multiview(to create a effect that the wizard is all
on the same page and not the whole page has to be reloaded) it caused some
problems(I can’t really remember since it was a couple months ago when I
started but had to stop due to the amount of school work). This is why I want
to go back later and make them with ajax. This also makes another learning
experience.
Where I am at now.
When I started this I really did not think much of my
database mainly because I am not good at data basing and don’t really like it that
much. I have had a course in data basing (was with oracle though)that was part
of my program. At the time I did not understand very much since I found the
teacher going too fast and he started at chapter 8….. Also when you got 7 other
courses with it it’s hard to learn lots.
I have gone through some tutorials and stuff. I am not
very keen on reading a database book since I just don’t have the time since I
want to also read a book on c#, javascript, ajax and so forth. Also I don’t
know how much I will retain/learn from a book. With some of the stuff I just
find its better to try to something where you will be interested in and then
when needed read chapters of a book or ask questions. This is what I done for my c# stuff like I
had a c# with asp course and 2 months after the courses I started this site and
I had to ask myself what the heck did I learn in that course since it seemed I
knew nothing(and I was close to top in my class). With pounding it out and
reading I was able to accomplish what I needed. Like I still want to read a
book on C# but for now it’s just not going to happen same with Data basing.
All the pervious information was so you can understand
what my website is trying to do so you can better evaluate my database design
and answer my questions.
First Design of my
database.
This is when I just made it up on the spot and did not do
any database design or anything.
Question 1: I
forgot how to limit select query results. Like If I just want to show 10 query
results how do I do this?
I have currently 2 tables How one called Hiragana and the
other Called Katakana
HiraganaID = PK
HiraganaID HiraganaCharacter HiraganaImage
----------- -----------------
--------------------------------------------------
1 a Images/hiragana/a-o/a.jpg
2 i Images/hiragana/a-o/i.jpg
3 u Images/hiragana/a-o/u.jpg
4 e Images/hiragana/a-o/e.jpg
5 o Images/hiragana/a-o/o.jpg
6 ka Images/hiragana/ka-ko/ka.jpg
Katakana
KataKanaID = PK
KatakanaID KatakanaCharacter KatakanaImage
-----------
-------------------------------------------------- --------------------------------------------------
1 chk_Kata_a
Images/katakana/a-o/a.jpg
2 chk_Kata_i
Images/katakana/a-o/i.jpg
3 chk_Kata_u Images/katakana/a-o/u.jpg
4 chk_Kata_e
Images/katakana/a-o/e.jpg
5
chk_Kata_o
Images/katakana/a-o/o.jpg
I quickly found that this design was very bad since I was
unable to add new rows very easily. Each character set has each of its characters
in rows of 5. Some rows however have only 3 romaji characters so what they do
is leave the other cells blank representing that they don’t exist. I wanted to
do this too so I figured the easier way would be to have just null rows of
data. So say for “ya,yu,yo� it would be like this “ya,null,yu,null,o�. That’s
how it would appear in the database so when my c# would read it in it would not
have to account for rows that had less than 5 characters since it would have
already the nulls for it.
You can check a chart out here: http://www.alpha.ac.jp/japanese/img/moji.gif
So with this poor design it would result me in basically
rewriting the database.
I have thought of 2 possible ways to. I am not sure if
either way is good but I will try to explain my reasoning as much as I can.
Possible Way 1
In this approach I have 5 tables.
Hiragana
This table stores all the information about Hiragana
Characters
CREATE TABLE [dbo].[Hiragana](
[HiraganaID] [int] IDENTITY(1,1) NOT NULL,
[HiraganaCharacter] [varchar](5) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL,
[HiraganaImage] [varchar](50) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL,
[SortOrder] [numeric](3, 0) NOT NULL,
CONSTRAINT [PK_Hiragana] PRIMARY
KEY CLUSTERED
Katakana
This table stores all the information about Katakana
Characters
CREATE TABLE [dbo].[Katakana](
[KatakanaID] [int] IDENTITY(1,1) NOT NULL,
[KatakanaCharacter] [varchar](50) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL,
[KatakanaImage] [varchar](50) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL,
[SortOrder] [numeric](3, 0) NOT NULL,
CONSTRAINT [PK_Katakana] PRIMARY
KEY CLUSTERED
Quick Links
This table will store the users quick link information.
CREATE TABLE [dbo].[QuickLinks](
[QuickLinkName] [varchar](50) COLLATE
SQL_Latin1_General_CP1_CI_AS NOT NULL,
[UserID] [int] NOT NULL,
[SavedCharacters] [varchar](200) COLLATE
SQL_Latin1_General_CP1_CI_AS NOT NULL,
[SavedImagePaths] [varchar](200) COLLATE
SQL_Latin1_General_CP1_CI_AS NOT NULL
) ON [PRIMARY]
Users
This will store login information.
CREATE TABLE [dbo].[Users](
[UserID] [int] IDENTITY(1,1) NOT NULL,
[UserName] [varchar](30) COLLATE
SQL_Latin1_General_CP1_CI_AS NOT NULL,
[EmailAddress] [varchar](50) COLLATE
SQL_Latin1_General_CP1_CI_AS NOT NULL,
[Password] [varchar](50) COLLATE
SQL_Latin1_General_CP1_CI_AS NOT NULL,
[DateTimeStamp] [smalldatetime] NOT
NULL,
CONSTRAINT [PK_Users] PRIMARY
KEY CLUSTERED
Charts
This will store all information that will be used for
charts.
CREATE TABLE [dbo].[Charts](
[PracticeNum] [int] IDENTITY(1,1) NOT NULL,
[UserID] [int] NOT NULL,
[Correct] [numeric](3, 0) NOT NULL,
[Wrong] [numeric](3, 0) NOT NULL,
[AssitanceNeeded] [numeric](3, 0) NOT NULL,
[TimeDateStamp] [smalldatetime] NOT
NULL,
CONSTRAINT
[PK_Charts] PRIMARY KEY
CLUSTERED
(
Relationships
Users and QucikLinks have a PK to FK relationship this is
because quicklinks is dependent on the user having a user account. It also away
to identify which QuickLinks will belong to who.
Question 2: Currently I don’t have a primary Key for this
table what would be a good primary key for this table?
QuickLinks also does not have any relationship to either
to HiraganaCharacters or Katakana Characters. This is because I did not feel it
was necessary to grab the information from here. I simply could just grab it
from the array that holds this information from my c# code.
Question 3: How can I make this table for all users? Like
Say they choose 5 characters and save it as QuickLink1(as the
QuickLinkName). Should each of these 5
characters gets its own line or should it all be saved in one row? Or should I
even have another table to hold this data?
Option 1
QuickLinkName UserID
SavedCharacters SavedImagePaths
---------------- ----------- ------------------- --------------------------
QuickLink1 1 a image/a.jpg
QuickLink1 1 i image/i.jpg
QuickLink1 1 u image/u.jpg
QuickLink1 1 e image/e.jpg
QuickLink1 1 o image/o.jpg
QuickLink1 2 a image/a.jpg
QuickLink1 2 ya image/ya.jpg
QuickLink1 2 ki image/ki.jpg
QuickLink1 2 yo image/yo.jpg
QuickLink1 2 n image/n.jpg
Option 2
QuickLinkName UserID
SavedCharacters SavedImagePaths
---------------- ----------- ------------------- --------------------------
QuickLink1 1 a,i,u,e,o image/a.jpg, image/i.jpg,
image/u.jpg, image/e.jpg,
image/o.jpg,
QuickLink2 2 a,ya,ki,yo,n image/a.jpg,
image/ya.jpg,
image/ki.jpg, image/yo.jpg,
image/n.jpg,
Charts table also has a Relationship with Users
The thinking for this one is that Charts will use the
UserID to tell who this data belongs too. It will store the number of correct
answers, wrong answers and AssitanceNeed. This table will also hold a timeDateStamp.
The reason for this is because I want to have a chart that displays the last
Quiz they did and also the stats of a week’s worth of quizzes, and month’s
worth of quiz’s. With a timeDateStamp I should be able to add up all those columns
and then display them for whatever period I choose.
Second Possible
Way.
Characters
CREATE TABLE [dbo].[Chracters](
[CharacterID] [int] NOT NULL,
[CharacterName] [varchar](5) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL,
[CharacterPath] [varchar](50) COLLATE
SQL_Latin1_General_CP1_CI_AS NULL,
[SortOrder] [numeric](3, 0) NOT NULL,
CONSTRAINT [PK_Chracters] PRIMARY
KEY CLUSTERED
This way uses 4 charts instead of 5. The main difference
is that the Hiragana Charts and Katakana Charts have been merged into one
table.
This way has another relationship between Characters and
Quick Links. This will store the Character
ID instead of the actual Characters and Path through the use of C# code. When a
user selects a box it will make a note of the CharacterID. When it is time for
the user to use the QuickLink it will join the tables together and filter out
the CharacterIDs. Giving me the CharacterName and Path.
The problem with this way is that well the code I written
will need to be changed since currently it grabs stuff from 2 tables into one.
I don’t know if this would save anytime over the first way either.
I hope these are sort of close to an alright design since
I did try to think about how my website would interact with the database.
Sorry for it being so long.
Summary of Questions
Question 1: I
forgot how to limit select query results. Like If I just want to show 10 query
results how do I do this?
Question 2: Currently I don’t have a primary Key for this
table what would be a good primary key for this table?
Question 3: How can I make this table for all users? Like
Say they choose 5 characters and save it as QuickLink1(as the
QuickLinkName). Should each of these 5
characters gets its own line or should it all be saved in one row? Or should I
even have another table to hold this data?
View 9 Replies
View Related
Jul 27, 2007
With regards to time zones, daylight savings, and web users, is there a best practice for storing date & time information in a database?
For example, my databases are hosted in Time Zone A, but the web users are in Time Zone B. Then, when I create a rss feed (which is displayed in GMT), I add a third time zone into the mix for the same data. To date (no pun intended), I have been entering the date/time data in the time zone of the database server (Time Zone A), and then converting it using an application setting in the web.config file (i.e. TimeZoneBOffset = -1, GMTOffSet = -5). In other words, each time I display a date I calculate what it should be using the time-zone offset in the web.config. This also enables me to account for changes in day light savings, etc.
My concerns are three fold: 1. What if I move the database to another server and the time zone changes? 2. Right now the users are in only 1 time zone. If I expand it to several then the offset will have to be by users, which is do-able, but something I haven't had experience with in the past. 3. It is likely more efficient to calculate the time zone once on input into the DB, rather than in each use like I'm doing now. What time zone baseline for insert into the db should I use?
Thanks in advance for your help!
PS My application is primarily looking at 'smalldatetime' data - down to the 'minute' level.
View 6 Replies
View Related
Feb 7, 2006
What's the best practice for adding / editing a record into a database with lots of fields ?I am not talking about the mechanics of it, as there are a lot of trivial examples using ADO.NET, stored procs, etc.
Deleting is easy, you just pass in (a few) primary key/keys to uniquely identify the record.
But in the real world when you have, say, a table with 100 fields! Do you code the INSERT sproc by hand, with 100 parameters... then call it with your ADO.NET code ? sounds like a lot of work to me...
What about updating! That's even worst, sometimes you may need to update only 3 or 4 fields, but using sprocs you would have to pass the whole 100 parameters in again, and "update" the whole record (when in fact you are only changing 3 or 4 fields).
With the update i could write different sprocs targeting only the fields i wish to update, but that sounds like duplicating work, vs having one generic update proc.
Sometimes i just feel like bypassing sprocs and having inline sql as it would be less work... but i know it is untidy.. and more potential to be buggy.
So come on guys (and gals)... let's hear your thoughts on how you would handle the insert / update scenarios when you have lots of fields ? Northwind examples are too trivial :-)
View 1 Replies
View Related
Jan 6, 2005
Hey,
Does anyone know how I would go about upgrading a database version to 'C.0.6.43'? I am getting an error and it is telling me to upgrade my database to this version.
Thanks
View 2 Replies
View Related
Jul 27, 1998
After found out the `transfer object` command in MS SQL EM didn`t work well
in my databases, I started code by myself to generate the `Create xxx` statements to copy objects across databases (structure only) using SQL.
I`ve coded out most of them, logins, defaults, UDT, tables, stored procedures,
but then I started to have problems with primary keys and foreign key const.
Has anyone tried to do the same thing before or is there some SQL scripts created to handle this already? Please advise me.
I am thinking to use SQL-DMO with VBscript now. But I still prefer a good
SQL script (old thought, the DB-Lib based `isql` is more reliable than the
SQL-OLE).
Thanks for any suggestion.
- Ken
View 3 Replies
View Related
Sep 12, 2007
I have inherited some responsibilities for which I'm not really qualified, so I'll push on through and maybe not totally fall down.
Assume 10 50GB databases, each in a single MDF file. All these MDF files reside on the C drive (the only drive on the system), running SQL 2005 in a 32-bit Windows 2003 or later, 8GB RAM.
The C drive is 6 physical disks in RAID 5, say about 1.0 TB or so. We have 4 dual-core processors on the box.
We have limited simultaneous users, initally about 8 users doing very heavy write on all tables in any one database. Later, we have about 15 users connecting via Web interface, and doing very heavy read and light writing. Each of the 10 or so database has this lifecycle: Heavy write for about 2 weeks (load data) then heavy read for about 1 month (research and search data), then nothing ever again (db is taken offline).
Of course, this is not enough information to go on, but let's just go on it anyway.
My TempDB, Log (simple recovery), Index etc is all on the same RAID 5 drive (C).
I have two basic questions I'd love to hear feedback on:
1. Is there any real advantage to creating 8 Data files for my database (one per processor core)?
2. Given that the hardware people here REALLY don't want to change anything, what should I fight for first:
a. Separate drive for LOG files?
b. Separate drive for TempDB?
c. Something else
Thanks in advance.
View 1 Replies
View Related
May 7, 2008
If I am upgrading the SQL Server 2005 32 bit to 64 bit (only DB Server), Do Applications that communicate with Database need to be upgraded to 64 bit as well???
Thanks,
View 1 Replies
View Related
Nov 20, 2006
Hello,
I need a tool that will let me model a SQL Server 2005 database and then generate the tables, constraints, etc. from the model. I've never used a modeling tool so my knowledge is quite limited. I don't need to model or reverse engineer an application - my sole concern is on the SQL Server database side. I'm not concerned if the tool integrates with Visual Studio. And, of course, price is one consideration.
Are there any good tools that I should look at?
Thanks,
BCB
View 3 Replies
View Related
Mar 13, 2008
I am actually a newbie to asp.net and i m using ASP.net 3.5 i.e, VWD 2008. i am using it for the first time as my tool to develop a website for my final year project. i am planning to develop an online job recruitment site like www.monster.com. Rigth now i am confused how will i manage my database. i've learned to use databinding concept of SQL SERVER in VWD 2008 but will it be enough to handle such huge # of Job postings and employers and as well as Resumes in pdf of word format? or do i have to create a separate databse in SQL Server and to connect it with my website? i am confused at the moment. please help me in this matter.
Regards,
Jigzy
View 6 Replies
View Related
Apr 27, 2007
I have a WinXP Pro sp2 system that I have installed SQL Express in one case and in another caes I have installed SQL Express sp1. When trying to upgrade either to the next service pack, I get a "Setup Failed" on the "SQL Server Database Services". When I look at the log file, the following is the error:
...
MSI (s) (F8!28) [14:43:23:980]: PROPERTY CHANGE: Adding EditionTypechecksum.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 property. Its value is 'Express Edition with Advanced Services'.
<Func Name='GetSkuIt'>
GetServiceUserGroup failed for SQLEXPRESS, 5
Error Code: 0x80070534 (1332)
Windows Error Text: No mapping between account names and security IDs was done.
Source File Name: sqlcasqlcax.cpp
Compiler Timestamp: Fri Feb 9 22:35:05 2007
Function Name: SetInstanceProperty
Source Line Number: 1223
Error Code: 1332
MSI (s) (F8!28) [14:43:27:235]: Product: Microsoft SQL Server 2005 -- Error 29528. The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
Error 29528. The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
<EndFunc Name='LaunchFunction' Return='1332' GetLastError='203'>...
I was hoping someone has run into this before and can direct me to the solution.
Thank you.
KSLarson
View 3 Replies
View Related
Mar 8, 2007
hi,
I've modified some of my database tables and in the existing version(ver1.3) of my database and i named the new version as ver1.5.
now when i've detached ver1.3 database and attaching ver 1.5 to server it is taking the .ldf file from the folder ver1.3.(I'm maintaning the each version in a saperate folder)
I want to create an independent .ldf file for ver 1.5 also. i dont want to depend on old version for .ldf file.
Can any one help me regarding this issue....
dpindra@yahoo.com
View 1 Replies
View Related
Apr 18, 2002
I upgraded from 6.5 to 7.0 SP3. Now when I save (write) an invoice it takes about 10-12 seconds, at 6.5 it was 1-3 seconds. SQL Server and my Materials App are the only thing running on this box. This is the only area that has gotten slower everything else works great. I have 3 users saving invoices and about 15 people total using the system at one time. It's a compaq DL580 loaded with memory, database is 2,195MB in size. Same 6.5 client to access system as before. Should I rebuild/reindex the database? Is there something from the old 6.5 version I need to remove?? Thanks in advance!!!
View 1 Replies
View Related
Jan 21, 2004
Oke here is the problem. I hope sombody can help me with it.
After a lot of discussion, I finaly got the people that control the MS SQL server with my appertment as far to allow me to upgrade my access database to the MS SQL server.
After this I've created an access project. Devellopping in access I concluded I made a mistake in the rowsource property of one of the tablefields. The people that control the MS SQL server don'n allow me to make changes to the database structure from within access. So I've to write a SQL statement to change this.
example:
fields table1: id_document, id_document_type, document_name
fields tabel2: id_document_type, document_type_description.
the field id_document_type from table 1 is defined as a combo/list box tha contains the values from the field document_type_description from table 2.
I hope somebody can tell me if it is possible to write an SQL statement for this problem and how it shoud look like ?
thank you
View 1 Replies
View Related
Apr 17, 2007
I have one 32-bit SQL 2000 server that is our enterprise-wide reporting server (we'll call it RS) and another 32-bit SQL 2000 server that serves as a stored proc data source for certain reports on that server (we'll call it DS). I am about to go through an upgrade/migration of DS to 64-bit SQL 2005 and was wondering if:
it is possible to just change the data source location on RS and point the old reports against the new DS server?
there are any necessary steps to take within RS to make the data source (DS reference on RS) compatible with the destination (report on RS)?
it is possible/easy to bulk-migrate all the RDL's for a particular data source from RS to DS?
Does anyone know any of the answers to these questions?
Thanks in advance!
View 1 Replies
View Related
May 29, 2007
My question is two fold:
We have a database 65 GB in size and has grown over 12 years.
1) How can I upgrade to 2005 without downtime?
2) Our upgrades on SQL 2000 now can take upwards of 10 hours to add just a column and rebuild index tables?
Any way we can speed this up without detaching the database and going offline?
thanks,
Larry Sitka
View 6 Replies
View Related
Aug 3, 2015
I just upgraded from Windows 7 to Windows 10, and now I can't connect to SQL Server 2008 R2 nor 2014 Express. The logs on both say it can't open master.mdf because it was originally formatted with a sector size 4096 but now it's 3072. But no sector sizes were changed. The only thing that changed was going from Windows 7 (64-bit) to Windows 10 (64-bit). How can this be resolved?
View 10 Replies
View Related
Feb 11, 2015
Copy mssqlsystemresource.mdf of a recently upgraded server and paste to an old server have same effect of upgrading via .exe installation?
My idea is to save time and administrative efforts in upgrades (Service Packs and/or Cumulative Updates) using this method.
According to BOL:
The Resource database makes upgrading to a new version of SQL Server an easier and faster procedure. In earlier versions of SQL Server, upgrading required dropping and creating system objects. Because the Resource database file contains all system objects, an upgrade is now accomplished simply by copying the single Resource database file to the local server.
View 3 Replies
View Related
Nov 7, 2006
I'm having problems upgrading the SQL express 2005 database engine services to 2005 standard 32 bit. I've also tried to install sql 2005 service pack 1 "SQLServer2005SP1-KB913090-x86-ENU.exe" and it did the same thing, upgraded everything except the database engine services. After that I tried another install from the run command "Z:Setup.exe SKUUPGRADE=1" and that failed at the same place as well.
My windows version is is 5.2 (build 3790.srv03_sp1_rtm.050324-1447:service pack 1
Below is a copy of the error log file from the install, any help would be greatly appreciated.
=== Verbose logging started: 11/7/2006 9:06:34 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe ===
MSI (c) (68:CC) [09:06:34:789]: Resetting cached policy values
MSI (c) (68:CC) [09:06:34:789]: Machine policy value 'Debug' is 0
MSI (c) (68:CC) [09:06:34:789]: ******* RunEngine:
******* Product: z:SetupSqlRun_SQL.msi
******* Action:
******* CommandLine: **********
MSI (c) (68:CC) [09:06:34:789]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (68:CC) [09:06:34:789]: Grabbed execution mutex.
MSI (c) (68:CC) [09:06:34:805]: Cloaking enabled.
MSI (c) (68:CC) [09:06:34:805]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (68:CC) [09:06:34:805]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (A0:24) [09:06:34:805]: Grabbed execution mutex.
MSI (s) (A0:E0) [09:06:34:805]: Resetting cached policy values
MSI (s) (A0:E0) [09:06:34:805]: Machine policy value 'Debug' is 0
MSI (s) (A0:E0) [09:06:34:805]: ******* RunEngine:
******* Product: z:SetupSqlRun_SQL.msi
******* Action:
******* CommandLine: **********
MSI (s) (A0:E0) [09:06:34:867]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (A0:E0) [09:06:34:867]: Machine policy value 'TransformsSecure' is 1
MSI (s) (A0:E0) [09:06:34:899]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (A0:E0) [09:06:34:977]: File will have security applied from OpCode.
MSI (s) (A0:E0) [09:06:44:055]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (A0:E0) [09:06:44:086]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'z:SetupSqlRun_SQL.msi' against software restriction policy
MSI (s) (A0:E0) [09:06:44:086]: SOFTWARE RESTRICTION POLICY: z:SetupSqlRun_SQL.msi has a digital signature
MSI (s) (A0:E0) [09:06:53:289]: SOFTWARE RESTRICTION POLICY: z:SetupSqlRun_SQL.msi is permitted to run at the 'unrestricted' authorization level.
MSI (s) (A0:E0) [09:06:53:289]: End dialog not enabled
MSI (s) (A0:E0) [09:06:53:289]: Original package ==> z:SetupSqlRun_SQL.msi
MSI (s) (A0:E0) [09:06:53:289]: Package we're running from ==> C:WINDOWSInstaller4cc6a2.msi
MSI (s) (A0:E0) [09:06:53:367]: APPCOMPAT: looking for appcompat database entry with ProductCode '{778634FA-DB0F-4D0F-B55F-FB0461B36C44}'.
MSI (s) (A0:E0) [09:06:53:367]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (A0:E0) [09:06:53:367]: Detected that this product uses a multiple instance transform.
MSI (s) (A0:E0) [09:06:53:367]: MSCOREE already loaded, using loaded copy
MSI (s) (A0:E0) [09:06:53:367]: Applying multiple instance transform ':SqlRun01.mst'...
MSI (s) (A0:E0) [09:06:53:367]: Looking for storage transform: SqlRun01.mst
MSI (s) (A0:E0) [09:06:53:367]: Validating transform 'SqlRun01.mst' with validation bits 0x809
MSI (s) (A0:E0) [09:06:53:367]: Transform 'SqlRun01.mst' is valid.
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2205 2: 3: Patch
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _Tables 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _Columns 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Media 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: File 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: TRANSFORM: 'PatchPackage' table is missing or empty. No pre-transform fixup necessary.
MSI (s) (A0:E0) [09:06:53:367]: TRANSFORM: Applying regular transform to database.
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _Tables 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _Columns 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _Validation 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: File 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: RegLocator 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: AppSearch 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: CompLocator 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: DrLocator 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Directory 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Registry 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Condition 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: CreateFolder 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlObjectSecurity 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Icon 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: InstallUISequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: AdminExecuteSequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: AdminUISequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: AdvtExecuteSequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: AdvtUISequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlAction 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlActionsModule 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlDriveType 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ReserveCost 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: TypeLib 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Feature 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: MsiAssembly 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Class 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: PublishComponent 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ServiceControl 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ModuleDependency 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ModuleSignature 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ModuleExclusion 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ModuleComponents 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlBuiltInAccounts 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: MsiAssemblyName 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ServiceInstall 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlNativeImage 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlPropertyValues 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlUserSecurity 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlRegistry 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlServiceControl 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlHiveCopy 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlRegSecurity 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlGroup 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlGroupMember 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlConfig 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlUpgradeScript 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlHotfixScript 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlScript 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ActionText 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlSku 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlStart 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlServiceAccount 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlDelimitProperty 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlEquivalent 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlWizardSequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Dialog 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlMofcomp 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlWMISecurity 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlInstanceProperty 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlInstanceComponents 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlAssembly 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlPerfCounters 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlCollation 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlExecutable 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlFileSR 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlUnmanagedComponent 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlUpgradeComponent 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlProducts 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlTopLevelFeatureProducts 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlFileRename 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlFollowComponents 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlLocalServers 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlVerIndependentProgID 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlServiceState 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlServiceProperty 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlServiceConfig 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlSupportFiles 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlDomainGroup 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: FeatureComponents 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Control 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ControlEvent 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ControlCondition 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ListBox 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ListView 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ComboBox 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: CheckBox 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: EventMapping 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: RadioButton 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Upgrade 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: TextStyle 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: UIText 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Media 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Shortcut 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: SxsMsmGenComponents 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: MsiSFCBypass 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: RemoveFile 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: RemoveRegistry 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Environment 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlUpgradeFile 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlUpgradeRegistry 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlUpgradeFolders 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _MsiPatchTransformView 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Machine policy value 'DisablePatch' is 0
MSI (s) (A0:E0) [09:06:53:367]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (A0:E0) [09:06:53:367]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (A0:E0) [09:06:53:367]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (A0:E0) [09:06:53:367]: Looking for storage transform: InstID01.mst
MSI (s) (A0:E0) [09:06:53:367]: Validating transform 'InstID01.mst' with validation bits 0
MSI (s) (A0:E0) [09:06:53:367]: Transform 'InstID01.mst' is valid.
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2205 2: 3: Patch
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _Tables 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _Columns 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Media 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: File 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: TRANSFORM: 'PatchPackage' table is missing or empty. No pre-transform fixup necessary.
MSI (s) (A0:E0) [09:06:53:367]: TRANSFORM: Applying regular transform to database.
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _Tables 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _Columns 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Property 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _Validation 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: File 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: RegLocator 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: AppSearch 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: CompLocator 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: DrLocator 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Directory 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Registry 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Condition 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: CreateFolder 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlObjectSecurity 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Icon 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: InstallUISequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: AdminExecuteSequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: AdminUISequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: AdvtExecuteSequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: AdvtUISequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlAction 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlActionsModule 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlDriveType 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ReserveCost 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: TypeLib 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Feature 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: MsiAssembly 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Class 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: PublishComponent 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ServiceControl 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ModuleDependency 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ModuleSignature 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ModuleExclusion 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ModuleComponents 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlBuiltInAccounts 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: MsiAssemblyName 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ServiceInstall 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlNativeImage 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlPropertyValues 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlUserSecurity 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlRegistry 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlServiceControl 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlHiveCopy 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlRegSecurity 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlGroup 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlGroupMember 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlConfig 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlUpgradeScript 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlHotfixScript 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlScript 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ActionText 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlSku 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlStart 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlServiceAccount 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlDelimitProperty 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlEquivalent 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlWizardSequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Dialog 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlMofcomp 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlWMISecurity 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlInstanceProperty 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlInstanceComponents 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlAssembly 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlPerfCounters 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlCollation 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlExecutable 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlFileSR 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlUnmanagedComponent 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlUpgradeComponent 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlProducts 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlTopLevelFeatureProducts 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlFileRename 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlFollowComponents 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlLocalServers 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlVerIndependentProgID 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlServiceState 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlServiceProperty 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlServiceConfig 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlSupportFiles 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlDomainGroup 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: FeatureComponents 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Control 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ControlEvent 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ControlCondition 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ListBox 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ListView 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: ComboBox 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: CheckBox 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: EventMapping 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: RadioButton 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Upgrade 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: TextStyle 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: UIText 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Media 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Shortcut 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: SxsMsmGenComponents 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: MsiSFCBypass 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: RemoveFile 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: RemoveRegistry 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Environment 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlUpgradeFile 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlUpgradeRegistry 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlUpgradeFolders 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _MsiPatchTransformView 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: #_BaselineCost 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: #_BaselineFile 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: #_BaselineData 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: #_PatchCache 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Looking for storage transform: InstName02.mst
MSI (s) (A0:E0) [09:06:53:367]: Validating transform 'InstName02.mst' with validation bits 0
MSI (s) (A0:E0) [09:06:53:367]: Transform 'InstName02.mst' is valid.
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2205 2: 3: Patch
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _Tables 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _Columns 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Media 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: File 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: TRANSFORM: 'PatchPackage' table is missing or empty. No pre-transform fixup necessary.
MSI (s) (A0:E0) [09:06:53:367]: TRANSFORM: Applying regular transform to database.
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _Tables 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _Columns 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Property 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _Validation 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: File 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: RegLocator 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: AppSearch 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: CompLocator 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: DrLocator 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: CustomAction 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Directory 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Registry 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: Condition 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: CreateFolder 3: -2147287038
MSI (s) (A0:E0) [09:06:53:367]: Note: 1: 2262 2: _sqlObjectSecurity 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: Icon 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: InstallUISequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: AdminExecuteSequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: AdminUISequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: AdvtExecuteSequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: AdvtUISequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlAction 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlActionsModule 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlDriveType 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: ReserveCost 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: TypeLib 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: Feature 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: MsiAssembly 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: Class 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: PublishComponent 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: ServiceControl 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: ModuleDependency 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: ModuleSignature 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: ModuleExclusion 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: ModuleComponents 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlBuiltInAccounts 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: MsiAssemblyName 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: ServiceInstall 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlNativeImage 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlPropertyValues 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlUserSecurity 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlRegistry 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlServiceControl 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlHiveCopy 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlRegSecurity 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlGroup 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlGroupMember 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlConfig 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlUpgradeScript 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlHotfixScript 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlScript 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: ActionText 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlSku 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlStart 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlServiceAccount 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlDelimitProperty 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlEquivalent 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlWizardSequence 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: Dialog 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlMofcomp 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlWMISecurity 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlInstanceProperty 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlInstanceComponents 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlAssembly 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlCollation 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlExecutable 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlFileSR 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlUnmanagedComponent 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlUpgradeComponent 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlProducts 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlTopLevelFeatureProducts 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlFileRename 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlFollowComponents 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlLocalServers 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlVerIndependentProgID 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlServiceState 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlServiceProperty 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlServiceConfig 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlSupportFiles 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlDomainGroup 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: FeatureComponents 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: Control 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: ControlEvent 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: ControlCondition 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: ListBox 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: ListView 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: ComboBox 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: CheckBox 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: EventMapping 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: RadioButton 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: Upgrade 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: TextStyle 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: UIText 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: Media 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: Shortcut 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: SxsMsmGenComponents 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: MsiSFCBypass 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: RemoveFile 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: RemoveRegistry 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: Environment 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlUpgradeFile 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlUpgradeRegistry 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _sqlUpgradeFolders 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: _MsiPatchTransformView 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: #_BaselineCost 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: #_BaselineFile 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: #_BaselineData 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: #_PatchCache 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: APPCOMPAT: looking for appcompat database entry with ProductCode '{130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}'.
MSI (s) (A0:E0) [09:06:53:382]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (A0:E0) [09:06:53:382]: Transforms are not secure.
MSI (s) (A0:E0) [09:06:53:382]: Transforming table Property.
MSI (s) (A0:E0) [09:06:53:382]: Transforming table Property.
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: Property 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Transforming table Property.
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: Property 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Command Line: USERNAME=NW COMPANYNAME=WSDOT PIDKEY=********** INSTALLSQLSHAREDDIR=C:Program FilesMicrosoft SQL Server INSTANCENAME=AUTODESKVAULT INSTALLSQLDIR=F:Program FilesMicrosoft SQL Server INSTALLSQLDATADIR=F:Program FilesMicrosoft SQL Server SECURITYMODE=SQL UPGRADEUSER=sa UPGRADEPWD=********** ENABLERANU=1 STPSETUPTHREADID=5032 STPSETUPPROCESSID=5992 EXTERNALCONTROL=1 ADDLOCAL=SQL_Engine,SQL_Data_Files,SQL_Replication,SQL_FullText,SQL_SharedTools,SQL_BC_DEP TRANSFORMS=:SqlRun01.mst;:InstID01.mst;:InstName02.mst MSINEWINSTANCE=1 UPGRADE=SQL_Engine REBOOT=ReallySuppress CURRENTDIRECTORY=C:Program FilesMicrosoft SQL Server90Setup Bootstrap CLIENTUILEVEL=3 CLIENTPROCESSID=5992
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{3185FC73-41E0-43F4-97DF-2254C4D7C667}'.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding TRANSFORMS property. Its value is ':SqlRun01.mst;:InstID01.mst;:InstName02.mst'.
MSI (s) (A0:E0) [09:06:53:382]: Product Code passed to Engine.Initialize: ''
MSI (s) (A0:E0) [09:06:53:382]: Product Code from property table before transforms: '{778634FA-DB0F-4D0F-B55F-FB0461B36C44}'
MSI (s) (A0:E0) [09:06:53:382]: Product Code from property table after multiple instance transforms: '{130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}'
MSI (s) (A0:E0) [09:06:53:382]: Product Code from property table after transforms: '{130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}'
MSI (s) (A0:E0) [09:06:53:382]: Product not registered: beginning first-time install
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding ProductState property. Its value is '-1'.
MSI (s) (A0:E0) [09:06:53:382]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (A0:E0) [09:06:53:382]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (A0:E0) [09:06:53:382]: Adding new sources is allowed.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding PackagecodeChanging property. Its value is '1'.
MSI (s) (A0:E0) [09:06:53:382]: Package name extracted from package path: 'SqlRun_SQL.msi'
MSI (s) (A0:E0) [09:06:53:382]: Package to be registered: 'SqlRun_SQL.msi'
MSI (s) (A0:E0) [09:06:53:382]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (A0:E0) [09:06:53:382]: Machine policy value 'DisableMsi' is 1
MSI (s) (A0:E0) [09:06:53:382]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (A0:E0) [09:06:53:382]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (A0:E0) [09:06:53:382]: Product installation will be elevated because user is admin and product is being installed per-machine.
MSI (s) (A0:E0) [09:06:53:382]: Running product '{130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}' with elevated privileges: Product is assigned.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding USERNAME property. Its value is 'NW'.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding COMPANYNAME property. Its value is 'WSDOT'.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding INSTALLSQLSHAREDDIR property. Its value is 'C:Program FilesMicrosoft SQL Server'.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding INSTANCENAME property. Its value is 'AUTODESKVAULT'.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding INSTALLSQLDIR property. Its value is 'F:Program FilesMicrosoft SQL Server'.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding INSTALLSQLDATADIR property. Its value is 'F:Program FilesMicrosoft SQL Server'.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding SECURITYMODE property. Its value is 'SQL'.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding UPGRADEUSER property. Its value is 'sa'.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding UPGRADEPWD property. Its value is '**********'.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding ENABLERANU property. Its value is '1'.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding STPSETUPTHREADID property. Its value is '5032'.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding STPSETUPPROCESSID property. Its value is '5992'.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding EXTERNALCONTROL property. Its value is '1'.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding ADDLOCAL property. Its value is 'SQL_Engine,SQL_Data_Files,SQL_Replication,SQL_FullText,SQL_SharedTools,SQL_BC_DEP'.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding MSINEWINSTANCE property. Its value is '1'.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding UPGRADE property. Its value is 'SQL_Engine'.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding REBOOT property. Its value is 'ReallySuppress'.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'C:Program FilesMicrosoft SQL Server90Setup Bootstrap'.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '5992'.
MSI (s) (A0:E0) [09:06:53:382]: TRANSFORMS property is now: :SqlRun01.mst;:InstID01.mst;:InstName02.mst
MSI (s) (A0:E0) [09:06:53:382]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '150'.
MSI (s) (A0:E0) [09:06:53:398]: SHELL32::SHGetFolderPath returned: C:Documents and SettingswprimaccApplication Data
MSI (s) (A0:E0) [09:06:53:398]: SHELL32::SHGetFolderPath returned: C:Documents and SettingswprimaccFavorites
MSI (s) (A0:E0) [09:06:53:398]: SHELL32::SHGetFolderPath returned: C:Documents and SettingswprimaccNetHood
MSI (s) (A0:E0) [09:06:53:398]: SHELL32::SHGetFolderPath returned: C:Documents and SettingswprimaccMy Documents
MSI (s) (A0:E0) [09:06:53:398]: SHELL32::SHGetFolderPath returned: C:Documents and SettingswprimaccPrintHood
MSI (s) (A0:E0) [09:06:53:398]: SHELL32::SHGetFolderPath returned: C:Documents and SettingswprimaccRecent
MSI (s) (A0:E0) [09:06:53:414]: SHELL32::SHGetFolderPath returned: C:Documents and SettingswprimaccSendTo
MSI (s) (A0:E0) [09:06:53:414]: SHELL32::SHGetFolderPath returned: C:Documents and SettingswprimaccTemplates
MSI (s) (A0:E0) [09:06:53:414]: SHELL32::SHGetFolderPath returned: C:Documents and SettingsAll UsersApplication Data
MSI (s) (A0:E0) [09:06:53:414]: SHELL32::SHGetFolderPath returned: C:Documents and SettingswprimaccLocal SettingsApplication Data
MSI (s) (A0:E0) [09:06:53:414]: SHELL32::SHGetFolderPath returned: C:Documents and SettingswprimaccMy DocumentsMy Pictures
MSI (s) (A0:E0) [09:06:53:414]: SHELL32::SHGetFolderPath returned: C:Documents and SettingsAll UsersStart MenuProgramsAdministrative Tools
MSI (s) (A0:E0) [09:06:53:414]: SHELL32::SHGetFolderPath returned: C:Documents and SettingsAll UsersStart MenuProgramsStartup
MSI (s) (A0:E0) [09:06:53:414]: SHELL32::SHGetFolderPath returned: C:Documents and SettingsAll UsersStart MenuPrograms
MSI (s) (A0:E0) [09:06:53:414]: SHELL32::SHGetFolderPath returned: C:Documents and SettingsAll UsersStart Menu
MSI (s) (A0:E0) [09:06:53:429]: SHELL32::SHGetFolderPath returned: C:Documents and SettingsAll UsersDesktop
MSI (s) (A0:E0) [09:06:53:429]: SHELL32::SHGetFolderPath returned: C:Documents and SettingswprimaccStart MenuProgramsAdministrative Tools
MSI (s) (A0:E0) [09:06:53:429]: SHELL32::SHGetFolderPath returned: C:Documents and SettingswprimaccStart MenuProgramsStartup
MSI (s) (A0:E0) [09:06:53:429]: SHELL32::SHGetFolderPath returned: C:Documents and SettingswprimaccStart MenuPrograms
MSI (s) (A0:E0) [09:06:53:429]: SHELL32::SHGetFolderPath returned: C:Documents and SettingswprimaccStart Menu
MSI (s) (A0:E0) [09:06:53:429]: SHELL32::SHGetFolderPath returned: C:Documents and SettingswprimaccDesktop
MSI (s) (A0:E0) [09:06:53:429]: SHELL32::SHGetFolderPath returned: C:Documents and SettingsAll UsersTemplates
MSI (s) (A0:E0) [09:06:53:429]: SHELL32::SHGetFolderPath returned: C:WINDOWSFonts
MSI (s) (A0:E0) [09:06:53:429]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
MSI (s) (A0:E0) [09:06:53:429]: PROPERTY CHANGE: Adding Privileged property. Its value is '1'.
MSI (s) (A0:E0) [09:06:53:429]: PROPERTY CHANGE: Adding DATABASE property. Its value is 'C:WINDOWSInstaller4cc6a2.msi'.
MSI (s) (A0:E0) [09:06:53:429]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is 'z:SetupSqlRun_SQL.msi'.
MSI (s) (A0:E0) [09:06:53:429]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (A0:E0) [09:06:53:429]: Machine policy value 'DisableRollback' is 0
MSI (s) (A0:E0) [09:06:53:429]: User policy value 'DisableRollback' is 0
MSI (s) (A0:E0) [09:06:53:429]: PROPERTY CHANGE: Adding UILevel property. Its value is '2'.
=== Logging started: 11/7/2006 9:06:53 ===
MSI (s) (A0:E0) [09:06:53:429]: PROPERTY CHANGE: Adding Preselected property. Its value is '1'.
MSI (s) (A0:E0) [09:06:53:429]: PROPERTY CHANGE: Adding ACTION property. Its value is 'INSTALL'.
MSI (s) (A0:E0) [09:06:53:429]: Doing action: INSTALL
MSI (s) (A0:E0) [09:06:53:445]: Running ExecuteSequence
MSI (s) (A0:E0) [09:06:53:445]: Doing action: ProgramFilesFolder.68C6D15C_77E0_11D5_8528_00C04F68155C
Action start 9:06:53: INSTALL.
MSI (s) (A0:E0) [09:06:53:445]: PROPERTY CHANGE: Adding ProgramFilesFolder.68C6D15C_77E0_11D5_8528_00C04F68155C property. Its value is 'C:Program Files'.
Action start 9:06:53: ProgramFilesFolder.68C6D15C_77E0_11D5_8528_00C04F68155C.
MSI (s) (A0:E0) [09:06:53:445]: Doing action: CommonFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128
Action ended 9:06:53: ProgramFilesFolder.68C6D15C_77E0_11D5_8528_00C04F68155C. Return value 1.
MSI (s) (A0:E0) [09:06:53:445]: PROPERTY CHANGE: Adding CommonFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 property. Its value is 'C:Program FilesCommon Files'.
Action start 9:06:53: CommonFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128.
MSI (s) (A0:E0) [09:06:53:445]: Doing action: SystemFolder.291EAD4C_0726_4504_A2A1_C9FF1E711B8C
Action ended 9:06:53: CommonFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128. Return value 1.
MSI (s) (A0:E0) [09:06:53:445]: PROPERTY CHANGE: Adding SystemFolder.291EAD4C_0726_4504_A2A1_C9FF1E711B8C property. Its value is 'C:WINDOWSsystem32'.
Action start 9:06:53: SystemFolder.291EAD4C_0726_4504_A2A1_C9FF1E711B8C.
MSI (s) (A0:E0) [09:06:53:445]: Doing action: SystemFolder.7188DA12_A95E_46B7_8623_9D93B5260E2A
Action ended 9:06:53: SystemFolder.291EAD4C_0726_4504_A2A1_C9FF1E711B8C. Return value 1.
MSI (s) (A0:E0) [09:06:53:445]: PROPERTY CHANGE: Adding SystemFolder.7188DA12_A95E_46B7_8623_9D93B5260E2A property. Its value is 'C:WINDOWSsystem32'.
Action start 9:06:53: SystemFolder.7188DA12_A95E_46B7_8623_9D93B5260E2A.
MSI (s) (A0:E0) [09:06:53:445]: Doing action: SystemFolder.7F92F353_B3A2_4AE0_A288_5B746146B1B8
Action ended 9:06:53: SystemFolder.7188DA12_A95E_46B7_8623_9D93B5260E2A. Return value 1.
MSI (s) (A0:E0) [09:06:53:445]: PROPERTY CHANGE: Adding SystemFolder.7F92F353_B3A2_4AE0_A288_5B746146B1B8 property. Its value is 'C:WINDOWSsystem32'.
Action start 9:06:53: SystemFolder.7F92F353_B3A2_4AE0_A288_5B746146B1B8.
MSI (s) (A0:E0) [09:06:53:445]: Doing action: ProgramFilesFolder.EAD22282_F1AF_4119_B1F9_C9F1DCBC62FF
Action ended 9:06:53: SystemFolder.7F92F353_B3A2_4AE0_A288_5B746146B1B8. Return value 1.
MSI (s) (A0:E0) [09:06:53:445]: PROPERTY CHANGE: Adding ProgramFilesFolder.EAD22282_F1AF_4119_B1F9_C9F1DCBC62FF property. Its value is 'C:Program Files'.
Action start 9:06:53: ProgramFilesFolder.EAD22282_F1AF_4119_B1F9_C9F1DCBC62FF.
MSI (s) (A0:E0) [09:06:53:445]: Doing action: CommonFilesFolder.808C44A0_9EC0_4446_A4CB_3E51F5C5D59F
Action ended 9:06:53: ProgramFilesFolder.EAD22282_F1AF_4119_B1F9_C9F1DCBC62FF. Return value 1.
MSI (s) (A0:E0) [09:06:53:445]: PROPERTY CHANGE: Adding CommonFilesFolder.808C44A0_9EC0_4446_A4CB_3E51F5C5D59F property. Its value is 'C:Program FilesCommon Files'.
Action start 9:06:53: CommonFilesFolder.808C44A0_9EC0_4446_A4CB_3E51F5C5D59F.
MSI (s) (A0:E0) [09:06:53:445]: Doing action: CommonFilesFolder.1887A514_D285_4653_98A1_6B7128517683
Action ended 9:06:53: CommonFilesFolder.808C44A0_9EC0_4446_A4CB_3E51F5C5D59F. Return value 1.
MSI (s) (A0:E0) [09:06:53:445]: PROPERTY CHANGE: Adding CommonFilesFolder.1887A514_D285_4653_98A1_6B7128517683 property. Its value is 'C:Program FilesCommon Files'.
Action start 9:06:53: CommonFilesFolder.1887A514_D285_4653_98A1_6B7128517683.
MSI (s) (A0:E0) [09:06:53:461]: Doing action: SystemFolder.60A85CA1_D9D8_43FA_9DD5_574BEF970F9F
Action ended 9:06:53: CommonFilesFolder.1887A514_D285_4653_98A1_6B7128517683. Return value 1.
MSI (s) (A0:E0) [09:06:53:461]: PROPERTY CHANGE: Adding SystemFolder.60A85CA1_D9D8_43FA_9DD5_574BEF970F9F property. Its value is 'C:WINDOWSsystem32'.
Action start 9:06:53: SystemFolder.60A85CA1_D9D8_43FA_9DD5_574BEF970F9F.
MSI (s) (A0:E0) [09:06:53:461]: Doing action: WindowsFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E
Action ended 9:06:53: SystemFolder.60A85CA1_D9D8_43FA_9DD5_574BEF970F9F. Return value 1.
MSI (s) (A0:E0) [09:06:53:461]: PROPERTY CHANGE: Adding WindowsFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E property. Its value is 'C:WINDOWS'.
Action start 9:06:53: WindowsFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E.
MSI (s) (A0:E0) [09:06:53:461]: Doing action: SystemFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E
Action ended 9:06:53: WindowsFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E. Return value 1.
MSI (s) (A0:E0) [09:06:53:461]: PROPERTY CHANGE: Adding SystemFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E property. Its value is 'C:WINDOWSsystem32'.
Action start 9:06:53: SystemFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E.
MSI (s) (A0:E0) [09:06:53:461]: Doing action: WindowsFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E
Action ended 9:06:53: SystemFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E. Return value 1.
MSI (s) (A0:E0) [09:06:53:461]: PROPERTY CHANGE: Adding WindowsFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E property. Its value is 'C:WINDOWS'.
Action start 9:06:53: WindowsFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E.
MSI (s) (A0:E0) [09:06:53:461]: Doing action: SystemFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E
Action ended 9:06:53: WindowsFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E. Return value 1.
MSI (s) (A0:E0) [09:06:53:461]: PROPERTY CHANGE: Adding SystemFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E property. Its value is 'C:WINDOWSsystem32'.
Action start 9:06:53: SystemFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E.
MSI (s) (A0:E0) [09:06:53:461]: Doing action: WindowsFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E
Action ended 9:06:53: SystemFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E. Return value 1.
MSI (s) (A0:E0) [09:06:53:461]: PROPERTY CHANGE: Adding WindowsFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E property. Its value is 'C:WINDOWS'.
Action start 9:06:53: WindowsFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E.
MSI (s) (A0:E0) [09:06:53:461]: Doing action: SystemFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E
Action ended 9:06:53: WindowsFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E. Return value 1.
MSI (s) (A0:E0) [09:06:53:461]: PROPERTY CHANGE: Adding SystemFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E property. Its value is 'C:WINDOWSsystem32'.
Action start 9:06:53: SystemFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E.
MSI (s) (A0:E0) [09:06:53:461]: Doing action: WindowsFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E
Action ended 9:06:53: SystemFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E. Return value 1.
MSI (s) (A0:E0) [09:06:53:461]: PROPERTY CHANGE: Adding WindowsFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E property. Its value is 'C:WINDOWS'.
Action start 9:06:53: WindowsFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E.
MSI (s) (A0:E0) [09:06:53:461]: Doing action: SystemFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E
Action ended 9:06:53: WindowsFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E. Return value 1.
MSI (s) (A0:E0) [09:06:53:461]: PROPERTY CHANGE: Adding SystemFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E property. Its value is 'C:WINDOWSsystem32'.
Action start 9:06:53: SystemFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E.
MSI (s) (A0:E0) [09:06:53:476]: Doing action: WindowsFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E
Action ended 9:06:53: SystemFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E. Return value 1.
MSI (s) (A0:E0) [09:06:53:476]: PROPERTY CHANGE: Adding WindowsFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E property. Its value is 'C:WINDOWS'.
Action start 9:06:53: WindowsFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E.
MSI (s) (A0:E0) [09:06:53:476]: Doing action: SystemFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E
Action ended 9:06:53: WindowsFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E. Return value 1.
MSI (s) (A0:E0) [09:06:53:476]: PROPERTY CHANGE: Adding SystemFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E property. Its value is 'C:WINDOWSsystem32'.
Action start 9:06:53: SystemFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E.
MSI (s) (A0:E0) [09:06:53:476]: Doing action: WindowsFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E
Action ended 9:06:53: SystemFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E. Return value 1.
MSI (s) (A0:E0) [09:06:53:476]: PROPERTY CHANGE: Adding WindowsFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E property. Its value is 'C:WINDOWS'.
Action start 9:06:53: WindowsFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E.
MSI (s) (A0:E0) [09:06:53:476]: Doing action: SystemFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E
Action ended 9:06:53: WindowsFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E. Return value 1.
MSI (s) (A0:E0) [09:06:53:476]: PROPERTY CHANGE: Adding SystemFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E property. Its value is 'C:WINDOWSsystem32'.
Action start 9:06:53: SystemFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E.
MSI (s) (A0:E0) [09:06:53:476]: Doing action: WindowsFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E
Action ended 9:06:53: SystemFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E. Return value 1.
MSI (s) (A0:E0) [09:06:53:476]: PROPERTY CHANGE: Adding WindowsFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E property. Its value is 'C:WINDOWS'.
Action start 9:06:53: WindowsFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E.
MSI (s) (A0:E0) [09:06:53:476]: Doing action: SystemFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E
Action ended 9:06:53: WindowsFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E. Return value 1.
MSI (s) (A0:E0) [09:06:53:476]: PROPERTY CHANGE: Adding SystemFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E property. Its value is 'C:WINDOWSsystem32'.
Action start 9:06:53: SystemFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E.
MSI (s) (A0:E0) [09:06:53:476]: Doing action: WindowsFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
Action ended 9:06:53: SystemFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E. Return value 1.
MSI (s) (A0:E0) [09:06:53:476]: PROPERTY CHANGE: Adding WindowsFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E property. Its value is 'C:WINDOWS'.
Action start 9:06:53: WindowsFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E.
MSI (s) (A0:E0) [09:06:53:476]: Doing action: SystemFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
Action ended 9:06:53: WindowsFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E. Return value 1.
MSI (s) (A0:E0) [09:06:53:476]: PROPERTY CHANGE: Adding SystemFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E property. Its value is 'C:WINDOWSsystem32'.
Action start 9:06:53: SystemFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E.
MSI (s) (A0:E0) [09:06:53:476]: Doing action: ProgramMenuFolder.ConfigurationTools1033
Action ended 9:06:53: SystemFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E. Return value 1.
MSI (s) (A0:E0) [09:06:53:476]: PROPERTY CHANGE: Adding ProgramMenuFolder.ConfigurationTools1033 property. Its value is 'C:Documents and SettingsAll UsersStart MenuPrograms'.
Action start 9:06:53: ProgramMenuFolder.ConfigurationTools1033.
MSI (s) (A0:E0) [09:06:53:492]: Doing action: ProgramFilesFolder.D20239D7_E87C_40C9_9837_E70B8D4882C2
Action ended 9:06:53: ProgramMenuFolder.ConfigurationTools1033. Return value 1.
MSI (s) (A0:E0) [09:06:53:492]: PROPERTY CHANGE: Adding ProgramFilesFolder.D20239D7_E87C_40C9_9837_E70B8D4882C2 property. Its value is 'C:Program Files'.
Action start 9:06:53: ProgramFilesFolder.D20239D7_E87C_40C9_9837_E70B8D4882C2.
MSI (s) (A0:E0) [09:06:53:492]: Doing action: SetMDACSxS
Action ended 9:06:53: ProgramFilesFolder.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 1.
MSI (s) (A0:E0) [09:06:53:492]: PROPERTY CHANGE: Adding MDACSXS property. Its value is '1'.
Action start 9:06:53: SetMDACSxS.
MSI (s) (A0:E0) [09:06:53:492]: Doing action: SetInstanceName
Action ended 9:06:53: SetMDACSxS. Return value 1.
MSI (s) (A0:E0) [09:06:53:492]: PROPERTY CHANGE: Adding SqlInstanceName property. Its value is 'AUTODESKVAULT'.
Action start 9:06:53: SetInstanceName.
MSI (s) (A0:E0) [09:06:53:492]: Doing action: SetCollation
Action ended 9:06:53: SetInstanceName. Return value 1.
Action start 9:06:53: SetCollation.
MSI (s) (A0:E0) [09:06:53:492]: Doing action: SetSecurityMode
Action ended 9:06:53: SetCollation. Return value 1.
MSI (s) (A0:E0) [09:06:53:492]: PROPERTY CHANGE: Adding SqlSecurityMode property. Its value is 'SQL'.
Action start 9:06:53: SetSecurityMode.
MSI (s) (A0:E0) [09:06:53:492]: Doing action: SetUpgradeUser
Action ended 9:06:53: SetSecurityMode. Return value 1.
MSI (s) (A0:E0) [09:06:53:492]: PROPERTY CHANGE: Adding SqlUpgradeUser property. Its value is 'sa'.
Action start 9:06:53: SetUpgradeUser.
MSI (s) (A0:E0) [09:06:53:492]: Skipping action: ErrorDisableNetworkProtocols (condition is false)
MSI (s) (A0:E0) [09:06:53:492]: Skipping action: SetCluster (condition is false)
MSI (s) (A0:E0) [09:06:53:492]: Doing action: SetClusterSec
Action ended 9:06:53: SetUpgradeUser. Return value 1.
Action start 9:06:53: SetClusterSec.
MSI (s) (A0:E0) [09:06:53:492]: Doing action: SetSaPwd
Action ended 9:06:53: SetClusterSec. Return value 1.
Action start 9:06:53: SetSaPwd.
MSI (s) (A0:E0) [09:06:53:492]: Doing action: SetUpgradePwd
Action ended 9:06:53: SetSaPwd. Return value 1.
MSI (s) (A0:E0) [09:06:53:492]: PROPERTY CHANGE: Adding SqlUpgradePwd property. Its value is '**********'.
Action start 9:06:53: SetUpgradePwd.
MSI (s) (A0:E0) [09:06:53:492]: Doing action: StreamSupportFiles.D20239D7_E87C_40C9_9837_E70B8D4882C2
Action ended 9:06:53: SetUpgradePwd. Return value 1.
MSI (s) (A0:D0) [09:06:53:523]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI40E.tmp, Entrypoint: StreamSupportFiles
MSI (s) (A0:C8) [09:06:53:523]: Generating random cookie.
MSI (s) (A0:C8) [09:06:53:523]: Created Custom Action Server with PID 4592 (0x11F0).
MSI (s) (A0:A8) [09:06:53:554]: Running as a service.
MSI (s) (A0:A8) [09:06:53:554]: Hello, I'm your 32bit Impersonated custom action server.
Action start 9:06:53: StreamSupportFiles.D20239D7_E87C_40C9_9837_E70B8D4882C2.
Property(SQL): Setup Bootstrap Directory = C:Program FilesMicrosoft SQL Server90Setup Bootstrap
1: 0 2: Iterating through _sqlSupportFiles entries
Streamed sqlca.D20239D7_E87C_40C9_9837_E70B8D4882C2 to C:Program FilesMicrosoft SQL Server90Setup Bootstrapin{130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}sqlca.dll
MSI (s) (A0:E0) [09:06:53:664]: Doing action: Do_LogInstallStart.D20239D7_E87C_40C9_9837_E70B8D4882C2
Action ended 9:06:53: StreamSupportFiles.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 1.
MSI (s) (A0:90) [09:06:53:679]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI40F.tmp, Entrypoint: Do_LogInstallStart
Action start 9:06:53: Do_LogInstallStart.D20239D7_E87C_40C9_9837_E70B8D4882C2.
Property(SQL): Setup Bootstrap Directory = C:Program FilesMicrosoft SQL Server90Setup Bootstrap
Property(SQL): CA DLL Path = C:Program FilesMicrosoft SQL Server90Setup BootstrapBin{130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}sqlca.dll
<Func Name='LaunchFunction'>
Function=Do_LogInstallStart
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: Do_LogInstallStart
PerfTime Start: Do_LogInstallStart : Tue Nov 07 09:06:53 2006
<Func Name='Do_LogInstallStart'>
<EndFunc Name='Do_LogInstallStart' Return='0' GetLastError='203'>
PerfTime Stop: Do_LogInstallStart : Tue Nov 07 09:06:53 2006
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (A0:E0) [09:06:53:773]: Doing action: GetDefaultDomain.D20239D7_E87C_40C9_9837_E70B8D4882C2
Action ended 9:06:53: Do_LogInstallStart.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 1.
MSI (s) (A0:04) [09:06:53:804]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI410.tmp, Entrypoint: GetDefaultDomain
Action start 9:06:53: GetDefaultDomain.D20239D7_E87C_40C9_9837_E70B8D4882C2.
<Func Name='LaunchFunction'>
Function=GetDefaultDomain
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: GetDefaultDomain
PerfTime Start: GetDefaultDomain : Tue Nov 07 09:06:53 2006
<Func Name='GetDefaultDomain'>
MSI (s) (A0!F4) [09:06:53:820]: PROPERTY CHANGE: Adding DefaultDomain property. Its value is 'WSDOT'.
MSI (s) (A0!F4) [09:06:53:820]: PROPERTY CHANGE: Adding QuotedDefaultDomain property. Its value is 'WSDOT'.
MSI (s) (A0!F4) [09:06:53:820]: PROPERTY CHANGE: Adding QuotedComputerName property. Its value is 'NWUCWFAUTODESK'.
PerfTime Stop: GetDefaultDomain : Tue Nov 07 09:06:53 2006
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (A0:E0) [09:06:53:820]: Doing action: RestoreSetupParams.D20239D7_E87C_40C9_9837_E70B8D4882C2
Action ended 9:06:53: GetDefaultDomain.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 1.
MSI (s) (A0:8C) [09:06:53:851]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI411.tmp, Entrypoint: RestoreSetupParams
Action start 9:06:53: RestoreSetupParams.D20239D7_E87C_40C9_9837_E70B8D4882C2.
<Func Name='LaunchFunction'>
Function=RestoreSetupParams
Skipping Action: RestoreSetupParams (Condition is false)
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (A0:E0) [09:06:53:867]: Doing action: LaunchConditions
Action ended 9:06:53: RestoreSetupParams.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 1.
MSI (s) (A0:E0) [09:06:53:867]: Note: 1: 2205 2: 3: LaunchCondition
MSI (s) (A0:E0) [09:06:53:867]: Note: 1: 2228 2: 3: LaunchCondition 4: SELECT `Condition`, `Description` FROM `LaunchCondition`
Action start 9:06:53: LaunchConditions.
MSI (s) (A0:E0) [09:06:53:867]: Skipping action: Collation.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 (condition is false)
MSI (s) (A0:E0) [09:06:53:867]: Doing action: ShutdownServiceManager.D20239D7_E87C_40C9_9837_E70B8D4882C2
Action ended 9:06:53: LaunchConditions. Return value 0.
MSI (s) (A0:C0) [09:06:53:882]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI412.tmp, Entrypoint: ShutdownServiceManager
Action start 9:06:53: ShutdownServiceManager.D20239D7_E87C_40C9_9837_E70B8D4882C2.
<Func Name='LaunchFunction'>
Function=ShutdownServiceManager
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: ShutdownServiceManager
PerfTime Start: ShutdownServiceManager : Tue Nov 07 09:06:53 2006
<Func Name='ShutdownServiceManager'>
<EndFunc Name='ShutdownServiceManager' Return='0' GetLastError='2'>
PerfTime Stop: ShutdownServiceManager : Tue Nov 07 09:06:53 2006
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (A0:E0) [09:06:53:914]: Doing action: Write_sqlWellKnownAccountNames.D20239D7_E87C_40C9_9837_E70B8D4882C2
Action ended 9:06:53: ShutdownServiceManager.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 1.
MSI (s) (A0:D4) [09:06:53:929]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI413.tmp, Entrypoint: Write_sqlWellKnownAccountNames
Action start 9:06:53: Write_sqlWellKnownAccountNames.D20239D7_E87C_40C9_9837_E70B8D4882C2.
<Func Name='LaunchFunction'>
Function=Write_sqlWellKnownAccountNames
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: Write_sqlWellKnownAccountNames
PerfTime Start: Write_sqlWellKnownAccountNames : Tue Nov 07 09:06:53 2006
<Func Name='Write_sqlWellKnownAccountNames'>
MSI (s) (A0!10) [09:06:53:945]: PROPERTY CHANGE: Adding AdministratorsGroup property. Its value is 'BUILTINAdministrators'.
MSI (s) (A0!10) [09:06:53:945]: PROPERTY CHANGE: Adding PerformanceMontiorUsersGroup property. Its value is 'BUILTINPerformance Monitor Users'.
MSI (s) (A0!10) [09:06:53:961]: PROPERTY CHANGE: Adding PerformanceLogUsersGroup property. Its value is 'BUILTINPerformance Log Users'.
MSI (s) (A0!10) [09:06:53:961]: PROPERTY CHANGE: Adding UsersGroup property. Its value is 'BUILTINUsers'.
MSI (s) (A0!10) [09:06:53:961]: PROPERTY CHANGE: Adding NetworkServiceAccount property. Its value is 'NT AUTHORITYNETWORK SERVICE'.
MSI (s) (A0!10) [09:06:53:961]: PROPERTY CHANGE: Adding SCMNetworkServiceAccount property. Its value is 'NT AUTHORITYNetworkService'.
MSI (s) (A0!10) [09:06:53:961]: PROPERTY CHANGE: Adding LocalSystemAccount property. Its value is 'NT AUTHORITYSYSTEM'.
MSI (s) (A0!10) [09:06:53:961]: PROPERTY CHANGE: Adding LocalServiceAccount property. Its value is 'NT AUTHORITYLOCAL SERVICE'.
MSI (s) (A0!10) [09:06:53:961]: PROPERTY CHANGE: Adding SCMLocalServiceAccount property. Its value is 'NT AUTHORITYLocalService'.
<EndFunc Name='Write_sqlWellKnownAccountNames' Return='0' GetLastError='0'>
PerfTime Stop: Write_sqlWellKnownAccountNames : Tue Nov 07 09:06:53 2006
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (A0:E0) [09:06:53:961]: Skipping action: PropSetSQLAutoStart.D20239D7_E87C_40C9_9837_E70B8D4882C2 (condition is false)
MSI (s) (A0:E0) [09:06:53:961]: Doing action: CheckIIS.D20239D7_E87C_40C9_9837_E70B8D4882C2
Action ended 9:06:53: Write_sqlWellKnownAccountNames.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 1.
MSI (s) (A0:A8) [09:06:53:976]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI414.tmp, Entrypoint: CheckIIS
Action start 9:06:53: CheckIIS.D20239D7_E87C_40C9_9837_E70B8D4882C2.
<Func Name='LaunchFunction'>
Function=CheckIIS
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: CheckIIS
PerfTime Start: CheckIIS : Tue Nov 07 09:06:54 2006
<Func Name='CheckIIS'>
MSI (s) (A0!6C) [
View 5 Replies
View Related
Jun 2, 2004
Hello, everyone:
Does any one know the good T-SQL practice topic web site? It is better to include solutions. Thanks a lot.
ZYT
View 2 Replies
View Related
Sep 3, 2006
When setting up databases for end users, what's the best practice regarding who's the dbo for each individual database - the user itself or a sysadmin?
Does it really have any importance at all who the owner (as defined by 'dbo') is ?
View 5 Replies
View Related
May 7, 2007
(Terms)
TermID, Term
1----- Abc
2----- Arcico
3----- Tunic
and
(RelatedTerms)
TermID, RelatedTermID
1 ------ 3
1------ 2
2------ 4
I want to get the following results
1.- a list of all the terms that start with A%
2.- a list of all the related terms … that belong to terms that start with A%
For number 1 - I am doing a select on Terms table with where term like A%.
For number 2 – I am joining both tables and then once again doing a where term like A%.
Would it be more efficient to take the first results and put them in a table variable, and then just do a join with the second table RelatedTerms.TermID = Terms .TermID
The number of records that generally comeback are between 500 to 1000 records that
What would you consider is a better approach ? or maybe there is an even better way ?
View 4 Replies
View Related
