Problem with SQL Server 2005 Standard Edition installation

Hello,

When I try to install SQL Server 2005 Standard Edition, Windows XP SP2, setup fails.

Please help!!!

This is log file:

..............................

Loaded DLL:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\DbgHelp.dll
Version:
6.5.3.7
MSI (s) (98:E8) [12:19:07:890]: Leaked MSIHANDLE (6010) of type 790531 for thread 2260
MSI (s) (98:E8) [12:19:07:890]: Leaked MSIHANDLE (6009) of type 790540 for thread 2260
MSI (s) (98:E8) [12:19:07:890]: Leaked MSIHANDLE (6008) of type 790541 for thread 2260
MSI (s) (98:E8) [12:19:07:890]: Leaked MSIHANDLE (5973) of type 790541 for thread 2260
MSI (s) (98:E8) [12:19:07:890]: Leaked MSIHANDLE (5970) of type 790531 for thread 2260
MSI (s) (98:E8) [12:19:07:890]: Note: 1: 2769 2: Write_sqlLocalServers.D20239D7_E87C_40C9_9837_E70B8D4882C2 3: 5

Info 2769.The installer has encountered an unexpected error. The error code is 2769. Custom Action Write_sqlLocalServers.D20239D7_E87C_40C9_9837_E70B8D4882C2 did not close 5 MSIHANDLEs.
MSI (s) (98:2C) [12:19:07:890]: Machine policy value 'DisableRollback' is 0
MSI (s) (98:2C) [12:19:07:890]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
Action ended 12:19:07: Write_sqlLocalServers.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
MSI (s) (98:2C) [12:19:07:890]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (98:2C) [12:19:07:890]: No System Restore sequence number for this installation.
MSI (s) (98:2C) [12:19:07:890]: Unlocking Server
Action ended 12:19:07: INSTALL. Return value 3.
Property(S): ProductCode = {28B22773-100E-4AF2-A1C9-2F2EA8A35844}
Property(S): ProductLanguage = 1033

You did not say what version of XP you are running because you cannot install SQL Server 2005 Standard in XP Home, if you are running Media edition or Pro copy the content of the CDs/DVD into a folder in your C drive and run setup from your C drive. One more thing if you intend to install Reporting Services make sure IIS is running or the installer will skip it without telling you why. Hope this helps.

|||From the error message in the log, it appears that you have a setting on your machine which is preventing the systemstate backup to be rolled back. Check with your network administrator about disabling this setting.|||

I have Windows XP professional. IIS is running. Installation from C is also failed.

May be, I uninstalled incorrectly beta-version of Visual studio 2005 and/or SQL Server 2005.

I uninstalled all components and then cleaned register, but it didn't help.

Thanks.

Gato.

|||

Please comment what setting "is preventing the systemstate backup to be rolled back" , where and how can I check that?

I work without network administrator .

Thanks,

Gato.

|||

Gato wrote:

I have Windows XP professional. IIS is running. Installation from C is also failed.

May be, I uninstalled incorrectly beta-version of Visual studio 2005 and/or SQL Server 2005.

I uninstalled all components and then cleaned register, but it didn't help.

Thanks.

Gato.

Lets start with some WinXP system restore to the last available restore point and copy the files to the C and install from C drive. And I just noticed you are not running the standard setup, because I know the bootstrap setup runs for a short while and terminates. The 2005 installer is very easy I know because I had installed 2000 on all operating systems including 64bits except Vista and it was a pain but installing 2005 was a breeze. Keep me posted and pay attention to the installer don't answer questions not relevant to you.

Problem with scripting in SQL 2005 after SP2

