Install Error SQL Personal

May 12, 2004

I’m trying to install SQL 2000 personal edition on my XP pro machine, but during installation I get an error _INS5576._MP.exe and the installation stops.
I would appreciate any advice the you could offer me.

View 3 Replies


ADVERTISEMENT

SQL Server 2000 Std Ed/Personal Ed Install Problem

Jul 1, 2004

I already had MSDE installed on my laptop and I was trying to load the Client Tools. I stopped the MSDE service, then tried to install the Client Tools from the SQL Server 2000 Standard Edition (Personal Edition) CD. Near the end of the install, I received an error telling me that the C:Program FilesCommon FilesMicrosoft SharedSQL Debuggingsqldbg.dll file was in use and it would not complete the install.

So, I removed the MSDE thru Add/Remove programs, rebooted, then tried to install SQL Server 2000 Std Ed (Personal Ed) and the Client Tools from the CD. Same error message. I used My Computer to try to go to that folder and see the sqldbg.dll file, but when I try to open the folder it tells me "Access is denied".

Obviously, something is using this file, but I'm not sure where to go from here. Any suggestions?

Thanks,

Chris

View 1 Replies View Related

Personal Web Developer Kit SQL Error

Jun 30, 2007

Hi folks,

I get this error message when I try to run my personal web page starter kit (Ctrl + F5) which has come straight out of the box:


Server Error in '/WebSite1' Application.


An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

SQLExpress database file auto-creation error:



The connection string specifies a local Sql Server Express instance using a database location within the applications App_Data directory. The provider attempted to automatically create the application services database because the provider determined that the database does not exist. The following configuration requirements are necessary to successfully check for existence of the application services database and automatically create the application services database:


If the applications App_Data directory does not already exist, the web server account must have read and write access to the applications directory. This is necessary because the web server account will automatically create the App_Data directory if it does not already exist.
If the applications App_Data directory already exists, the web server account only requires read and write access to the applications App_Data directory. This is necessary because the web server account will attempt to verify that the Sql Server Express database already exists within the applications App_Data directory. Revoking read access on the App_Data directory from the web server account will prevent the provider from correctly determining if the Sql Server Express database already exists. This will cause an error when the provider attempts to create a duplicate of an already existing database. Write access is required because the web server accounts credentials are used when creating the new database.
Sql Server Express must be installed on the machine.
The process identity for the web server account must have a local user profile. See the readme document for details on how to create a local user profile for both machine and domain accounts.



Source Error:





An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:





[SqlException (0x80131904): An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)]
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +173
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +199
System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) +1069
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +606
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +193
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +219
System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) +27
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +49
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +89
System.Data.SqlClient.SqlConnection.Open() +160
System.Web.Management.SqlServices.GetSqlConnection(String server, String user, String password, Boolean trusted, String connectionString) +67

[HttpException (0x80004005): Unable to connect to SQL Server database.]
System.Web.Management.SqlServices.GetSqlConnection(String server, String user, String password, Boolean trusted, String connectionString) +123
System.Web.Management.SqlServices.SetupApplicationServices(String server, String user, String password, Boolean trusted, String connectionString, String database, String dbFileName, SqlFeatures features, Boolean install) +89
System.Web.Management.SqlServices.Install(String database, String dbFileName, String connectionString) +26
System.Web.DataAccess.SqlConnectionHelper.CreateMdfFile(String fullFileName, String dataDir, String connectionString) +388





Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210



In my web administration tool, under the Security tab the following error is listed:



There is a problem with your selected data store. This can be caused by an invalid server name or credentials, or by insufficient permission. It can also be caused by the role manager feature not being enabled. Click the button below to be redirected to a page where you can choose a new data store.

The following message may help in diagnosing the problem: Unable to connect to SQL Server database.



and under the provider tab the provider is listed as: AspNetSqlProvider.



So what do I need to do?

(By the way, I wasn't exactly sure where to put this post, but if it gets moved to another forum please may you post the new link? Cheers)

View 6 Replies View Related

SQL Server Personal Edition Error 1069

Apr 1, 2004

I have just installed the personal edition on a win xp pro PC, the installation seemed to work ok but when I try to start SQL in the Service Manager I get the following error:

"service did not start due to login failure - error 1069"

I have already got the Enterprise Edition installed on a win 2000 server which has been working nicely and used the same settings on the new xp PC, could this be the problem. I installed it using the domain user accout and SQL server authentication.

Anyone know how I can fix this?

Thanks

View 1 Replies View Related

SQL Server Error - Trying To Deploy Personal Website Package

Apr 20, 2007

After using FTP to transfer my site to Dotster, I get an error upon running the site. Here are the source error and stack trace respectively:
Line 5:  void Application_Start(object sender, EventArgs e) {Line 6:  SiteMap.SiteMapResolve += new SiteMapResolveEventHandler(AppendQueryString);Line 7:  if (!Roles.RoleExists("Administrators")) Roles.CreateRole("Administrators");Line 8:  if (!Roles.RoleExists("Friends")) Roles.CreateRole("Friends"); 
[SqlException (0x80131904): An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)]
The host provider says I must create the database [on their server] using their on-line utility, Is this true? Or do I need to configure the server to allow remote connections? If the latter is true, how is it accomplished?
Thanks in advance.... any help is appreciated.
 

View 4 Replies View Related

Failed To Install And Configure Error On Install

Nov 14, 2007

Hi,

I've tried looking for a solution in other threads but I couldn't find anything that was completely the same as my situation. I got a new pc at work and I've tried installing SQL Server 2005 on it but everytime I try to install it, regardless of services included or excluded with the install, I cannot get through the install without this error. Below is the excerpt from the Summary.txt log file.


Error Code: -2147024894
MSI (s) (74!98) [17:10:55:858]: Product: Microsoft SQL Server 2005 Tools -- Error 29549. Failed to install and configure assemblies C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242Binmicrosoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2147024894
Error message: The system cannot find the file specified.
Error description: Could not load file or assembly 'System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

Error 29549. Failed to install and configure assemblies C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242Binmicrosoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2147024894
Error message: The system cannot find the file specified.
Error description: Could not load file or assembly 'System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_sqlAssemblyRegSvcs
PerfTime Start: Do_sqlAssemblyRegSvcs : Mon Nov 12 17:10:55 2007
<Func Name='Do_sqlAssemblyRegSvcs'>
Failed to install and configure assemblies C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242Binmicrosoft.sqlserver.notificationservices.dll in the COM+ catalog.
Error: 2147942402
Error message: The system cannot find the file specified.
Error descrition: Could not load file or assembly 'System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
Error Code: -2147024894
Windows Error Text: The system cannot find the file specified.
Source File Name: sqlcasqlassembly.cpp
Compiler Timestamp: Thu Aug 11 01:12:01 2005
Function Name: Do_sqlAssemblyRegSvcs
Source Line Number: 155


I've searched for and found similar problems that deal with the microsoft.sqlserver.notificationservices.dll not being found but I haven't found a fix that worked for me. These are the fixes I've refered to thus far.


http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1651162&SiteID=17

http://support.microsoft.com/kb/940971

http://www.microsoft.com/products/ee/transform.aspx?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=29549&EvtType=sqlcasqlassembly.cpp@Do_sqlAssemblyRegSvcs@Do_sqlAssemblyRegSvcs@x80131501


The answer that seems to fix this problem for everyone is to set the MSDTC service login as the NT AUTHORITYNetworkService account. The problem for me is that this is already set to this profile and I've tried resetting the services and rebooting the machine. I did not have a problem with my old machine, which as far as I can tell, is the same configuration, so I know this install should work.


I'm running Windows XP SP2. This is not the upgrade to SQL Server 2005 SP2, this is the original disk that came with Visual Studio 2005.


Has anyone else faced this issue where changing the MSDTC login wasn't the solution? Also, this is my first post, so I apologize if I've left anything out. Just let me know if you want any other information.


Thank you in advance.
Tim

View 7 Replies View Related

SQL Server 2005 Install Error (Error 29528. Unexpected Error While Installing Performance Counters. )

Jun 12, 2007

I'm currently receiving the following error message whilst attempting to install SQL Server 2005 Standard Edition on Windows Server 2003 (32 Bit):
Error 29528. The setup has encountered an unexpected error while Installing performance counters. The error is: The system cannot find the file specified.

This server already has an install of SQL Server 2000 as the default instance. I'm attempting to install a new named instance of SQL Server 2005.

Extract from log:

<Func Name='LaunchFunction'>
Function=Do_sqlPerfmon2
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='0'>
Doing Action: Do_sqlPerfmon2
PerfTime Start: Do_sqlPerfmon2 : Tue Jun 12 10:20:02 2007
<Func Name='Do_sqlPerfmon2'>
<EndFunc Name='Do_sqlPerfmon2' Return='0' GetLastError='2'>
PerfTime Stop: Do_sqlPerfmon2 : Tue Jun 12 10:20:02 2007
MSI (s) (4C:FC) [10:20:02:833]: Executing op: ActionStart(Name=Rollback_Do_sqlPerfmon2.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Removing performance counters,)
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (4C:FC) [10:20:02:849]: Executing op: CustomActionSchedule(Action=Rollback_Do_sqlPerfmon2.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1281,Source=BinaryData,Target=Rollback_Do_sqlPerfmon2,CustomActionData=100Removing performance counters200000DTSPipelineC:Program FilesMicrosoft SQL Server90DTSBinnDTSPERF.INI)
MSI (s) (4C:FC) [10:20:02:849]: Executing op: ActionStart(Name=Do_sqlPerfmon2.D20239D7_E87C_40C9_9837_E70B8D4882C2,Description=Installing performance counters,)
MSI (s) (4C:FC) [10:20:02:849]: Executing op: CustomActionSchedule(Action=Do_sqlPerfmon2.D20239D7_E87C_40C9_9837_E70B8D4882C2,ActionType=1025,Source=BinaryData,Target=Do_sqlPerfmon2,CustomActionData=100Installing performance counters200000C:Program FilesMicrosoft SQL Server90DTSBinnDTSPERF.INIC:Program FilesMicrosoft SQL Server90DTSBinnDTSPERF.HC:Program FilesMicrosoft SQL Server90DTSBinnDTSPipelinePerf.dllDTSPipeline0DTSPipelinePrfData_OpenPrfData_CollectPrfData_Close)
MSI (s) (4C:94) [10:20:02:864]: Invoking remote custom action. DLL: C:WINDOWSInstallerMSI1683.tmp, Entrypoint: Do_sqlPerfmon2
<Func Name='LaunchFunction'>
Function=Do_sqlPerfmon2
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='0'>
Doing Action: Do_sqlPerfmon2
PerfTime Start: Do_sqlPerfmon2 : Tue Jun 12 10:20:02 2007
<Func Name='Do_sqlPerfmon2'>
<EndFunc Name='Do_sqlPerfmon2' Return='2' GetLastError='2'>
PerfTime Stop: Do_sqlPerfmon2 : Tue Jun 12 10:20:02 2007
Gathering darwin properties for failure handling.
Error Code: 2
MSI (s) (4C!F0) [10:23:46:381]: Product: Microsoft SQL Server 2005 Integration Services -- Error 29528. The setup has encountered an unexpected error while Installing performance counters. The error is: The system cannot find the file specified.Error 29528. The setup has encountered an unexpected error while Installing performance counters. The error is: The system cannot find the file specified.

You can ignore this and it will complete the installation, but subsequently trying to patch with SP2 will fail on the same sections - Hotfix.exe crashes whilst attempting to patch Database Services, Integration Services and Client Components (3 separate crashes).

I've removed SQL Server 2005 elements and tried to re-install, but it's not improved the situation.

Any ideas?

View 3 Replies View Related

Personal SQL Server

Feb 4, 2000

Does anyone know about a product called "Personal SQL Server" or similar, which would provide your the services of SQL Server, but running on W95, 98 or NT? Is it included in Backoffice Server? Where can I get it? Is it there a demo available?

Thank you.

Alvaro de León

View 1 Replies View Related

Upgrading SQL Personal ED -&&> SQL Std

May 4, 2006

I am currently runing SQL Server 200 (personal edition) and I need to upgrade to SQL SVR Standard Edtion. Do I need to uninstall the personal edition first? Or can I install over it?

Thank You!

View 1 Replies View Related

Personal Edition?

Jul 10, 2006

What are the main differences with personal edition compared to standard edition?

Will be grateful for answers!

Regards,
Marius

View 1 Replies View Related

Deploying The Personal Web Site

May 15, 2007

Rank newbie to ASP.NET here, so I'm totally "at sea" as to finding a "cookbook" for "how to deploy" a slightly customized version of the "Personal Web Site" project.
My hosting service has an ASP.NET database installed. I can verify from their "SQL Server Web Admin" package that there are 11 "aspnet_" table names present. I have run the "personal-add.sql" script which has defined two (empty) tables -- "Albums" and "Photos".
CONFUSION 1: The hosting service includes a Help fille for "Connecting to a SQL Server Database Using ASP.NET 2.0" which details the way to add 'connectionStrings' for "Personal" and "LocalSqlServer". I have made a "remote" copy of the "web.config" file and supplied the ostensively correct info for my Server, Database, User ID and Password. QUESTION: Why are there TWO names -- "Personal" and "LocalSqlServer"? Since all of the tables are contained now within the ASP.NET database are the details for both of these to be the same?
CONFUSION 2: Error handling. I'm getting "An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine." Huh!? That page then goes on to mention "<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>". I've not a clue as to what "mycustompage.htm" should contain in order to field the error[s] erupting.
POINTERS, anyone? Have I missed some basic part of the manual[s] someplace? I was sort of hoping that there would be a simple "cookbook" around someplace for how to "deploy" a relatively tested group of pages (application) in a relatively idiot-proof manner. I'm not finding it, so ANY pointers, hints, URLs will be greatly appreciated.
Color me "confused in Kauai" ... :)  KevInKauai

