SQL,tables in a DB: windows

Showing posts with label windows. Show all posts

Thursday, March 22, 2012

(Cluster) Memory settings

Hello, I am purchasing a HP DL-380 (Cluster)
I am planing to install Windows 2003 and SQL 2000
Both machines has two processors and 4 GB o Physical Memory (RAM), but I
want to put 6 GB in the
Active Machine and 2 GB in the Passive Machine.
So, That is possible?
1) Is possible to have differentes memory configuration in a cluster?
2) SQL 2000 and Windows 2003 supports 6GB of Physical Memory?
Thanks a lot!!
AA
I forgot to mention that both machine are with 32 bits processors
Thanks again
AA
"AA" <aa@.personal.net.py> wrote in message
news:%23K0V94MIEHA.2376@.TK2MSFTNGP12.phx.gbl...
> Hello, I am purchasing a HP DL-380 (Cluster)
> I am planing to install Windows 2003 and SQL 2000
> Both machines has two processors and 4 GB o Physical Memory (RAM), but I
> want to put 6 GB in the
> Active Machine and 2 GB in the Passive Machine.
> So, That is possible?
> 1) Is possible to have differentes memory configuration in a cluster?
> 2) SQL 2000 and Windows 2003 supports 6GB of Physical Memory?
>
> Thanks a lot!!
>
> AA
>

(Cluster) Memory settings

Hello, I am purchasing a HP DL-380 (Cluster)
I am planing to install Windows 2003 and SQL 2000
Both machines has two processors and 4 GB o Physical Memory (RAM), but I
want to put 6 GB in the
Active Machine and 2 GB in the Passive Machine.
So, That is possible?
1) Is possible to have differentes memory configuration in a cluster?
2) SQL 2000 and Windows 2003 supports 6GB of Physical Memory?
Thanks a lot!!
AA
Do not do this. Just remember that some day resources from node one with 6GB of memory failover to node 2 with 2GB of memory. What will you do then
rgds
Sinisa Perovic
|||What you will do then is exactly what everyone has to do who is running a
configuration with dissimilar processing capacity. You plan for the case
where both are running on the node with the least power. You estimate the
degradation in performance for the applications based on various load and
time scenarios. You then make a business decision as to whether that
degradation in performance during that specific downtime scenario is
acceptable or not. If it is acceptable, you configure it and off you go.
If it isn't acceptable, you come up with alternatives. Saying to not ever
do this is a very simplistic answer that simply is not correct.
Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com

Monday, March 19, 2012

"The feature(s) specified are not valid for this edition of SQL Server" error when ins

I've successfully installed SQL Server 2005 Standard Edition on an Enterprise edition of Windows Server 2003 x64. I'm now (and also tried & failed during the install of the database engine) attempting to install the "Management Tools" component on the same server. However, in all my attempts to do so, I receive the following error:

The feature(s) specified are not valid for this edition of SQL Server

The message box does not list the features that are not valid but since the only item I've selected to install is the "Management Tools" option under "Client Components" it obviously points to something with that.

Am I missing something or are the Management Tools not supported in my config - most notably SQL Server 2005 Standard edition running on Windows Server 2003 x64?

Thanks.

- Lance

Colorado State University

I was finally able to install the "Management Tools" with a pretty simple solution: Install using the installer files directly off of the physical DVD. My prior attempts had all been using a copy of the files on the DVD stored locally on the server. Incidently, I had used the same copied files to successfully install the DB engine and SSIS. Go figure.

"SQL Server Mobile encountered problems when opening the database."

Hi,

I am writing an application for a device (HP IPAQ 6828) having Windows Mobile 5.0 using

-MS .NET Compact Framework 2.0 SP-1
-SQL Mobile 2005.
-VS 2005 .NET

The application uses Merge Replication. The error occurs in the Synchronise() Method of the SqlCeReplication object.

"SQL Server Mobile encountered problems when opening the database."