Hello everyone,
We hit a snag after installing SP2 for SQL Server 2005 Standard. Basically,
when we want to script the database the server takes ages to determine
objects in the database and then it takes another age to actually script the
objects.
Before the SP2 scripting was lightning fast. Now we dread any change that
would require scripting.
Any help and/or insight much appreciated.
BR,
GAZ
> Before the SP2 scripting was lightning fast. Now we dread any change that
> would require scripting.
I find Red-Gate's SQL Compare to be very fast at generating change scripts.
Yes, it is not free, but it beats Management Studio's output hands down.
Anyway, here's something from Erland that I posted in the .Tools newsgroup
just yesterday:
[vbcol=seagreen]
I haven't tested scripting with SP2 as far as I can recall, but a tip
is that setting the database in forced parameterisation, can speed up
scripting considerably, since MgmtStudio uses inlined parameter values.
See also
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=247968[vbcol=seagreen]
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006
|||Thanks for the tip. Changing the property Parametarisation to Forced has
resolved the issue. Scripting is a pleasurable task once again.
Thanks.
GAZ
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:O$UD4VcgHHA.284@.TK2MSFTNGP05.phx.gbl...
> I find Red-Gate's SQL Compare to be very fast at generating change
> scripts. Yes, it is not free, but it beats Management Studio's output
> hands down.
> Anyway, here's something from Erland that I posted in the .Tools newsgroup
> just yesterday:
> I haven't tested scripting with SP2 as far as I can recall, but a tip
> is that setting the database in forced parameterisation, can speed up
> scripting considerably, since MgmtStudio uses inlined parameter values.
> See also
> http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=247968
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.sqlblog.com/
> http://www.aspfaq.com/5006
>

Problem with scripting in SQL 2005 after SP2

Hello everyone,
We hit a snag after installing SP2 for SQL Server 2005 Standard. Basically,
when we want to script the database the server takes ages to determine
objects in the database and then it takes another age to actually script the
objects.
Before the SP2 scripting was lightning fast. Now we dread any change that
would require scripting.
Any help and/or insight much appreciated.
BR,
GAZ
> Before the SP2 scripting was lightning fast. Now we dread any change that
> would require scripting.
I find Red-Gate's SQL Compare to be very fast at generating change scripts.
Yes, it is not free, but it beats Management Studio's output hands down.
Anyway, here's something from Erland that I posted in the .Tools newsgroup
just yesterday:
[vbcol=seagreen]
I haven't tested scripting with SP2 as far as I can recall, but a tip
is that setting the database in forced parameterisation, can speed up
scripting considerably, since MgmtStudio uses inlined parameter values.
See also
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=247968[vbcol=seagreen]
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006
|||Thanks for the tip. Changing the property Parametarisation to Forced has
resolved the issue. Scripting is a pleasurable task once again.
Thanks.
GAZ
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:O$UD4VcgHHA.284@.TK2MSFTNGP05.phx.gbl...
> I find Red-Gate's SQL Compare to be very fast at generating change
> scripts. Yes, it is not free, but it beats Management Studio's output
> hands down.
> Anyway, here's something from Erland that I posted in the .Tools newsgroup
> just yesterday:
> I haven't tested scripting with SP2 as far as I can recall, but a tip
> is that setting the database in forced parameterisation, can speed up
> scripting considerably, since MgmtStudio uses inlined parameter values.
> See also
> http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=247968
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.sqlblog.com/
> http://www.aspfaq.com/5006
>

Problem with scripting in SQL 2005 after SP2