View 2 Replies View Related

Is It Possible To Migrate From Personal To Standard ?

Jun 18, 2002

is it possible to migrate from personal to standard without reinstalling server ?

View 2 Replies View Related

SQL 2000 Personal Editon And XP Pro

Feb 12, 2004

I just installed SQL 2000 personal edition on a win xp pro box and now when it boots I get a SQL service manager error that says service manager has generated errors and needs to be closed.

Is there anything particular with XP and SQL 2000 i need to know?

I thought this would be a no brainer as it was with Win2k, but no.

MD, MCSA/MCSE WIN2K

View 2 Replies View Related

SQL Server Personal Ed - Licencing?

Feb 27, 2004

I just found that one of the SQL Servers I support shows it is 'SQL Server 2000 Personal Edition'. I've checked and there is a spare SQL Server 2000 Standard Edition' licence in the organisation.

Do I need to re-install SQL Server 2000 with the correct media so that it shows 'Standard Edition' in the SQL Server properties? Or is it ok just to leave Personal Edition on there?

Clive

View 1 Replies View Related

SQL Server Personal Edition

Mar 31, 2004

Does anyone have any pointers on where I can find out exactly what we're allowed to do with this product? For example, we sell systems based on Microsoft Small Business Server 2000, which includes SQL Server standard edition. If I want to have, say, a branch system which replicates data to the main SBS system, but run it on XP Pro and use a couple of PCs for workstations, can I use SQL PE, or do I have to use SBS on the branch as well? What about if I have two branches? Or five? Does the fact that we're using SBS make any difference? At the moment, where possible, our branch in that scenario might use the MSDE, but that is limited to a 2Gb database which isn't always useful.

Your thoughts would be most welcome. The Microsoft web site doesn't specifically say what we can and cannot do here, or if it does I haven't found it yet. We're in the UK, if that affects licensing information.

View 3 Replies View Related

Installing Personal Edition On NT4 Wkstn

Jul 23, 2002

The rap from Microsoft is that "SQL Server 2000 Personal Edition is not a separate product but rather a client component of SQL Server 2000 (included as part of the Enterprise and Standard Editions) that is designed to bring SQL Server 2000 functionality to non-server hardware, including workstations and laptops."

I have a copy of SQL2K Standard, but when I try to install it on a workstation it tells me it'll install client tools only. I've searched Microsoft and don't see any downloads for SQL2K PE.

I need the server component on an NT4 Workstation; what's the trick in getting PE installed on an NT4 Workstation?

Al

View 1 Replies View Related

Personal Edition Then Move To Enterprise

Jul 23, 2005

Hello,Could i start work with personal edition then move all data toenterprise edition ? i've to design and code on workgroup environmentthen implement to windows server 2003. Do i just cut & paste data ?TIAPong

View 1 Replies View Related

Path To A Personal Knowledge Database

Jul 20, 2005

Greetings,I have to admit that I'm still a beginner in the database field, but I'mactively studying, and this is why I will be utterly grateful for theproper, accurate, and wise guidance to the right direction or specificpaths of database studies.I simply want to make my first major database project a "personalknowledge database" or a "personal encyclopedia", so to speak. By this Imean that I want to gather diverse, multi-format bits of knowledge intoa single database divided into major categories, sub-categories, and soon. For example, I want to scan collected articles from newspapers &magazine and save them as images, type hand-written notes into thecomputer and save them as MS Word or Text files, save audio files withsearchable keywords, even save searchable MS OneNote audio & text files,all into directories & sub-directories. Then I want to be able to searchall these files for specific words or subjects; sort them according todate, subject, etc; update, add to or append, edit, or even cut & paste(within) any of those records in the database, which rely on easilycustomizable formats like text & images (in contrast with audio files orOneNote files, for example).I also want to prevent wasting time in the future, by avoidingrepetitive, same-keywords typing for every non-text new entry, like animage or audio file, by having a customizable keyword list open (byright clicking for example), where one could mark all the relevantkeywords for the picture or audio file. Also have a short descriptionfor each one of those entries when needed. And I want to be able to addslick, good-looking graphics to the interface of the database and theforms of the records.Basically, my priorities include: saving time filling the database withknowledge, quickly & accurately finding the future targets of anysearch, presenting the search results in a highly comprehensible &organized form, and a good looking interface & forms for every entry,which are pleasing to the eye and encouraging to study.I already use graphics applications for the "looks" part. So my questionis: what are the technologies or applications that I should learn byheart and use in order to design such a database in the best way? WouldMS Access alone do it all for me? Or should I learn other technologies?I'll be grateful for anyone taking the time to help. Thanks.Sincerely,Yasso"Claiming that God does not exist because there are people suffering anddying is like saying that barbers do not exist because there are peoplewith long hair! Truth is: they suffer because they did not find God ordo not go to Him, just like the others did not find a barber or do notgo to one."*** Sent via Developersdex http://www.developersdex.com ***Don't just participate in USENET...get rewarded for it!

View 1 Replies View Related

Deployment Of SQL 2000 Server Personal

Mar 28, 2008



Hi everyone,

I would like to know how I can deploy Microsoft SQL 2000 Server Personal edition using SMS 2003 Sp2.

When I map a drive and I execute my batch file it install SQL 2000 correctly but when I try to deploy SQL 2000 server personal edition using SMS 2003, It said that I deployed successfully sql 2000 server but when I look into my client computer, it didn't install SQL so this is the problem I have.

anyone can help me?

Best regards

View 1 Replies View Related

SQL Server 2000 Personal Edition

Feb 6, 2008

One of my clients has an application that only requires €œSQL Server 2000 Personal Edition€? (the new versions of SQL are not supported). Tried going to Microsoft€™s download center to get €œSQL Server 2000 Personal Edition€?, but all I found were the service packs. I also talked to the client about getting an updated version of the application he is using, but it is not cost effective. Does anyone know where I can get/buy a copy of €œSQL Server 2000 Personal Edition€?? Thanks for your help and time.