repl.AddSubscription(AddOption.ExistingDatabase)
repl.Synchronize()

I also checked the the connection string and it seems to be fine. Both my device and server can ping each other. Moreever I can also access the Web syncronization folder(on server) from the device.

Is anyone having a resolution for this?

This problem may be caused by many reasons.

The most common is not disposing the replication object or other data related objects. Make sure there isn't any other arround.
Sql Mobile 2005 allows multiple connections except while syncronizing.

Another known cause is a bad path on the connection string.

Other forum entries referring this problem:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=334604&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=478902&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=961633&SiteID=1|||

Hi,

I finally found the solution to this...

repl.AddSubscription(AddOption.ExistingDatabase)
repl.Synchronize()

(Note: I am trying to synchronize on an exisiting database)

The problem was since my database is already in use by my application and I am trying to sync the same DB. Synchronization cannot occur if the connection is already open by the application. Sql Mobile 2005 allows multiple connections except while synchronizing.

Therefore we need to close and dispose the open connection used by the application as under before attempting to synchonize.

(Below is the sample code)

private sub SampleSync()

sharedCon.close
sharedCon.dispose

try

' TO DO: Set replication object properties here

repl.AddSubscription(AddOption.ExistingDatabase)
repl.Synchronize()

finally
repl.dispose
end try

' TO DO: Open your shared connection here if required.

End sub

Note: Most of the times the connection string also causes a problem. A sample connection string would look like this...

repl.SubscriberConnectionString ="\Program Files\YourAppName\YourDb.sdf;Password =<...>"

Friday, March 16, 2012

"Report is being generated"

I have a windows application. I am using following code right after setting the LocalReport ReportPath. Report rendering is too slow if use following line of code and Report viewer does not show spiny and the text that says “Report is being generated.”

Me.ReportViewer1.SetDisplayMode(DisplayMode.PrintLayout)

Me.ReportViewer1.ZoomMode = ZoomMode.Percent

Me.ReportViewer1.ZoomPercent = 80

Please advise how can make it fast and show spiny.

Thanks in advance.

As to how to make it fast, you need to either increase the horsepower of your system or optimize your SQL query.

As to the spiny thingy, I believe that setting the zoom on the report viewer changes the zoom of the report once it is rendered. From what I can tell, the spiny thingy is rendered prior to the report being rendered.

I think the report viewer is actually showing the spiny thingy, but your report viewer is too large and the spiny thingy always appears in the middle of the report viewer.

I've yet to find an answer as to how to move the spiny thingy closer to the upper left corner of the screen. If you figure it out, let me know!

|||

Thanks for your reply. I think it is not related with SQL server query or system speed. If I take out following line of code it works superfast and spiny also appears.

Me.ReportViewer1.SetDisplayMode(DisplayMode.PrintLayout)

Me.ReportViewer1.ZoomMode = ZoomMode.Percent

Me.ReportViewer1.ZoomPercent = 80

I am getting a dataset from the server and then assigning that dataset to RDL file in Windows application at client side so there is no SQL server involved.

Spiny does not appear even after taking out Zoom mode and zoom percent. I guess something is wrong with setting DisplayMode.PrintLayout.

|||Any answer?|||

Just a reality check on Mr. Spiny:

Are you executing this report asynchronously?

>L<

|||Yes.|||Then, see here http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=231258&SiteID=1

>L<

|||

Thanks Lisa,

I am using a Report Viewer for Windows application and I guess by default AsyncRendering is True. I did not find any way to make it false to give a try. I am still not able to figure it out why "SetDisplayMode(DisplayMode.PrintLayout)" making report rendering so slow and also it is making spiny to disapear.

Appreciate you help.

|||

Hi there,

Of course you're right that there is this difference between web and winform usage -- and I often forget which we're talking about <sigh>. I apologize.

Did you try using the ShowProgress property to get Mr. Spiny?