Hello everyone,
We hit a snag after installing SP2 for SQL Server 2005 Standard. Basically,
when we want to script the database the server takes ages to determine
objects in the database and then it takes another age to actually script the
objects.
Before the SP2 scripting was lightning fast. Now we dread any change that
would require scripting.
Any help and/or insight much appreciated.
BR,
GAZ> Before the SP2 scripting was lightning fast. Now we dread any change that
> would require scripting.
I find Red-Gate's SQL Compare to be very fast at generating change scripts.
Yes, it is not free, but it beats Management Studio's output hands down.
Anyway, here's something from Erland that I posted in the .Tools newsgroup
just yesterday:
[vbcol=seagreen]
I haven't tested scripting with SP2 as far as I can recall, but a tip
is that setting the database in forced parameterisation, can speed up
scripting considerably, since MgmtStudio uses inlined parameter values.
See also
http://connect.microsoft.com/SQLSer...edbackID=247968[vbcol=se
agreen]
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006|||Thanks for the tip. Changing the property Parametarisation to Forced has
resolved the issue. Scripting is a pleasurable task once again.
Thanks.
GAZ
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in mess
age
news:O$UD4VcgHHA.284@.TK2MSFTNGP05.phx.gbl...
> I find Red-Gate's SQL Compare to be very fast at generating change
> scripts. Yes, it is not free, but it beats Management Studio's output
> hands down.
> Anyway, here's something from Erland that I posted in the .Tools newsgroup
> just yesterday:
>
> I haven't tested scripting with SP2 as far as I can recall, but a tip
> is that setting the database in forced parameterisation, can speed up
> scripting considerably, since MgmtStudio uses inlined parameter values.
> See also
> http://connect.microsoft.com/SQLSer...=247
968
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.sqlblog.com/
> http://www.aspfaq.com/5006
>

Problem with scripting in SQL 2005 after SP2

Hello everyone,
We hit a snag after installing SP2 for SQL Server 2005 Standard. Basically,
when we want to script the database the server takes ages to determine
objects in the database and then it takes another age to actually script the
objects.
Before the SP2 scripting was lightning fast. Now we dread any change that
would require scripting.
Any help and/or insight much appreciated.
BR,
GAZ> Before the SP2 scripting was lightning fast. Now we dread any change that
> would require scripting.
I find Red-Gate's SQL Compare to be very fast at generating change scripts.
Yes, it is not free, but it beats Management Studio's output hands down.
Anyway, here's something from Erland that I posted in the .Tools newsgroup
just yesterday:
I haven't tested scripting with SP2 as far as I can recall, but a tip
is that setting the database in forced parameterisation, can speed up
scripting considerably, since MgmtStudio uses inlined parameter values.
See also
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=247968
--
Aaron Bertrand
SQL Server MVP
http://www.sqlblog.com/
http://www.aspfaq.com/5006|||Thanks for the tip. Changing the property Parametarisation to Forced has
resolved the issue. Scripting is a pleasurable task once again.
Thanks.
GAZ
"Aaron Bertrand [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:O$UD4VcgHHA.284@.TK2MSFTNGP05.phx.gbl...
>> Before the SP2 scripting was lightning fast. Now we dread any change that
>> would require scripting.
> I find Red-Gate's SQL Compare to be very fast at generating change
> scripts. Yes, it is not free, but it beats Management Studio's output
> hands down.
> Anyway, here's something from Erland that I posted in the .Tools newsgroup
> just yesterday:
> I haven't tested scripting with SP2 as far as I can recall, but a tip
> is that setting the database in forced parameterisation, can speed up
> scripting considerably, since MgmtStudio uses inlined parameter values.
> See also
> http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=247968
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.sqlblog.com/
> http://www.aspfaq.com/5006
>

Problem with Remote Connections with SQL Server 2005 Standard Edition

After applying the changes mentioned in KB 914277 to allow remote connections, while working in Visual Studio 2005, I'm now getting an error with the number 26: Error locating server/Instance specified...

Sure wish I knew what remote means in this scenario, as there is nothing "remote" about my installation. I only have 1 computer, the one i'm working on, where SQL Server and Visual Studio are installed, and no networks involved, so what is remote?

Any help would be appreciated!!

If the sql server you are trying to connect to and the app you are running are on the same physical machine then you do not need to config remote connections.

Can you check if the SQL Server is still running via the services.msc or config manager first of all.

|||

If there is a way of telling SQL Server that I don't need any remote connection, I'd be more than happy to use it.