View 1 Replies View Related

SQL Server 2000 Personal Edition

Nov 20, 2007

Hi,
May i know whether SQL Server 2000 Personal Edition is a freeware?
If i install it with the Analysis Services, will it still be considered as freeware?
Thank you.

Regards,
Chong

View 1 Replies View Related

Update SQL Personal Edition Service Pack 3

Dec 7, 2004

Please do not tell me to go to the MS site coz I did not see any helpful step by step how to install this service pack to my SQL Personal Edition. So please anyone, SQL Guru, post here how to install the SP3 for PERSONAL EDITION - not the DESKTOP Engine. Thank you so much...

View 3 Replies View Related

Networking With Personal Edition Sql Server 2000

Apr 26, 2002

I am using the personal edition of sql server 2000 and i have a number of databases stored on the harddrive, how would i set up a connection with other PC's to be able to view/modify/delete the data through an access 2000 front end. The other PC's will not have SQL server on them but will have Access 2000, they will need to go via the network which is non-microsoft compliant.

Thank you very much for you help it would be very much appreciated.

Britta

View 1 Replies View Related

DB Design :: Normalizing Personal Contact Information

May 22, 2015

I have a large data set with 10s of millions of rows of contact information.  The data is in CSV format and contains 48 columns of information (First name, MI, last name, 4 part address, 10+ demographic points, etc.) and I'm struggling with how I should design the database and normalize this data, or if I should normalize this data.

My 2 thoughts for design were either:

Break the columns into logical categorical tables (i.e. BasicContactInfo, Demographics, Financials, Interests, etc.) Keep the entire row in one table, and pull out the "Objects" into another table (i.e. ContactInformation, States, ZIPCodes, EmployementStatus, EthnicityCodes, etc.)

The data will be immutable for the most part, and when I get new data, I'll just create a new database and replace the old one.

The reason I like option 1 is because it makes importing easier, since I can just insert the appropriate columns from each row into the appropriate tables.  Option number 2 feels like it would be faster to get metrics on the data, like how many contacts live in which states, or what is the total number of unique occupations in the data set.  Plus I'll be able to make relationships between the tables, like which state is tied to which zipcode, which city is tied with which county, etc.  Importing that data might be more tricky, since I don't think SQL Bulk Copy will allow for inserting into normalized tables like that.

The primary use for this data is to allow our sales force to create custom lists of contact information based on a faceted search page.  The sales person would create the filter, and then I will provide them with the resulting data so they can start making business contacts.  Search performance needs to be good.  Insert, update, and deletes won't happen once the data has been imported.

What should I look for in designing this database?  Any good articles on designing tables around wide data sets like my contact information? 

View 6 Replies View Related

How To Send Mail To A Personal Distribution List (PDL) ?

Jul 27, 2007

Hi friends,
Though we can send mails to Individual addresses, I wonder what would be the Syntax to specify in the script task or Format to specify in a "To" Property of Send Mail task that I use to Send a mail to my Personal Distribution List (PDL).

Thanks
Subhash Subramanyam

View 9 Replies View Related

Connection Problem, MS Personal Website Starter Kit

Mar 18, 2007

I have had a local Website up and running based on the MS Personal Website Starter Kit using Visual Studio 2005 Professional and SQL Server Express.

I am now trying to get the databases to run on SQL Server 2005 Standard Edition but can't get the connection to work.

I have changed the connection string in the Web.Config file from:

connectionString="Data Source=.SQLExpress;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Personal.mdf" providerName="System.Data.SqlClient"

To

connectionString="Data Source=.scastle;Integrated Security=True;User Instance=True;AttachDBFilename=|DataDirectory|Personal.mdf" providerName="System.Data.SqlClient"

But am getting the following error:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

Source Error:





Line 5: Sub Application_Start(ByVal sender As [Object], ByVal e As EventArgs)
Line 6: AddHandler SiteMap.SiteMapResolve, AddressOf Me.AppendQueryString
Line 7: If (Roles.RoleExists("Administrators") = False) Then
Line 8: Roles.CreateRole("Administrators")
Line 9: End If

I am able to connect OK in both Server Management Studio (Server Name: SCastle, Windons Authentication) and clicking Connect to Database in Server Manager in Visual Studio (Server Name: (local)).

Have I got the connection string wrong or do I need to set up additional permissions in the database?

Thanks for your help.

Stephen



View 6 Replies View Related

Problem In Installing SQL Server 2000 Personal

Aug 23, 2007

Hi... I recently reformatted my pc due to a very slow operation. Then I reinstall SQL Server 2000 Personal to my PC running Windows XP OS....As I run the setup, it will display INTERNAL ERROR and won't continue... What seemed to be the problem there? Before I reformatted the PC, it was installed well...

View 6 Replies View Related

Installing SQL Server 2000 Personal Edition On Windows XP SP1

Jul 20, 2005