You probably haven't touched it at all. And I don't think that setting display mode to false would automatically set ShowProgress False, but it *might* have that effect -- test its value, just in case, after you use the SetDisplayMode method.

Can you verify a couple of things about this report -- what is the interactive page size versus the standard page size? If the two are different, this might explain why you don't see the progress feedback in one case but you do in the other (if the page sizes are significantly different, I mean).

Alternatively, if you have been omitting the zoom-setting lines after the SetDisplayMode line when you don't set display mode, then Greg's explanation completely maks sense: the original zoom value shows enough of the page to show the progress feedback, while your chosen zoom value here does not.

>L<

"Report is being generated"

Me.ReportViewer1.SetDisplayMode(DisplayMode.PrintLayout)

Me.ReportViewer1.ZoomMode = ZoomMode.Percent

Me.ReportViewer1.ZoomPercent = 80

Please advise how can make it fast and show spiny.

Thanks in advance.

As to how to make it fast, you need to either increase the horsepower of your system or optimize your SQL query.

I think the report viewer is actually showing the spiny thingy, but your report viewer is too large and the spiny thingy always appears in the middle of the report viewer.

I've yet to find an answer as to how to move the spiny thingy closer to the upper left corner of the screen. If you figure it out, let me know!

|||

Thanks for your reply. I think it is not related with SQL server query or system speed. If I take out following line of code it works superfast and spiny also appears.

Me.ReportViewer1.SetDisplayMode(DisplayMode.PrintLayout)

Me.ReportViewer1.ZoomMode = ZoomMode.Percent

Me.ReportViewer1.ZoomPercent = 80

I am getting a dataset from the server and then assigning that dataset to RDL file in Windows application at client side so there is no SQL server involved.

Spiny does not appear even after taking out Zoom mode and zoom percent. I guess something is wrong with setting DisplayMode.PrintLayout.

|||Any answer?|||

Just a reality check on Mr. Spiny:

Are you executing this report asynchronously?

>L<

|||Yes.|||Then, see here http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=231258&SiteID=1

>L<

|||

Thanks Lisa,

Appreciate you help.

|||

Hi there,

Of course you're right that there is this difference between web and winform usage -- and I often forget which we're talking about <sigh>. I apologize.

Did you try using the ShowProgress property to get Mr. Spiny?

>L<

"Report is being generated"

Me.ReportViewer1.SetDisplayMode(DisplayMode.PrintLayout)

Me.ReportViewer1.ZoomMode = ZoomMode.Percent

Me.ReportViewer1.ZoomPercent = 80

Please advise how can make it fast and show spiny.

Thanks in advance.

As to how to make it fast, you need to either increase the horsepower of your system or optimize your SQL query.

I think the report viewer is actually showing the spiny thingy, but your report viewer is too large and the spiny thingy always appears in the middle of the report viewer.

I've yet to find an answer as to how to move the spiny thingy closer to the upper left corner of the screen. If you figure it out, let me know!

|||

Thanks for your reply. I think it is not related with SQL server query or system speed. If I take out following line of code it works superfast and spiny also appears.

Me.ReportViewer1.SetDisplayMode(DisplayMode.PrintLayout)

Me.ReportViewer1.ZoomMode = ZoomMode.Percent

Me.ReportViewer1.ZoomPercent = 80

I am getting a dataset from the server and then assigning that dataset to RDL file in Windows application at client side so there is no SQL server involved.

Spiny does not appear even after taking out Zoom mode and zoom percent. I guess something is wrong with setting DisplayMode.PrintLayout.

|||Any answer?|||

Just a reality check on Mr. Spiny:

Are you executing this report asynchronously?

>L<

|||Yes.|||Then, see here http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=231258&SiteID=1

>L<

|||

Thanks Lisa,

Appreciate you help.

|||

Hi there,

Of course you're right that there is this difference between web and winform usage -- and I often forget which we're talking about <sigh>. I apologize.

Did you try using the ShowProgress property to get Mr. Spiny?