However I don't know how to do that... therefore I got the error-message about the remote connection.

How do I tell SQL Server there is no need for a remote connection?

Thanx!!

|||Use the surface area config tool|||

And then...

Check what, click what, do what?

I've only been able to install SQL Server, with a lot of coaching from this forum, I've never used it, and have no idea what makes it or any of it's utilities tick...

I'm thankful for any advice I've been given, but I have no idea what to do with the Surface Area tool, when I get there...

|||

Hello Layne - I got your e-mail about still not being able to connect. Without more information, this will be hard for everyone to help you with. But before I give you some more pointers, you should know about a couple of things.

First, this isn't the primary mechanism for support for Microsoft products. Everyone here is happy to help out where we can, but it's a free site where Microsoft and other database folks will try and help you. We'll do what we can to help you, but there are no guarantees. Microsoft hosts these sites (again, at no cost to you) but this isn't the primary method they support their products. If you need immediate assistance you can check out several support options at http://www.microsoft.com/support.

I also think the comments in your e-mail to me about "all of us going back to India" isn't very polite. If you're asking for help (for free), you may want to be complimentary rather than derogatory. It will get you more answers faster to be polite to others.

The best place for you to look for what you're asking is:

http://msdn.microsoft.com/vstudio/express/sql/learning/default.aspx

It's on Express, but will help you with your edition as well.

|||

If the problem is just remote connection is not allowed on the remote server read and check whether the remote server is configured as in the following article http://www.kodyaz.com/content/SQLServerdoesnotallowremoteconnections.aspx but it seems that you are hitting another problem

Problem with Remote Connections with SQL Server 2005 Standard Edition

After applying the changes mentioned in KB 914277 to allow remote connections, while working in Visual Studio 2005, I'm now getting an error with the number 26: Error locating server/Instance specified...

Sure wish I knew what remote means in this scenario, as there is nothing "remote" about my installation. I only have 1 computer, the one i'm working on, where SQL Server and Visual Studio are installed, and no networks involved, so what is remote?

Any help would be appreciated!!

If the sql server you are trying to connect to and the app you are running are on the same physical machine then you do not need to config remote connections.

Can you check if the SQL Server is still running via the services.msc or config manager first of all.

|||

If there is a way of telling SQL Server that I don't need any remote connection, I'd be more than happy to use it.

However I don't know how to do that... therefore I got the error-message about the remote connection.

How do I tell SQL Server there is no need for a remote connection?

Thanx!!

|||Use the surface area config tool|||

And then...

Check what, click what, do what?

I've only been able to install SQL Server, with a lot of coaching from this forum, I've never used it, and have no idea what makes it or any of it's utilities tick...

I'm thankful for any advice I've been given, but I have no idea what to do with the Surface Area tool, when I get there...

|||

Hello Layne - I got your e-mail about still not being able to connect. Without more information, this will be hard for everyone to help you with. But before I give you some more pointers, you should know about a couple of things.

First, this isn't the primary mechanism for support for Microsoft products. Everyone here is happy to help out where we can, but it's a free site where Microsoft and other database folks will try and help you. We'll do what we can to help you, but there are no guarantees. Microsoft hosts these sites (again, at no cost to you) but this isn't the primary method they support their products. If you need immediate assistance you can check out several support options at http://www.microsoft.com/support.

I also think the comments in your e-mail to me about "all of us going back to India" isn't very polite. If you're asking for help (for free), you may want to be complimentary rather than derogatory. It will get you more answers faster to be polite to others.

The best place for you to look for what you're asking is:

http://msdn.microsoft.com/vstudio/express/sql/learning/default.aspx

It's on Express, but will help you with your edition as well.

|||

If the problem is just remote connection is not allowed on the remote server read and check whether the remote server is configured as in the following article http://www.kodyaz.com/content/SQLServerdoesnotallowremoteconnections.aspx but it seems that you are hitting another problem