I have a need to become familiar with SQL Server 2000 for work.Needless to say I am new to SQL Server any version, but not IT ingeneral. My employer has provided me with the SQL Server 2000Personal disk from the SQL Server 2000 Enterprise kit as this isreported here on the MSDN web site to be the version that is supportedon Windows XP. In fact so many of you kind people confess to havingsucceeded in doing it.I have tried several installs using various custom componentcombinations as well as the default "typical" install.All start of trying to install the MDAC component, then after severalminutes display a dialog with the following text:"The software you are installing has not passed Windows Logo testingto verify its compatibility with Windows XP. The software will not beinstalled. Contact your system administrator"Before anyone asks, yes I am logged on as the administrator of theWindows XP machine.The setup program then displays a dialog with the following text:"Installation of the Microsoft Data Access Components package failed.(-1)"Setup then shuts down and the PC needs to be restarted before the SQLServer setup can be run again.For the techos that might have an insight, I have included detailsfrom the following logs below. SQL.MIF, SQLSTP.LOG, DASETUP.LOGSETUPAPI.LOG.Any ideas will be appreciated. Thank you.Only the log files follow from here.DASETUP.LOG: ****************************************: * Beginning of Install *: ****************************************Starting Install: Current Date/Time (U.S. Local Time): 09/07/2003 :18:25:09Path: C:Windows;C:WindowsSystem32;Localization: Machine Locale set to: English_Australia.1252Command Line Parameters:Suppress Reboot: 0Quiet/Silent Mode: 1Logging Level: 3Windows Directory: C:WindowsProgress: Loading Resource Library.Progress: Parsing INI File.*************************:** Begin INI File Dump **:*************************:Ini Section: General: ProductName = Microsoft Data Access Components 2.6: ProductBuild = 2.60.6526.2: ProductUrl = http://www.microsoft.com/data: ProductVersionKey = SOFTWAREMicrosoftDataAccess: ProductVersionValue = FullInstallVer: InstanceName = MDAC: CheckInUseFiles = 1: EULAFile = MDACEULA.RTF: EULAType = rtf: BackupSize = 10: InstallSize = 20: SupportsTS = 1: SupportsMUI = 0: CheckForDiskSpace = 1: ValidOs = 4294967295Ini Section: Packages: A = SETUP_LIBS: B = C_RUNTIME_LIBS: C = MTX_FILES: D = SETUP_RSP_FILES: E = DASETUP_FILES: F = WDSETUP_DOWNLEVEL: G = WDSETUP_MILLENNIUM: H = WDSETUP_W2K_MIGRATION: I = MDAC_DOWNLEVEL: J = MDAC_MILLENNIUM: K = MDAC_W2K_MIGRATION: L = MSXML_FILES: M = SQLXMLX: N = SQLNET_DOWNLEVEL: O = SQLNET_MILLENNIUM: P = SQLNET_W2K_MIGRATION: Q = SQLODBC_DOWNLEVEL: R = SQLODBC_MILLENNIUM: S = SQLODBC_W2K_MIGRATION: T = SQLOLEDB_DOWNLEVEL: U = SQLOLEDB_MILLENNIUM: V = SQLOLEDB_W2K_MIGRATION: W = JET_FILES: X = NEW_MUI_ENGINE: Y = REG_MDAC_VERSIONIni Section: SETUP_LIBS: Name = Microsoft Setup Libraries: ComponentName = SETUP_LIBS: Dependencies =: InstallType = inf: CabFile = setupapi.cab: InfFile = setupapi.inf: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd =: ExtractCab = 1: UseRollback = 0: RebootAfter = 0: ValidOs = 3Ini Section: C_RUNTIME_LIBS: Name = Microsoft C/C++ Runtime Libraries: ComponentName = C_RUNTIME_LIBS: Dependencies =: InstallType = inf: CabFile = msvcrt.cab: InfFile = msvcrt.inf: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd =: ExtractCab = 0: UseRollback = 0: RebootAfter = 0: ValidOs = 7Ini Section: MTX_FILES: Name = MTX System Files: ComponentName = MTX_FILES: Dependencies =: InstallType = inf: CabFile = mtxfiles.cab: InfFile = mtxfiles.inf: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd =: ExtractCab = 0: UseRollback = 0: RebootAfter = 0: ValidOs = 7Ini Section: DASETUP_FILES: Name = MDAC Setup Files: ComponentName = DASETUP: Dependencies =: InstallType = inf: CabFile =: InfFile = dasetup.inf: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd =: ExtractCab = 0: UseRollback = 0: RebootAfter = 0: ValidOs = 4294967295Ini Section: SETUP_RSP_FILES: Name = MDAC Setup Response Files: ComponentName = SETUP_RSP_FILES: Dependencies =: InstallType = inf: CabFile =: InfFile = rspfiles.inf: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd =: ExtractCab = 0: UseRollback = 0: RebootAfter = 0: ValidOs = 4294967295Ini Section: WDSETUP_DOWNLEVEL: Name = WebData Setup Files: ComponentName = WDSETUP: Dependencies =: InstallType = inf: CabFile = WDSETUP.CAB: InfFile = WDSET_DL.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd =: ExtractCab = 0: UseRollback = 0: RebootAfter = 0: ValidOs = 7Ini Section: WDSETUP_MILLENNIUM: Name = WebData Setup Files: ComponentName = WDSETUP: Dependencies =: InstallType = inf: CabFile = WDSETUP.CAB: InfFile = WDSETUPM.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd =: ExtractCab = 0: UseRollback = 0: RebootAfter = 0: ValidOs = 16Ini Section: WDSETUP_W2K_MIGRATION: Name = WebData Setup Files: ComponentName = WDSETUP: Dependencies =: InstallType = xpak: CabFile = WDSETUP.CAB: InfFile = WDSETUP.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd =: ExtractCab = 0: UseRollback = 0: RebootAfter = 0: ValidOs = 12Ini Section: MDAC_DOWNLEVEL: Name = Microsoft Data Access Components: ComponentName = MDAC_CORE: Dependencies = C_RUNTIME_LIBS,MTX_FILES,WDSETUP: InstallType = inf: CabFile = MDACXPAK.CAB: InfFile = MDACXPDL.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd = %11%odbcconf.exe /S /Lv odbcconf.log /F%11%mdaccore.rsp: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 7Ini Section: MDAC_MILLENNIUM: Name = Microsoft Data Access Components: ComponentName = MDAC_CORE: Dependencies = C_RUNTIME_LIBS,MTX_FILES,WDSETUP: InstallType = inf: CabFile = MDACXPAK.CAB: InfFile = MDACXPKM.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd = %11%odbcconf.exe /S /Lv odbcconf.log /F%11%mdaccore.rsp: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 16Ini Section: MDAC_W2K_MIGRATION: Name = Microsoft Data Access Components: ComponentName = MDAC_CORE: Dependencies = C_RUNTIME_LIBS,MTX_FILES,WDSETUP: InstallType = xpak: CABFile = MDACXPAK.CAB: InfFile = MDACXPAK.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd = %11%odbcconf.exe /S /Lv odbcconf.log /F%11%mdaccore.rsp: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOS = 12Ini Section: MSXML_FILES: Name = Microsoft XML Parser: ComponentName = MSXML: Dependencies =: InstallType = inf: CabFile = MSXML.cab: InfFile = MSXML.inf: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd =: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 31Ini Section: SQLXMLX: Name = XML Extensions for Microsoft OLE DB Provider for SQL Server: ComponentName = SQLXMLX: Dependencies = WDSETUP,MDAC_CORE,MSXML: InstallType = inf: CabFile = SQLXMLX.cab: InfFile = SQLXMLX.inf: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd =: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 31Ini Section: SQLNET_DOWNLEVEL: Name = Microsoft SQL Server Network Libraries: ComponentName = SQLNET: Dependencies =: InstallType = inf: CabFile = SQLNET.CAB: InfFile = SQLNETDL.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd =: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 7Ini Section: SQLNET_MILLENNIUM: Name = Microsoft SQL Server Network Libraries: ComponentName = SQLNET: Dependencies =: InstallType = inf: CabFile = SQLNET.CAB: InfFile = SQLNETM.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd =: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 16Ini Section: SQLNET_W2K_MIGRATION: Name = Microsoft SQL Server Network Libraries: ComponentName = SQLNET: Dependencies =: InstallType = xpak: CabFile = SQLNET.CAB: InfFile = SQLNET.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd =: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 31Ini Section: SQLOLEDB_DOWNLEVEL: Name = Microsoft SQL Server OLE DB Provider: ComponentName = SQLOLEDB: Dependencies = MDAC_CORE,SQLXMLX,SQLNET: InstallType = inf: CabFile = SQLOLDB.CAB: InfFile = SQLOL_DL.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd =: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 7Ini Section: SQLOLEDB_MILLENNIUM: Name = Microsoft SQL Server OLE DB Provider: ComponentName = SQLOLEDB: Dependencies = MDAC_CORE,SQLXMLX,SQLNET: InstallType = inf: CabFile = SQLOLDB.CAB: InfFile = SQLOLDBM.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd =: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 16Ini Section: SQLOLEDB_W2K_MIGRATION: Name = Microsoft SQL Server OLE DB Provider: ComponentName = SQLOLEDB: Dependencies = MDAC_CORE,SQLXMLX,SQLNET: InstallType = xpak: CabFile = SQLOLDB.CAB: InfFile = SQLOLDB.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd =: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 31Ini Section: SQLODBC_DOWNLEVEL: Name = Microsoft SQL Server ODBC Driver: ComponentName = SQLODBC: Dependencies = WDSETUP,SQLNET: InstallType = inf: CabFile = SQLODBC.CAB: InfFile = SQLOD_DL.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd = %11%odbcconf.exe /S /Lv odbcconf.log /F%11%sqlclnt.rsp: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 7Ini Section: SQLODBC_MILLENNIUM: Name = Microsoft SQL Server ODBC Driver: ComponentName = SQLODBC: Dependencies = WDSETUP,SQLNET: InstallType = inf: CabFile = SQLODBC.CAB: InfFile = SQLODBCM.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd = %11%odbcconf.exe /S /Lv odbcconf.log /F%11%sqlclnt.rsp: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 16Ini Section: SQLODBC_W2K_MIGRATION: Name = Microsoft SQL Server ODBC Driver: ComponentName = SQLODBC: Dependencies = WDSETUP,SQLNET: InstallType = xpak: CabFile = SQLODBC.CAB: InfFile = SQLODBC.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd = %11%odbcconf.exe /S /Lv odbcconf.log /F%11%sqlclnt.rsp: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 31Ini Section: JET_FILES: Name = Jet Expression Service and String Sorting Libraries: ComponentName = JET: Dependencies =: InstallType = inf: CabFile = JETFILES.cab: InfFile = JETFILES.inf: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall.NT: PostInstallCmd =: ExtractCab = 0: UseRollback = 1: RebootAfter = 0: ValidOs = 7Ini Section: NEW_MUI_ENGINE: Name = Microsoft MUI Setup Engine: ComponentName = NEWMUI: Dependencies =: InstallType = inf: CabFile = NEWMUI.CAB: InfFile = NEWMUI.INF: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd =: ExtractCab = 0: UseRollback = 0: RebootAfter = 0: ValidOs = 8Ini Section: REG_MDAC_VERSION: Name = Microsoft Data Access Components: ComponentName = REG_MDAC_VERSION: Dependencies = MDAC_CORE,WDSETUP,MSXML,SQLXMLX,SQLNET,SQLOLEDB,SQ LODBC: InstallType = inf: CabFile =: InfFile = noop.inf: InstallSection = DefaultInstall: InstallSection.NT = DefaultInstall: PostInstallCmd = %11%odbcconf.exe /S /Lv odbcconf.log /F%11%
edist.rsp: ExtractCab = 0: UseRollback = 0: RebootAfter = 0: ValidOs = 31*************************:** End INI File Dump **:*************************:Progress: Loading EULA.Progress: Loading Strings.Debug: Loaded string resource: 13. Characters = 8Windows Version:Major Version: 5Minor Version: 0Windows NT: 1SP Level: 1Terminal Services: 0Progress: Loading Setup Engine Library.Entering function: LoadAdvPack()Parameters:*phInstance = 0x00000000pAdvPackLib = 0x0013EEF0Exiting function: LoadAdvPack()Return value: (BOOL) 1Progress: Loading ODBCConf Library.Entering function: LoadODBCConf()Parameters:*phInstance = 0x00000000pODBCConfLib = 0x0013EEFCExiting function: LoadODBCConf()Return value: (BOOL) 1IE Version:IE 6.00 and greaterVerifying System Language: The system LCID and the LCID of the setupresource DLL do not match.Entering function: BuildJobList()Parameters:pContext = 0x0013EEE4Entering function: CJob::InitializeJobQueues()Parameters:hHive = 0x80000002szRoot = ???????????????spContext = 0x%08XExiting function: CJob::InitializeJobQueues()Return value: (HRESULT) 0x00000000Exiting function: BuildJobList()Return value: (HRESULT) 0x00000000Progress: Creating Setup Wizard.Creating Wizard Page: 0Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 1Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 2Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 3Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 4Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 5Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Debug: Loaded string resource: 10. Characters = 104Creating Wizard Page: 6Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 7Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 8Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 9Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 10Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 11Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 12Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 13Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard Page: 14Debug: Loaded string resource: 1. Characters = 10Debug: Loaded string resource: 2. Characters = 129Creating Wizard: Microsoft Data Access Components 2.6 SetupProgress: Running in Silent Mode. Suppressing UIChecking for disk space: Drive C: requires 12316672 bytes, there are17936592896 bytes available.Detecting in-use files: Setup is checking for in-use files.Detecting in-use files: Start time: 08:25:12:25Detecting in-use files: Setup has detected a locked file:C:WindowsSystem32odbc32.dllDetecting in-use files: Setup has detected a locked file:C:WindowsSystem32odbcint.dllDetecting in-use files: Finished building filelist. CheckPoint time:08:25:15:259Detecting in-use files: Process requires reboot: winlogon.exe, ProcessID 600 (System Process: 1)Detecting in-use files: Process requires reboot: WINDOWS, Process ID556 (System Process: 1)Detecting in-use files: Process requires reboot: Program Manager,Process ID 556 (System Process: 1)Detecting in-use files: End time: 08:25:15:900Detecting in-use files: Elapsed time: 00:00:03:875Detecting in-use files: In-use file check complete.Progress: Running in Silent Mode. Starting Install...Entering function: InstallPackages()Parameters:hWnd = 0x00000000pContext = 0x0013EEE4hMessageTarget = 0x00000000pParam = 0x00000000bAsync = 0Entering function: InstallPackagesThread()Parameters:pParam = 0x009C29C0Entering function: CJob::InitializeJobQueues()Parameters:hHive = 0x80000002szRoot = ???????????????spContext = 0x%08XExiting function: CJob::InitializeJobQueues()Return value: (HRESULT) 0x00000000Debug: Loaded string resource: 3. Characters = 21Debug: Loaded string resource: 5. Characters = 14Entering function: ExecuteInstall()Parameters:nDirective = 1hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMP
spfiles.infpwcsCabFile = (null)pwcsSection = DefaultInstall.NTpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 4pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x00000000Debug: Loaded string resource: 3. Characters = 21Debug: Loaded string resource: 5. Characters = 14Entering function: ExecuteInstall()Parameters:nDirective = 1hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMPdasetup.infpwcsCabFile = (null)pwcsSection = DefaultInstall.NTpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 4pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x00000000Debug: Loaded string resource: 3. Characters = 21Debug: Loaded string resource: 5. Characters = 14Entering function: ExecuteInstall()Parameters:nDirective = 4hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMPWDSETUP.INFpwcsCabFile = (null)pwcsSection = DefaultInstallpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 4pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x01000003Debug: Loaded string resource: 3. Characters = 21Debug: Loaded string resource: 5. Characters = 14Entering function: ExecuteInstall()Parameters:nDirective = 4hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMPMDACXPAK.INFpwcsCabFile = (null)pwcsSection = DefaultInstallpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 36pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x00000BC2Reboot Required: Job number 4 requires rebootDebug: Loaded string resource: 3. Characters = 21Debug: Loaded string resource: 5. Characters = 14Entering function: ExecuteInstall()Parameters:nDirective = 1hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMPMSXML.infpwcsCabFile = (null)pwcsSection = DefaultInstall.NTpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 36pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x00000000Debug: Loaded string resource: 3. Characters = 21Debug: Loaded string resource: 5. Characters = 14Entering function: ExecuteInstall()Parameters:nDirective = 1hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMPSQLXMLX.infpwcsCabFile = (null)pwcsSection = DefaultInstall.NTpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 548pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x00000000Reboot Required: Job number 6 requires rebootDebug: Loaded string resource: 3. Characters = 21Debug: Loaded string resource: 5. Characters = 14Entering function: ExecuteInstall()Parameters:nDirective = 4hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMPSQLNET.INFpwcsCabFile = (null)pwcsSection = DefaultInstallpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 36pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x80004005Debug: Loaded string resource: 4. Characters = 23Debug: Loaded string resource: 6. Characters = 16Entering function: ExecuteInstall()Parameters:nDirective = 5hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMPSQLNET.INFpwcsCabFile = (null)pwcsSection = DefaultInstallpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 68pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x80004005Debug: Loaded string resource: 4. Characters = 23Debug: Loaded string resource: 6. Characters = 16Entering function: ExecuteInstall()Parameters:nDirective = 1hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMPSQLXMLX.infpwcsCabFile = (null)pwcsSection = DefaultInstall.NTpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 68pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x00000000Debug: Loaded string resource: 4. Characters = 23Debug: Loaded string resource: 6. Characters = 16Entering function: ExecuteInstall()Parameters:nDirective = 1hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMPMSXML.infpwcsCabFile = (null)pwcsSection = DefaultInstall.NTpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 68pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x00000BC2Reboot Required: Job number 5 requires rebootDebug: Loaded string resource: 4. Characters = 23Debug: Loaded string resource: 6. Characters = 16Entering function: ExecuteInstall()Parameters:nDirective = 5hWnd = 0x00000000pwcsInfFile = C:WINDOWSTempIXP000.TMPMDACXPAK.INFpwcsCabFile = (null)pwcsSection = DefaultInstallpwcsExtractPath = C:WINDOWSTempIXP000.TMPdwSetupFlags = 68pContext = 0x0013EEE4Exiting function: ExecuteInstall()Return value: (HRESULT) 0x00000BC2Reboot Required: Job number 4 requires rebootEntering function: CJob::DestroyJobQueues()Parameters: None.Exiting function: CJob::DestroyJobQueues()Return value: (HRESULT) 0x00000000Exiting function: InstallPackagesThread()Return value: (HRESULT) 0x00000000Exiting function: InstallPackages()Return value: (HRESULT) 0x00000000State after Install:Setup was Successful: 0Setup Requires Reboot: 0Setup Will Reboot the Machine: 0Exiting: Setup is shutting down..Ending Install: Current Date/Time (U.S. Local Time): 09/07/2003 :18:38:30Errors collection: Severity: 100, Type: 2, Code: 0x80004005, Title:(null), Text: Unspecified errorErrors collection: Severity: 100, Type: 2, Code: 0x80004005, Title:(null), Text: Unspecified errorError: The following error was encountered during setup:*** (null):Unspecified error(Severity: 100, Type: 2, Code: 0x80004005)SQL.MIFSTART COMPONENTNAME = "WORKSTATION"START GROUP NAME = "ComponentID"ID = 1CLASS = "DMTF|ComponentID|1.0"START ATTRIBUTENAME = "Manufacturer"ID = 1ACCESS = READ-ONLYSTORAGE = SPECIFICTYPE = STRING(64)VALUE = "Microsoft"END ATTRIBUTESTART ATTRIBUTENAME = "Product"ID = 2ACCESS = READ-ONLYSTORAGE = SPECIFICTYPE = STRING(64)VALUE = "Microsoft SQL Server 2000"END ATTRIBUTESTART ATTRIBUTENAME = "Version"ID = 3ACCESS = READ-ONLYSTORAGE = SPECIFICTYPE = STRING(64)VALUE = "8.00.194"END ATTRIBUTESTART ATTRIBUTENAME = "Locale"ID = 4ACCESS = READ-ONLYSTORAGE = SPECIFICTYPE = STRING(16)VALUE = ""END ATTRIBUTESTART ATTRIBUTENAME = "Serial Number"ID = 5ACCESS = READ-ONLYSTORAGE = SPECIFICTYPE = STRING(64)VALUE = ""END ATTRIBUTESTART ATTRIBUTENAME = "Installation"ID = 6ACCESS = READ-ONLYSTORAGE = SPECIFICTYPE = STRING(64)VALUE = "DateTime"END ATTRIBUTEEND GROUPSTART GROUPNAME = "InstallStatus"ID = 2CLASS = "MICROSOFT|JOBSTATUS|1.0"START ATTRIBUTENAME = "Status"ID = 1ACCESS = READ-ONLYSTORAGE = SPECIFICTYPE = STRING(32)VALUE = "Failed"END ATTRIBUTESTART ATTRIBUTENAME = "Description"ID = 2ACCESS = READ-ONLYSTORAGE = SPECIFICTYPE = STRING(128)VALUE = "Installation of the Microsoft Data Access Componentspackage failed. (-1)"END ATTRIBUTEEND GROUPEND COMPONENTSETUPAPI.LOG[2003/09/07 18:25:11 3916.11]#-199 Executing "C:WINDOWSTempIXP000.TMPdasetup.exe" with commandline: /Q:D /N#E077 Could not locate a non-empty section [DefaultInstall] whencalculating disk space in "C:WINDOWSTempIXP000.TMPoop.inf". Error0xe0000102: The required line was not found in the INF.[2003/09/07 18:25:16 3916.1]#-199 Executing "C:WINDOWSTempIXP000.TMPdasetup.exe" with commandline: /Q:D /N#E361 An unsigned or incorrectly signed file"c:windows empixp000.tmp
spfiles.inf" will be installed(Policy=Ignore). Error 1168: Element not found.#-024 Copying file "C:WINDOWSTempIXP000.TMP
spfiles.inf" to"C:Program FilesCommon FilesMicrosoft Shareddasetup
spfiles.inf".#E361 An unsigned or incorrectly signed file"C:WINDOWSTempIXP000.TMP
spfiles.inf" will be installed(Policy=Ignore). Error 1168: Element not found.#-336 Copying file "C:WINDOWSTempIXP000.TMP
edist.rsp" to"C:WindowsSystem32
edist.rsp" via temporary file"C:WindowsSystem32SET14.tmp".#E361 An unsigned or incorrectly signed file"C:WINDOWSTempIXP000.TMP
edist.rsp" will be installed(Policy=Ignore). Error 1168: Element not found.#-336 Copying file "C:WINDOWSTempIXP000.TMPmdaccore.rsp" to"C:WindowsSystem32mdaccore.rsp" via temporary file"C:WindowsSystem32SET17.tmp".#E361 An unsigned or incorrectly signed file"C:WINDOWSTempIXP000.TMPmdaccore.rsp" will be installed(Policy=Ignore). Error 1168: Element not found.#-336 Copying file "C:WINDOWSTempIXP000.TMPsqlclnt.rsp" to"C:WindowsSystem32sqlclnt.rsp" via temporary file"C:WindowsSystem32SET1A.tmp".#E361 An unsigned or incorrectly signed file"C:WINDOWSTempIXP000.TMPsqlclnt.rsp" will be installed(Policy=Ignore). Error 1168: Element not found.[2003/09/07 18:25:19 3916.1]#-199 Executing "C:WINDOWSTempIXP000.TMPdasetup.exe" with commandline: /Q:D /N#E361 An unsigned or incorrectly signed file"c:windows empixp000.tmpdasetup.inf" will be installed(Policy=Ignore). Error 1168: Element not found.#-024 Copying file "C:WINDOWSTempIXP000.TMPdasetup.inf" to"C:Program FilesCommon FilesMicrosoft Shareddasetupdasetup.inf".#E361 An unsigned or incorrectly signed file"C:WINDOWSTempIXP000.TMPdasetup.inf" will be installed(Policy=Ignore). Error 1168: Element not found.#-336 Copying file "C:WINDOWSTempIXP000.TMPdasetup.ini" to"C:Program FilesCommon FilesMicrosoft Shareddasetupdasetup.ini"via temporary file "C:Program FilesCommon FilesMicrosoftShareddasetupSET22.tmp".#E361 An unsigned or incorrectly signed file"C:WINDOWSTempIXP000.TMPdasetup.ini" will be installed(Policy=Ignore). Error 1168: Element not found.[2003/09/07 18:25:21 3916.1]#-199 Executing "C:WINDOWSTempIXP000.TMPdasetup.exe" with commandline: /Q:D /N#-340 Extracted file "ds16gt.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SETF4.tmp" (target is"C:WindowsSystem32ds16gt.dll").#-336 Copying file "C:WindowsSystem32SETF4.tmp" to"C:WindowsSystem32ds16gt.dll" via temporary file"C:WindowsSystem32SETF6.tmp".#W025 A newer file "C:WindowsSystem32ds16gt.dll" was overwritten byan older (signed) file. Version of source file: 3.510.3711.0. Versionof target file: 3.510.3711.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "ds32gt.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SETF7.tmp" (target is"C:WindowsSystem32ds32gt.dll").#-336 Copying file "C:WindowsSystem32SETF7.tmp" to"C:WindowsSystem32ds32gt.dll" via temporary file"C:WindowsSystem32SETF9.tmp".#W025 A newer file "C:WindowsSystem32ds32gt.dll" was overwritten byan older (signed) file. Version of source file: 3.520.6526.0. Versionof target file: 3.520.9030.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "msadce.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET106.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsadce.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET106.tmp" to "C:Program FilesCommonFilesSystemMSADCmsadce.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET108.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsadce.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msadcer.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET109.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsadcer.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET109.tmp" to "C:Program FilesCommonFilesSystemMSADCmsadcer.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET10B.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsadcer.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.70.7713.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msadcf.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET10C.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsadcf.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET10C.tmp" to "C:Program FilesCommonFilesSystemMSADCmsadcf.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET10E.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsadcf.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msadcfr.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET10F.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsadcfr.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET10F.tmp" to "C:Program FilesCommonFilesSystemMSADCmsadcfr.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET111.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsadcfr.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.70.7713.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msadco.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET112.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsadco.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET112.tmp" to "C:Program FilesCommonFilesSystemMSADCmsadco.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET114.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsadco.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msadcor.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET115.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsadcor.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET115.tmp" to "C:Program FilesCommonFilesSystemMSADCmsadcor.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET117.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsadcor.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.70.7713.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msadcs.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET118.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsadcs.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET118.tmp" to "C:Program FilesCommonFilesSystemMSADCmsadcs.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET11A.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsadcs.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msadds.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET11B.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsadds.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET11B.tmp" to "C:Program FilesCommonFilesSystemMSADCmsadds.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET11D.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsadds.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msaddsr.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET11E.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsaddsr.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET11E.tmp" to "C:Program FilesCommonFilesSystemMSADCmsaddsr.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET120.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsaddsr.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.70.7713.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msader15.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemADOSET121.tmp" (target is "C:Program FilesCommonFilesSystemADOmsader15.dll").#-336 Copying file "C:Program FilesCommonFilesSystemADOSET121.tmp" to "C:Program FilesCommonFilesSystemADOmsader15.dll" via temporary file "C:ProgramFilesCommon FilesSystemADOSET123.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemADOmsader15.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.70.7713.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msado15.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemADOSET124.tmp" (target is "C:Program FilesCommonFilesSystemADOmsado15.dll").#-336 Copying file "C:Program FilesCommonFilesSystemADOSET124.tmp" to "C:Program FilesCommonFilesSystemADOmsado15.dll" via temporary file "C:ProgramFilesCommon FilesSystemADOSET126.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemADOmsado15.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msado20.tlb" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemADOSET127.tmp" (target is "C:Program FilesCommonFilesSystemADOmsado20.tlb").#-336 Copying file "C:Program FilesCommonFilesSystemADOSET127.tmp" to "C:Program FilesCommonFilesSystemADOmsado20.tlb" via temporary file "C:ProgramFilesCommon FilesSystemADOSET129.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemADOmsado20.tlb" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msado21.tlb" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemADOSET12A.tmp" (target is "C:Program FilesCommonFilesSystemADOmsado21.tlb").#-336 Copying file "C:Program FilesCommonFilesSystemADOSET12A.tmp" to "C:Program FilesCommonFilesSystemADOmsado21.tlb" via temporary file "C:ProgramFilesCommon FilesSystemADOSET12C.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemADOmsado21.tlb" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msado25.tlb" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemADOSET12D.tmp" (target is "C:Program FilesCommonFilesSystemADOmsado25.tlb").#-336 Copying file "C:Program FilesCommonFilesSystemADOSET12D.tmp" to "C:Program FilesCommonFilesSystemADOmsado25.tlb" via temporary file "C:ProgramFilesCommon FilesSystemADOSET12F.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemADOmsado25.tlb" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msadomd.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemADOSET130.tmp" (target is "C:Program FilesCommonFilesSystemADOmsadomd.dll").#-336 Copying file "C:Program FilesCommonFilesSystemADOSET130.tmp" to "C:Program FilesCommonFilesSystemADOmsadomd.dll" via temporary file "C:ProgramFilesCommon FilesSystemADOSET132.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemADOmsadomd.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msador15.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemADOSET133.tmp" (target is "C:Program FilesCommonFilesSystemADOmsador15.dll").#-336 Copying file "C:Program FilesCommonFilesSystemADOSET133.tmp" to "C:Program FilesCommonFilesSystemADOmsador15.dll" via temporary file "C:ProgramFilesCommon FilesSystemADOSET135.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemADOmsador15.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msadox.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemADOSET136.tmp" (target is "C:Program FilesCommonFilesSystemADOmsadox.dll").#-336 Copying file "C:Program FilesCommonFilesSystemADOSET136.tmp" to "C:Program FilesCommonFilesSystemADOmsadox.dll" via temporary file "C:ProgramFilesCommon FilesSystemADOSET138.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemADOmsadox.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msadrh15.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemADOSET139.tmp" (target is "C:Program FilesCommonFilesSystemADOmsadrh15.dll").#-336 Copying file "C:Program FilesCommonFilesSystemADOSET139.tmp" to "C:Program FilesCommonFilesSystemADOmsadrh15.dll" via temporary file "C:ProgramFilesCommon FilesSystemADOSET13B.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemADOmsadrh15.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "mscpxl32.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET13C.tmp" (target is"C:WindowsSystem32mscpxl32.dll").#-336 Copying file "C:WindowsSystem32SET13C.tmp" to"C:WindowsSystem32mscpxl32.dll" via temporary file"C:WindowsSystem32SET13E.tmp".#W025 A newer file "C:WindowsSystem32mscpxl32.dll" was overwrittenby an older (signed) file. Version of source file: 3.511.3.20. Versionof target file: 3.520.7713.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "msdadc.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET13F.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdadc.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET13F.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdadc.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET141.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdadc.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdaenum.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET142.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdaenum.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET142.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdaenum.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET144.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdaenum.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdaer.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET145.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdaer.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET145.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdaer.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET147.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdaer.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdaora.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET148.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdaora.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET148.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdaora.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET14A.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdaora.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdaosp.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET14B.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdaosp.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET14B.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdaosp.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET14D.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdaosp.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdaprsr.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET14E.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsdaprsr.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET14E.tmp" to "C:Program FilesCommonFilesSystemMSADCmsdaprsr.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET150.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsdaprsr.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.70.7713.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msdaprst.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET151.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsdaprst.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET151.tmp" to "C:Program FilesCommonFilesSystemMSADCmsdaprst.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET153.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsdaprst.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msdaps.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET154.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdaps.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET154.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdaps.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET156.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdaps.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdarem.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET157.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsdarem.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET157.tmp" to "C:Program FilesCommonFilesSystemMSADCmsdarem.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET159.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsdarem.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msdaremr.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET15A.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsdaremr.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET15A.tmp" to "C:Program FilesCommonFilesSystemMSADCmsdaremr.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET15C.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsdaremr.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.70.7713.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msdart.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET15D.tmp" (target is"C:WindowsSystem32msdart.dll").#-336 Copying file "C:WindowsSystem32SET15D.tmp" to"C:WindowsSystem32msdart.dll" via temporary file"C:WindowsSystem32SET15F.tmp".#W025 A newer file "C:WindowsSystem32msdart.dll" was overwritten byan older (signed) file. Version of source file: 2.60.6526.0. Versionof target file: 2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored.The existing target file was signed.#-340 Extracted file "msdasc.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET163.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdasc.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET163.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdasc.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET165.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdasc.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdasql.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET166.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdasql.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET166.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdasql.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET168.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdasql.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdasqlr.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET169.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdasqlr.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET169.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdasqlr.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET16B.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdasqlr.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.70.7713.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdatl3.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET16C.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdatl3.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET16C.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdatl3.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET16E.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdatl3.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdatsrc.tlb" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET16F.tmp" (target is"C:WindowsSystem32msdatsrc.tlb").#-336 Copying file "C:WindowsSystem32SET16F.tmp" to"C:WindowsSystem32msdatsrc.tlb" via temporary file"C:WindowsSystem32SET171.tmp".#W025 A newer file "C:WindowsSystem32msdatsrc.tlb" was overwrittenby an older (signed) file. Version of source file: 9.0.6526.0. Versionof target file: 9.0.9030.0. The SP_COPY_FORCE_NEWER flag was ignored.The existing target file was signed.#-340 Extracted file "msdatt.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET172.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdatt.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET172.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdatt.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET174.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdatt.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdaurl.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET175.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsdaurl.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET175.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsdaurl.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET177.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsdaurl.dll" was overwritten by an older (signed) file. Version ofsource file: 9.1.6526.0. Version of target file: 9.1.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "msdfmap.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemMSADCSET178.tmp" (target is "C:Program FilesCommonFilesSystemMSADCmsdfmap.dll").#-336 Copying file "C:Program FilesCommonFilesSystemMSADCSET178.tmp" to "C:Program FilesCommonFilesSystemMSADCmsdfmap.dll" via temporary file "C:ProgramFilesCommon FilesSystemMSADCSET17A.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemMSADCmsdfmap.dll" was overwritten by an older (signed)file. Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msjro.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemADOSET17D.tmp" (target is "C:Program FilesCommonFilesSystemADOmsjro.dll").#-336 Copying file "C:Program FilesCommonFilesSystemADOSET17D.tmp" to "C:Program FilesCommonFilesSystemADOmsjro.dll" via temporary file "C:ProgramFilesCommon FilesSystemADOSET17F.tmp".#W025 A newer file "C:Program FilesCommonFilesSystemADOmsjro.dll" was overwritten by an older (signed) file.Version of source file: 2.60.6526.0. Version of target file:2.71.9030.0. The SP_COPY_FORCE_NEWER flag was ignored. The existingtarget file was signed.#-340 Extracted file "msorcl32.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET183.tmp" (target is"C:WindowsSystem32msorcl32.dll").#-336 Copying file "C:WindowsSystem32SET183.tmp" to"C:WindowsSystem32msorcl32.dll" via temporary file"C:WindowsSystem32SET185.tmp".#W025 A newer file "C:WindowsSystem32msorcl32.dll" was overwrittenby an older (signed) file. Version of source file: 2.573.6526.0.Version of target file: 2.573.9030.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "msxactps.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET186.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBmsxactps.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET186.tmp" to "C:Program FilesCommon FilesSystemOLEDBmsxactps.dll" via temporary file "C:Program FilesCommonFilesSystemOLE DBSET188.tmp".#W025 A newer file "C:Program FilesCommon FilesSystemOLEDBmsxactps.dll" was overwritten by an older (signed) file. Version ofsource file: 2.60.6526.0. Version of target file: 2.71.9030.0. TheSP_COPY_FORCE_NEWER flag was ignored. The existing target file wassigned.#-340 Extracted file "odbc16gt.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET199.tmp" (target is"C:WindowsSystem32odbc16gt.dll").#-336 Copying file "C:WindowsSystem32SET199.tmp" to"C:WindowsSystem32odbc16gt.dll" via temporary file"C:WindowsSystem32SET19B.tmp".#W025 A newer file "C:WindowsSystem32odbc16gt.dll" was overwrittenby an older (signed) file. Version of source file: 3.510.3711.0.Version of target file: 3.510.3711.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "odbc32.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET19C.tmp" (target is"C:WindowsSystem32odbc32.dll").#-336 Copying file "C:WindowsSystem32SET19C.tmp" to"C:WindowsSystem32odbc32.dll" via temporary file"C:WindowsSystem32SET19E.tmp".#W025 A newer file "C:WindowsSystem32odbc32.dll" was overwritten byan older (signed) file. Version of source file: 3.520.6526.0. Versionof target file: 3.520.9030.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#W190 File "C:WindowsSystem32SET19E.tmp" marked to be moved to"C:WindowsSystem32odbc32.dll" on next reboot.#-340 Extracted file "odbc32gt.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET19F.tmp" (target is"C:WindowsSystem32odbc32gt.dll").#-336 Copying file "C:WindowsSystem32SET19F.tmp" to"C:WindowsSystem32odbc32gt.dll" via temporary file"C:WindowsSystem32SET1A1.tmp".#W025 A newer file "C:WindowsSystem32odbc32gt.dll" was overwrittenby an older (signed) file. Version of source file: 3.520.6526.0.Version of target file: 3.520.9030.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "odbcad32.exe" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET1A2.tmp" (target is"C:WindowsSystem32odbcad32.exe").#-336 Copying file "C:WindowsSystem32SET1A2.tmp" to"C:WindowsSystem32odbcad32.exe" via temporary file"C:WindowsSystem32SET1A4.tmp".#W025 A newer file "C:WindowsSystem32odbcad32.exe" was overwrittenby an older (signed) file. Version of source file: 3.520.6526.0.Version of target file: 3.520.9030.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "odbccp32.cpl" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET1A5.tmp" (target is"C:WindowsSystem32odbccp32.cpl").#-336 Copying file "C:WindowsSystem32SET1A5.tmp" to"C:WindowsSystem32odbccp32.cpl" via temporary file"C:WindowsSystem32SET1A7.tmp".#W025 A newer file "C:WindowsSystem32odbccp32.cpl" was overwrittenby an older (signed) file. Version of source file: 3.520.6526.0.Version of target file: 3.520.7713.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "odbccp32.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET1A8.tmp" (target is"C:WindowsSystem32odbccp32.dll").#-336 Copying file "C:WindowsSystem32SET1A8.tmp" to"C:WindowsSystem32odbccp32.dll" via temporary file"C:WindowsSystem32SET1AA.tmp".#W025 A newer file "C:WindowsSystem32odbccp32.dll" was overwrittenby an older (signed) file. Version of source file: 3.520.6526.0.Version of target file: 3.520.9030.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "odbccr32.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET1AB.tmp" (target is"C:WindowsSystem32odbccr32.dll").#-336 Copying file "C:WindowsSystem32SET1AB.tmp" to"C:WindowsSystem32odbccr32.dll" via temporary file"C:WindowsSystem32SET1AD.tmp".#W025 A newer file "C:WindowsSystem32odbccr32.dll" was overwrittenby an older (signed) file. Version of source file: 3.520.6526.0.Version of target file: 3.520.9030.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "odbccu32.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET1AE.tmp" (target is"C:WindowsSystem32odbccu32.dll").#-336 Copying file "C:WindowsSystem32SET1AE.tmp" to"C:WindowsSystem32odbccu32.dll" via temporary file"C:WindowsSystem32SET1B0.tmp".#W025 A newer file "C:WindowsSystem32odbccu32.dll" was overwrittenby an older (signed) file. Version of source file: 3.520.6526.0.Version of target file: 3.520.9030.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "odbcint.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET1B4.tmp" (target is"C:WindowsSystem32odbcint.dll").#-336 Copying file "C:WindowsSystem32SET1B4.tmp" to"C:WindowsSystem32odbcint.dll" via temporary file"C:WindowsSystem32SET1B6.tmp".#W025 A newer file "C:WindowsSystem32odbcint.dll" was overwrittenby an older (signed) file. Version of source file: 3.520.6526.0.Version of target file: 3.520.7713.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#W190 File "C:WindowsSystem32SET1B6.tmp" marked to be moved to"C:WindowsSystem32odbcint.dll" on next reboot.#-340 Extracted file "odbctrac.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to"C:WindowsSystem32SET1B7.tmp" (target is"C:WindowsSystem32odbctrac.dll").#-336 Copying file "C:WindowsSystem32SET1B7.tmp" to"C:WindowsSystem32odbctrac.dll" via temporary file"C:WindowsSystem32SET1B9.tmp".#W025 A newer file "C:WindowsSystem32odbctrac.dll" was overwrittenby an older (signed) file. Version of source file: 3.520.6526.0.Version of target file: 3.520.9030.0. The SP_COPY_FORCE_NEWER flag wasignored. The existing target file was signed.#-340 Extracted file "oledb32.dll" from cabinet"C:WINDOWSTempIXP000.TMPmdacxpak.cab" to "C:Program FilesCommonFilesSystemOLE DBSET1BA.tmp" (target is "C:Program FilesCommonFilesSystemOLE DBoledb32.dll").#-336 Copying file "C:Program FilesCommon FilesSystemOLEDBSET1BA.tmp" to "C:Program FilesCommon FilesSystemOLEDBoledb32.dll" via temporary file