>L<

Thursday, March 8, 2012

"Microsoft.Jet.OLEDB.4.0" has not been registered

Using OpenDataSource I run into this problem.

I have an SQL Server 2005 installed on Windows 2003 64 bit server (no itanium)
I have a 32 bit client where I run Management Studio.

This is the full detail of the error:
--
Msg 7403, Level 16, State 1, Line 1
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
--

I have tried installing a new 64bit Jet driver, but it only exists for Itanium.
How to force the system to use the 32 bit one?
I am stuck!The is no way to use Jet driver from a 64-bit SQL Server unfortunately. They did not port the driver to 64-bit. So this would only work from a 32-bit SQL Server.|||xxx|||You can force the SQL Server Agent to execute the 32-bit version of DTExec by setting up the job as a CmdExec task instead of an SSIS package call, as detailed here:
http://wiki.sqlis.com/default.aspx/SQLISWiki/x64.html?diff=y

"Microsoft.Jet.OLEDB.4.0" has not been registered

Using OpenDataSource I run into this problem.

I have an SQL Server 2005 installed on Windows 2003 64 bit server (no itanium)
I have a 32 bit client where I run Management Studio.

This is the full detail of the error:
--
Msg 7403, Level 16, State 1, Line 1
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
--

"Microsoft.Jet.OLEDB.4.0" has not been registered

Using OpenDataSource I run into this problem.

I have an SQL Server 2005 installed on Windows 2003 64 bit server (no itanium)
I have a 32 bit client where I run Management Studio.

This is the full detail of the error:
--
Msg 7403, Level 16, State 1, Line 1
The OLE DB provider "Microsoft.Jet.OLEDB.4.0" has not been registered.
--

I have tried installing a new 64bit Jet driver, but it only exists for Itanium.
How to force the system to use the 32 bit one?
I am stuck!
The is no way to use Jet driver from a 64-bit SQL Server unfortunately. They did not port the driver to 64-bit. So this would only work from a 32-bit SQL Server.|||xxx|||You can force the SQL Server Agent to execute the 32-bit version of DTExec by setting up the job as a CmdExec task instead of an SSIS package call, as detailed here:
http://wiki.sqlis.com/default.aspx/SQLISWiki/x64.html?diff=y

Saturday, February 25, 2012

"Could not start the SQL Server Integration Services..."

Running MS SQL 2005 SP1 on Windows 2003 Server SP1 (IA32). Upon rebooting, I get an error that this service failed to start, and when I attempt to start manually, I get the same error:

Could not start the SQL Server Integration Services service on the Local Computer.

Error 1053: The service did not respond to the start or control request in a timely fashion.

Any ideas?

Have you looed at http://support.microsoft.com/kb/886695/ ?

Thanks,
Ovidiu Burlacu

|||I also recommend this one - http://support.microsoft.com/kb/918644 :)

"could not open connection to SQL Server"?

I just installed a new SQL 2005 Server (September CTP - Developer Edition) on Windows Server 2003 (Using Virtual PC).

I have created a Data Model to be used for creating reports. When I tried to deploy the Model, I got an error along the lines of "...SQL Server does not allow remote connections...".