View 2 Replies View Related

Has Sql Server 2000 Personal Edition Any User Limits?

Jan 7, 2008


I have installed Sql Server 2000 Personal Edition (Version: 8.00.2039 SP4 Personal Edition), it runs over Windows XP.
Has Sql Server 2000 Personal Edition any user limits?
Thanks for reply
Ariel

View 6 Replies View Related

Sql Server Express And Sample Personal Web Site Start Up

Mar 5, 2006

I have installed sql server express 2005 and also visual studio express developer when i run the personal web site sample I get the folowing error

Shared Memory Provider, error: 40 - Could not open a connection to SQL Server



How do I correct this please does any one know ?

View 4 Replies View Related

How To Get The Default SA Account Password And How To Change It In Sql 2000 Personal Edition ?

May 9, 2005

hi, all:
         I installed a Sql 2000 Personal Edition in my Laptop,now I want to change my Sql 2000 sa account password.
         but I can not find where I can get the default password for sa account and how to change it .
 
         thanks

View 1 Replies View Related

Problems Publishing My Personal Website - Works Fine Locally!

Jan 24, 2006

People,I'm trying to publish my first website and am having a few problems.I've got Visual Web Developer 2005 Express and am trying to use the Personal Website Starter Kit. (my SQL server is SQL Server Express Edition 2005 - which is also running on my local machine)It seems to work fine when I run it on my localhost, as soon as I ftp it up to my web hosting company, I get an error message (see below) :-An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) My hypothesis is :-It would appear to me that when running locally, the starter kit website uses my installation of SQL 2005 Express Edition, but when I upload all the files, I'm guessing the application is still trying to point at a local instance of SQL on my local PC which it now cannot see. I'm guessing I need to somehow upload the SQL database onto my web host (I've purchased 100M of SQL Server 2005 space), and point the application at that SQL instance instead. But I don't know if I'm right about all this, or indeed how to do it if I am. Can anyone help?Much thanks in advance,Will

View 1 Replies View Related

SP2 Install Error : Error 1625

Mar 9, 2007

Hello,

I'm getting this error:



=== Verbose logging started: 09-03-2007 11:22:01 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: c:2615800be9b170361adff8bc7a52ebhotfix.exe ===
MSI (c) (68:50) [11:22:01:246]: Resetting cached policy values
MSI (c) (68:50) [11:22:01:246]: Machine policy value 'Debug' is 0
MSI (c) (68:50) [11:22:01:246]: ******* RunEngine:
******* Product: C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi
******* Action:
******* CommandLine: **********
MSI (c) (68:50) [11:22:01:246]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (68:50) [11:22:01:246]: Grabbed execution mutex.
MSI (c) (68:50) [11:22:01:246]: Cloaking enabled.
MSI (c) (68:50) [11:22:01:246]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (68:50) [11:22:01:246]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (A8:D0) [11:22:01:277]: Grabbed execution mutex.
MSI (s) (A8:3C) [11:22:01:277]: Resetting cached policy values
MSI (s) (A8:3C) [11:22:01:277]: Machine policy value 'Debug' is 0
MSI (s) (A8:3C) [11:22:01:277]: ******* RunEngine:
******* Product: C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi
******* Action:
******* CommandLine: **********
MSI (s) (A8:3C) [11:22:01:402]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (A8:3C) [11:22:01:402]: File will have security applied from OpCode.
MSI (s) (A8:3C) [11:22:01:996]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi' against software restriction policy
MSI (s) (A8:3C) [11:22:01:996]: SOFTWARE RESTRICTION POLICY: C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi has a digital signature
MSI (s) (A8:3C) [11:22:02:121]: SOFTWARE RESTRICTION POLICY: C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi is permitted to run at the 'unrestricted' authorization level.
MSI (s) (A8:3C) [11:22:02:121]: End dialog not enabled
MSI (s) (A8:3C) [11:22:02:121]: Original package ==> C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi
MSI (s) (A8:3C) [11:22:02:121]: Package we're running from ==> C:WINDOWSInstaller1e413d.msi
MSI (s) (A8:3C) [11:22:02:136]: APPCOMPAT: looking for appcompat database entry with ProductCode '{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}'.
MSI (s) (A8:3C) [11:22:02:136]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (A8:3C) [11:22:02:136]: MSCOREE not loaded loading copy from system32
MSI (s) (A8:3C) [11:22:02:136]: Opening existing patch 'C:WINDOWSInstaller3d37f8c.msp'.
MSI (s) (A8:3C) [11:22:02:136]: SequencePatches starts. Product code: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}, Product version: 9.00.3042.00, Upgrade code: {3A91FA19-A197-467C-850F-0AFE90899371}, Product language 1033
MSI (s) (A8:3C) [11:22:02:136]: PATCH SEQUENCER: Setting patch {EE92F683-5F5C-4970-BB0B-9AC591B60268} to be unregistered, because the patch doesn't have any transform that targets this product.
MSI (s) (A8:3C) [11:22:02:136]: SequencePatches returns success.
MSI (s) (A8:3C) [11:22:02:136]: Final Patch Application Order:
MSI (s) (A8:3C) [11:22:02:136]: Other Patches:
MSI (s) (A8:3C) [11:22:02:136]: UnknownAbsent: {EE92F683-5F5C-4970-BB0B-9AC591B60268} -
MSI (s) (A8:3C) [11:22:02:136]: Machine policy value 'DisablePatch' is 0
MSI (s) (A8:3C) [11:22:02:136]: Machine policy value 'AllowLockdownPatch' is 1
MSI (s) (A8:3C) [11:22:02:136]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (A8:3C) [11:22:02:152]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (A8:3C) [11:22:02:152]: APPCOMPAT: looking for appcompat database entry with ProductCode '{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}'.
MSI (s) (A8:3C) [11:22:02:152]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (A8:3C) [11:22:02:152]: Transforms are not secure.
MSI (s) (A8:3C) [11:22:02:152]: Note: 1: 2205 2: 3: Control
MSI (s) (A8:3C) [11:22:02:152]: Command Line: REBOOT=ReallySuppress REINSTALLMODE=vomus REINSTALL=ALL CURRENTDIRECTORY=c:2615800be9b170361adff8bc7a52eb CLIENTUILEVEL=3 CLIENTPROCESSID=5736
MSI (s) (A8:3C) [11:22:02:152]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{BEFE6789-8AE1-4E45-B1F7-E3D6B30A51C8}'.
MSI (s) (A8:3C) [11:22:02:152]: Product Code passed to Engine.Initialize: ''
MSI (s) (A8:3C) [11:22:02:152]: Product Code from property table before transforms: '{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}'
MSI (s) (A8:3C) [11:22:02:152]: Product Code from property table after transforms: '{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}'
MSI (s) (A8:3C) [11:22:02:152]: Product registered: entering maintenance mode
MSI (s) (A8:3C) [11:22:02:152]: PROPERTY CHANGE: Adding ProductState property. Its value is '5'.
MSI (s) (A8:3C) [11:22:02:152]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'.
MSI (s) (A8:3C) [11:22:02:152]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (A8:3C) [11:22:02:152]: Note: 1: 1402 2: UNKNOWNNet 3: 2
MSI (s) (A8:3C) [11:22:02:152]: Specifed source is not already in a list.
MSI (s) (A8:3C) [11:22:02:152]: Policy value 'SearchOrder' is 'nmu'
MSI (s) (A8:3C) [11:22:02:152]: Machine policy value 'DisableBrowse' is 1
MSI (s) (A8:3C) [11:22:02:152]: Adding new sources is not allowed.
MSI (s) (A8:3C) [11:22:02:152]: Note: 1: 1729
MSI (s) (A8:3C) [11:22:02:152]: Note: 1: 2729
MSI (s) (A8:3C) [11:22:02:199]: Note: 1: 2729
MSI (s) (A8:3C) [11:22:02:199]: Product: Microsoft SQL Server Setup Support Files (English) -- Configuration failed.

MSI (s) (A8:3C) [11:22:02:199]: MainEngineThread is returning 1625
This installation is forbidden by system policy. Contact your system administrator.
C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi
MSI (c) (68:50) [11:22:02:308]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (68:50) [11:22:02:308]: MainEngineThread is returning 1625
=== Verbose logging stopped: 09-03-2007 11:22:02 ===



Time: 03/09/2007 11:22:35.028
KB Number: KB921896
Machine: CEPHEUS
OS Version: Microsoft Windows Server 2003 family, Enterprise Edition Service Pack 1 (Build 3790)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 2
Package Version: 3042
Command-line parameters specified:
Cluster Installation: No

**********************************************************************************
Prerequisites Check & Status
SQLSupport: Failed

**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
Setup Support Files ENU 9.1.2047 x86
Database Services (MSSQLSERVER) ENU SP1 2005.090.2153.00 x86 ENTERPRISE
Analysis Services (MSSQLSERVER) ENU SP1 2005.090.2153.00 x86 ENTERPRISE
Reporting Services (MSSQLSERVER) ENU SP1 9.00.2153.00 x86 ENTERPRISE
Notification Services ENU SP1 9.00.2153.00 x86 ENTERPRISE
Integration Services ENU SP1 9.00.2153.00 x86 ENTERPRISE
SQL Server Native Client ENU 9.00.2047.00 x86
Client Components ENU SP1 9.1.2153 x86 ENTERPRISE
MSXML 6.0 Parser ENU 6.00.3890.0 x86
SQLXML4 ENU 9.00.2047.00 x86
Backward Compatibility ENU 8.05.1704 x86
Microsoft SQL Server VSS Writer ENU 9.00.2047.00 x86