I then took a step back and tried to browse the report server (http://localhost/reportserver) and I got the message 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

I also notice that when I go into the Reporting Services Configuration Manager, I see that the Initialization item in the left hand side is Not Configured (has a "red x"). When I try clicking on this item, I get a similar message to the one above.

I am very new at SQL 2005 and this is my first install of it (I have been using other installations in the past). I did some searching and found that I should use the SQL Server Surface Area Configuration utility to allow remote connections for both TCP and Named Pipes. I did this and rebooted my server and I am still getting the same error messages.

Is there something I have yet to configure?

Any and all help is very much appreciated!!!

Thanks!

Brian McCulloughRight after I posted this I realized I renamed the Computer after I installed SQL. The problem was that when I installed reporting services, it created all the connection information based on the "old" computer name.

Brian|||What did you have to do to fix it? Where is the connection information?|||In the Reporting Services Configuration Manager select the Database Setup item on the left-hand side. This is where you specify the Database connection properties for the ReportServer database. I had to change the Server Name to match the current machine name, not what I had it as originally.

-Brian|||I had a similar problem - I was able to fix it by specifying my server as computer-name\servername
Hope this helps

"could not open connection to SQL Server"?

I just installed a new SQL 2005 Server (September CTP - Developer Edition) on Windows Server 2003 (Using Virtual PC).

I have created a Data Model to be used for creating reports. When I tried to deploy the Model, I got an error along the lines of "...SQL Server does not allow remote connections...".

I then took a step back and tried to browse the report server (http://localhost/reportserver) and I got the message below:

Is there something I have yet to configure?

Any and all help is very much appreciated!!!

Thanks!

-Brian|||I had a similar problem - I was able to fix it by specifying my server as computer-name\servername
Hope this helps

"Class not registered" with RMO and x64 Windows

I have a small .net application that uses RMO to synchronize a merge subscription. Everything works fine when I build with platform target = "Any CPU" on both x86 and x64 systems, but I get a "Class not registered" error on my x64 system when the application is built with platform target = "x86". Incase you are wondering I have to run this code under x86 because it is actually going to distributed in a dll and called from an x86 application.

x64 System:

Microsoft Windows Server 2003 R2

Enterprise x64 Edition

Service Pack 1

Here is my code:

{
ServerConnection dbconn = new ServerConnection(publication_server);
dbconn.LoginSecure = true;
dbconn.Connect();

MergeSubscription subscription = new MergeSubscription();
subscription.ConnectionContext = dbconn;
subscription.DatabaseName = publication_db;
subscription.PublicationName = publication_name;
subscription.SubscriberName = subscription_server;
subscription.SubscriptionDBName = subscription_db;

if (!subscription.LoadProperties() || subscription.SubscriberSecurity == null)
throw new Exception("Unable to initialize the Synchronization");

MergeSynchronizationAgent agent = subscription.SynchronizationAgent;
agent.Synchronize();
}

The MergeSynchronizationAgent class is platform specific (it is just a thin wrapper around a pile of native code), so you would need to make sure that you have the x86 version of SQL Server installed on your x64 server if you compile your exe as x86.

-Raymond

|||

I would hate to install an x86 instance of SQL Server to solve this issue. Is there anything short of that I can do to get the appropriate files and registry keys on to an x64 system?

Thanks for your help.

|||

Sorry to disappoint you, but there really isn't a supported way to allow you to just pick the dependencies for running the MergeSynchronizationAgent class although we have plans to come up with a merge module for replication components in the future. Realistically, it would be rather difficult to just pick out the dependencies for the MergeSynchronizationAgent class as it depends on things that folks normally don't suspect such as:

sqlncli.dll\rll

msvc80*.dll

The 2.0 .NET Framework

instapi.dll under 90\Share and corresponding registry key for locating it.

-Raymond

"Can't find PInvoke DLL 'dbnetlib.dll'."

every time when I opened the connection from my windows CE4.2 device to sql server I got the error "Can't find PInvoke DLL 'dbnetlib.dll'.

My OS is MS CE4.2, I've installed Compact Framework 2.0 and SQL client. It worked fine at OS CE5.0 but not at CE4.2. My application is working correctly, but when I started the connection I received this error.

Any idea?

thanks, Jan

If you indeed have SQL Client installed properly, I would guess some dependencies required for it to function are missing from the OS image. Contact device OEM for help.

Friday, February 24, 2012

"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and retu

Hello,

We are running Windows Server 2003 SP 1 and trying to upgrade SQL 2000 SP 4 to SQL 2005 using the command line.

The process finishes in under ten minutes. Summary.txt file we have this information:

Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup_<ServerName>_SQL.log
Last Action : ValidateUpgrade
Error String : The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed
Error Number : 2259

In the log file named SQLSetup_ServerName_Core.log I found the following:

Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:
"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 1627
Aborting queue processing as nested installer has completed
Message pump returning: 1627

After receiving this info, I can navigate to the setup.bat for the SQL 2005 upgrade and complete the upgrade without error. We are planning on 500 of these, so manual updates is a very ugly concept.

I'd appreciate any and all ideas on where to go from here.

Most Sincerely.

Could you search inside the *_SQL.log for the string mentioned in summary.txt:

"The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed"

When you find the string, could you copy the lines above and below so we could see the context around the error? Hopefully you could include all the logging statements associated with the ValidateUpgrade action. It should start with a line like this:

<Func Name='ValidateUpgrade'>

Thanks!

|||

Dear R.Green,

I appreciate your help. The results of your request follows. Please let me know if I can help in any other way.

Thanks,

Bill

Function=SAPasswordPolicyCheck
Skipping Action: SAPasswordPolicyCheck (Condition is false)
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (A4:94) [11:38:44:323]: Doing action: ValidateUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2
Action ended 11:38:44: SAPasswordPolicyCheck.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 1.
MSI (s) (A4:2C) [11:38:44:339]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI11F.tmp, Entrypoint: ValidateUpgrade
Action start 11:38:44: ValidateUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2.
<Func Name='LaunchFunction'>
Function=ValidateUpgrade
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: ValidateUpgrade
PerfTime Start: ValidateUpgrade : Tue Nov 14 11:38:44 2006
<Func Name='ValidateUpgrade'>
<Func Name='updateFeatureSellection'>
<Func Name='SqlComponentUpgrade'>
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
<Func Name='ProcessHeaderTable'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
MSI (s) (A4!B0) [11:38:44:464]: Note: 1: 2205 2: 3: _sqlSqlUpgradeSequence
MSI (s) (A4!B0) [11:38:44:464]: Note: 1: 2228 2: 3: _sqlSqlUpgradeSequence 4: CREATE TABLE `_sqlSqlUpgradeSequence` (`Action` CHAR(255) NOT NULL, `Sequence` INT NOT NULL, `Param` CHAR(0), `Retryable` INT NOT NULL, `Fatal` INT NOT NULL PRIMARY KEY `Action`, `Sequence`)
MSI (s) (A4!B0) [11:38:44:464]: Note: 1: 2262 2: _sqlSqlUpgradeSequence 3: -2147287038
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Adding Sql_sqlSqlUpgradeSequence property. Its value is '15000000'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '15000000'. Its new value: '30000000'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '30000000'. Its new value: '30040000'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '30040000'. Its new value: '30050000'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '30050000'. Its new value: '30150000'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '30150000'. Its new value: '100150000'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '100150000'. Its new value: '230871400'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '230871400'. Its new value: '245871400'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '245871400'. Its new value: '275871400'.
MSI (s) (A4!B0) [11:38:44:480]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeSequence property. Its current value is '275871400'. Its new value: '275971400'.
<Func Name='GetFileTargetPath'>
<EndFunc Name='SqlComponentUpgrade' Return='0' GetLastError='0'>
Added FTE to SqlUpgrade property
Added REPL to SqlUpgrade property
<Func Name='updateFeatureSellection'>
MSI (s) (A4!B0) [11:38:44:636]: skipping installation of assembly component: {7F618CB9-9BCE-4C1E-9E33-59E8A564E456} since the assembly already exists
To perform upgrade setting feature SQL_Replication to be indtalled locally.
To perform upgrade setting feature SQL_FullText to be indtalled locally.
Running:
CollectInstallCases
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 44.44

Complete:
CollectInstallCases
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 44.44
, returned
true

Running:
DefineFeatureActionRules
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 44.44

Complete:
DefineFeatureActionRules
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 44.44
, returned
true

Running:
DefineInstallActionRules
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 44.44

Complete:
DefineInstallActionRules
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45
, returned
true

Running:
AddInstallCaseActions
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45

Complete:
AddInstallCaseActions
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45
, returned
true

Loaded DLL:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlboot.dll
Version:
2005.90.1399.0

Action "
languageUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:

Condition "differentLanguage_with_1033_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Loaded DLL:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlboot.dll
Version:
2005.90.1399.0

Action "
maintenance_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:

Condition "sameVersion_as_9.0.139906_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Loaded DLL:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlboot.dll
Version:
2005.90.1399.0

Action "
skuUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:

Condition "NOT_sameSKU_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Loaded DLL:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlboot.dll
Version:
2005.90.1399.0

Action "
virtualization_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:

Condition "virtualization_NotSupported_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Action "
warningPatchLevel_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:

Condition "diffInstancePatchLevel_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Action "
warningSPLevel_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:

Condition "diffInstanceSPLevel_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Action "
warningUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
" will be skipped due to the
following restrictions:

Condition "warningUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER" returned false.

Running:
versionUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45

Complete:
versionUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45
, returned
true

Running:
AddFeatureCase_versionUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45

Complete:
AddFeatureCase_versionUpgrade_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45
, returned
true

Running:
FeaturePhaseAction
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45

Complete:
FeaturePhaseAction
at:
Info 2006.2006
/
10
/
14
11
:
Info 38.38
:
Info 45.45
, returned
true

Action "
add_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER_SQL_Engine
" will be skipped due to the
following restrictions:

Condition "noFeatureConflict_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER_SQL_Engine" returned false.
Condition "NOT_featureInstalled_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER_SQL_Engine" returned false.
Condition "installActionAvailable_maintenance_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER_SQL_Engine" returned false.

Action "
remove_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER_SQL_Engine
" will be skipped due to the
following restrictions:

MSI (s) (A4!B0) [11:38:45:839]: PROPERTY CHANGE: Deleting AGTACCOUNT property. Its current value is 'CEDNetLive\Roamer'.
MSI (s) (A4!B0) [11:38:45:839]: PROPERTY CHANGE: Deleting AGTPASSWORD property. Its current value is '**********'.
Condition "installActionAvailable_maintenance_MSSQLSERVER SQL 8.0 SQL Server Standalone Product MSSQLSERVER_SQL_Engine" returned false.

Attempt to start service when it is already running
SQL service MSSQLSERVER started successfully waiting for SQL service to accept client connections
Loaded DLL:
C:\WINDOWS\system32\Odbc32.dll
Version:
3.526.1830.0

SQL_SUCCESS_WITH_INFO (1) in OdbcConnection::connect
sqlstate=01000, level=-1, state=-1, native_error=5701, msg=[Microsoft][SQL Native Client][SQL Server]Changed database context to 'master'.
sqlstate=01000, level=-1, state=-1, native_error=5703, msg=[Microsoft][SQL Native Client][SQL Server]Changed language setting to us_english.

Executing External Command
Message type: Progress
10
Message type: Component
Database Engine
Message type: Status
Checking for SQL Connectivity...
Message type: Status
Starting analysis...
Message type: Status
Analyzing 1%
Message type: Status
Analyzing 5%
Message type: Status
Analyzing 15%
Message type: Status
Analyzing 16%
Message type: Status
Analyzing 17%
Message type: Status
Analyzing 18%
Message type: Status
Analyzing 20%
Message type: Status
Analyzing 21%
Message type: Status
Analyzing 30%
Message type: Status
Analyzing 33%
Message type: Status
Analyzing 34%
Message type: Status
Analyzing 35%
Message type: Status
Analyzing 38%
Message type: Status
Analyzing 50%
Message type: Status
Analyzing 51%
Message type: Status
Analyzing 55%
Message type: Status
Analyzing 66%
Message type: Status
Analyzing 67%
Message type: Status
Analyzing 68%
Message type: Status
Analyzing 71%
Message type: Status
Analyzing 83%
Message type: Status
Analyzing 84%
Message type: Status
Analyzing 85%
Message type: Status
Analyzing 88%
Message type: Status
Analyzing 90%
Message type: Status
Analyzing 100%
Message type: Status
Creating report
Message type: Status
Creating report
Message type: Progress
Info 100.100
<Func Name='SqlComponentUpgrade'>
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
<Func Name='ProcessHeaderTable'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
MSI (s) (A4!B0) [11:39:18:558]: Note: 1: 2259 2: 3: 4:
<Func Name='GetFileTargetPath'>
Error Code: 0x8007065b (1627)
Windows Error Text: Function failed during execution.
Source File Name: darlib\viewinstaller.cpp
Compiler Timestamp: Mon Jun 13 14:19:43 2005
Function Name: sqls::ViewInstaller::modify
Source Line Number: 137

- Context --

Setting status of unmanaged components and removing unmanaged resources
Failed to modify installer view
1: 2259 2: 3: 4:

Error Code: 1627
MSI (s) (A4!B0) [11:39:18:745]: Product: Microsoft SQL Server 2005 -- Error 2259. The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed

Error 2259. The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed
<Failure Type='Fatal' Error='1627'>
<EndFunc Name='LaunchFunction' Return='1627' GetLastError='0'>
Action ended 11:39:18: ValidateUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
Action ended 11:39:18: INSTALL. Return value 3.
Property(S): ProductCode = {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
Property(S): ProductLanguage = 1033
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductVersion = 9.00.1399.06
Property(S): MEDIAPACKAGEPATH = \Setup\

|||

Thank you for the follow up, we are still looking into this internally to see if we have any ideas. I'm wondering how you are installing SQL Server 2005. Is it from removable media, a network location, or from the hard drive? Did the media come from a download or was it burned from ISO?

The error message is strange because it should list the query that was attempted, but it looks to be an empty string. I'm just wondering if there is a possibility that the point of installation has a corrupt MSI database in some way.

|||

Hi,

Thanks for your efforts. We have a volume license agreement with Microsoft. I copied the two CDs we received under that agreement to an IDE drive on the server that is being upgraded. My template.ini file is pointing to that drive. We are running from the hard drive because we will push this upgrade to the field using LanDesk. To say it another way, we are not sending media to our hundred plus sites.

Please let me know if I didn't answer the correct question. (Something I do more and more as I get older.)

Thanks,

Bill

|||

Hi,

Any word on this? I need to keep this moving.

Thanks,

Bill

|||

Hi BaldManDBA

Any resolution? This is also a SQL Server 2005 Express edition issue too

see: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1663937&SiteID=1

Extract of my log:

- Context --

Setting status of unmanaged components and removing unmanaged resources
Failed to modify installer view
1: 2259 2: 3: 4:

Error Code: 1627
MSI (s) (9C!2C) [21:36:21:171]: Product: Microsoft SQL Server 2005 Express Edition -- Error 2259. The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed

Error 2259. The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='203'>
Doing Action: ValidateUpgrade
PerfTime Start: ValidateUpgrade : Tue May 29 21:36:21 2007
<Func Name='ValidateUpgrade'>
<Func Name='updateFeatureSellection'>
<Func Name='SqlComponentUpgrade'>
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='203'>
<Func Name='ProcessHeaderTable'>
<Func Name='ProcessScriptTable'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>
<Func Name='GetFileTargetPath'>

In my case, it was simply a case of leave all the defaults during the SS2005 SP2 install, except the instance where (_) default instance had to be ticked instead of a named instance

Please let us know ... (as your solution may be related to all other SQL Server 2005 version/situations)

Alain

|||

Hi,

The server that generated that error was the only one to encounter the error. So, for that one server, we reinstalled SQL Server. All was OK after that. I hope this helps.

Thanks,

BaldManDBA.

"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and