**********************************************************************************
Products Disqualified & Reason
Product Reason

**********************************************************************************
Processes Locking Files
Process Name Feature Type User Name PID
MSSQLSERVER SQL Server Native Client Service 1168
SQLSERVERAGENT SQL Server Native Client Service 2776
DISTRIB.exe SQL Server Native Client Application VASPservicelogon 4276
DISTRIB.exe SQL Server Native Client Application VASPservicelogon 4280
DISTRIB.exe SQL Server Native Client Application VASPservicelogon 4288
DISTRIB.exe SQL Server Native Client Application VASPservicelogon 4300
DISTRIB.exe SQL Server Native Client Application VASPservicelogon 4308
DISTRIB.exe SQL Server Native Client Application VASPservicelogon 4324
DISTRIB.exe SQL Server Native Client Application VASPservicelogon 4364
msftesql Database Services Service 296
ReportServer Database Services Service 1660
MSSQLServerOLAPService Analysis Services Service 1148
MsDtsServer Integration Services Service 352

**********************************************************************************
Product Installation Status
Product : Setup Support Files
Product Version (Previous): 2047
Product Version (Final) :
Status : Failure
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlSupport.msi.log
Error Number : 1625
Error Description : Unable to install Windows Installer MSI file
----------------------------------------------------------------------------------
Product : Database Services (MSSQLSERVER)
Product Version (Previous): 2153
Product Version (Final) :
Status : Not Applied
Log File :
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Analysis Services (MSSQLSERVER)
Product Version (Previous): 2153
Product Version (Final) :
Status : Not Applied
Log File :
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Reporting Services (MSSQLSERVER)
Product Version (Previous): 2153
Product Version (Final) :
Status : Not Applied
Log File :
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Notification Services
Product Version (Previous): 2153
Product Version (Final) :
Status : Not Applied
Log File :
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Integration Services
Product Version (Previous): 2153
Product Version (Final) :
Status : Not Applied
Log File :
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : SQL Server Native Client
Product Version (Previous): 2047
Product Version (Final) :
Status : Not Applied
Log File :
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Client Components
Product Version (Previous): 2153
Product Version (Final) :
Status : Not Applied
Log File :
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : MSXML 6.0 Parser
Product Version (Previous): 3890
Product Version (Final) :
Status : Not Applied
Log File :
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : SQLXML4
Product Version (Previous): 2047
Product Version (Final) :
Status : Not Applied
Log File :
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Backward Compatibility
Product Version (Previous): 1704
Product Version (Final) :
Status : Not Applied
Log File :
Error Number : 0
Error Description :
----------------------------------------------------------------------------------
Product : Microsoft SQL Server VSS Writer
Product Version (Previous): 2047
Product Version (Final) :
Status : Not Applied
Log File :
Error Number : 0
Error Description :
----------------------------------------------------------------------------------

**********************************************************************************
Summary
One or more products failed to install, see above for details
Exit Code Returned: 1603





View 2 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved