Showing posts with label online. Show all posts
Showing posts with label online. Show all posts

Thursday, March 29, 2012

Can't complete SQL Server 2005 installation!!!

An err occurs when the installation of SQL Server 2005 ,"failed to start" SQL Server , the err msg asks me to query online menually,includes "SQL Server 2005 Setup Log Files and Starting SQL Server Manually." but I don't know what is the problem. Can you help me?

You first need to look at the SQL Server summary log file located at: %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\summary.txt. This should direct you to which component is failing and the log file for that component. When looking at the component log files you can easily locate the trouble area by searching the file for "value 3" - this will jump you to the area of the log file that contains the error. Reply back with the section of the log file that contains the error.

If this log file doesn't specify a particular component you need to look at the core log file located at: %Program Files%\Microsoft SQL Server\90\Setup Bootstrap\log\files\*core*.log. You should find the error at the bottom of this log file. If there error is in this log file please reply back with the section of the log file that contains the error.

Thanks,

Dan

|||Hello,Dan:
I found the two files, and i knew that what component is failing, but I don't know clearly you mean "value 3."

this is the failing component in summary.txt
--
Machine : PROJECTTEAM
Product : Microsoft SQL Server 2005 CTP
Product Version : 9.00.1116
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0013_PROJECTTEAM_SQL.log
Error Number : 2147944003

The file is the component log file,I don't know how to find the
cause of error,can you help me?
http://ms.ntcb.edu.tw/~s8856094/SQL/SQLSetup0013_PROJECTTEAM_SQL.log
Thank you..|||Okay, the service is failing to start. I need to direct you to yet another log file. In the middle of setup you will find a log file for the SQL Server DB Engine under the installation folder for this component. If you are installing on a clean machine it will be under c:\program files\microsoft sql server\mssql.1\log. This file will specify why the service couldn't start up.

Dan

p.s. "Value 3" is nothing special other than the MSI return code for failures. It's an easy thing to search on to find the actual text of the error message in the log. In your case it pointed me to the following error:

Error 29523. The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (1067)|||I'm going to close out this thread since there hasn't been a response to my question in three weeks.
Dan|||Most of the above applies to my case as well.
The best clue I have to the failure is this event log item:
Event Type: Warning
Event Source: WinMgmt
Event Category: None
Event ID: 5603
Date: 8/10/2005
Time: 8:16:07 AM
User: WINGS\rheitzman
Computer: PC3090-060
Description:
A provider, SQLServerEventProvider, has been registered in the WMI namespace, root\Microsoft\SqlServer\ServerEvents\SQLEXPRESS, but did not specify the HostingModel property. This provider will be run using the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests. Ensure that provider has been reviewed for security behavior and update the HostingModel property of the provider registration to an account with the least privileges possible for the required functionality.
The SQLExpress install proceeds OK to the midpoint of installing the Database Services that halts with the message that began this thread.
I tried to restart the service beore canceling the install to no avail. Canceling the install backs out the install so the directions to start manually are bogus since the service(s) is removed.
Beta 1 was installed and the removal tool has been used; serveral times.
SQL Server 2000 reporting services was installed at one time and was also problematic. It was removed via add/remove.
Any help would be appreciated!

Thursday, February 16, 2012

Cannot seem to connect to named instance

We are trying to connect to a SQL Server across the WAN. We can manage to
ping the server and know that SQL Server is online on the other end as on
the own internal network, we can connect to it.. but across the WAN, we
cannot. We are thinking its a port issue that needs to be opened. So the
question is do I only need to open the port that named instance is listening
on or do I have to open up some other ports too. I believe for named
instances, there is something to do with UDP port too. Let me know if i have
to open up UDP port 1434 too to get this to work.
> Let me know if i have to open up UDP port 1434 too to get this to work.
Yes, you'll need to open up UDP port 1434 for named instance port
enumeration as well as the named instance port TCP port. Alternatively, you
can create an alias for the named instance on the client machine and specify
the named instance port number. You won't need to open UDP 1434 in that
case.
Hope this helps.
Dan Guzman
SQL Server MVP
"Hassan" <hassan@.hotmail.com> wrote in message
news:ueLdNA41HHA.1188@.TK2MSFTNGP04.phx.gbl...
> We are trying to connect to a SQL Server across the WAN. We can manage to
> ping the server and know that SQL Server is online on the other end as on
> the own internal network, we can connect to it.. but across the WAN, we
> cannot. We are thinking its a port issue that needs to be opened. So the
> question is do I only need to open the port that named instance is
> listening on or do I have to open up some other ports too. I believe for
> named instances, there is something to do with UDP port too. Let me know
> if i have to open up UDP port 1434 too to get this to work.
>
>

Cannot seem to connect to named instance

We are trying to connect to a SQL Server across the WAN. We can manage to
ping the server and know that SQL Server is online on the other end as on
the own internal network, we can connect to it.. but across the WAN, we
cannot. We are thinking its a port issue that needs to be opened. So the
question is do I only need to open the port that named instance is listening
on or do I have to open up some other ports too. I believe for named
instances, there is something to do with UDP port too. Let me know if i have
to open up UDP port 1434 too to get this to work.> Let me know if i have to open up UDP port 1434 too to get this to work.
Yes, you'll need to open up UDP port 1434 for named instance port
enumeration as well as the named instance port TCP port. Alternatively, you
can create an alias for the named instance on the client machine and specify
the named instance port number. You won't need to open UDP 1434 in that
case.
Hope this helps.
Dan Guzman
SQL Server MVP
"Hassan" <hassan@.hotmail.com> wrote in message
news:ueLdNA41HHA.1188@.TK2MSFTNGP04.phx.gbl...
> We are trying to connect to a SQL Server across the WAN. We can manage to
> ping the server and know that SQL Server is online on the other end as on
> the own internal network, we can connect to it.. but across the WAN, we
> cannot. We are thinking its a port issue that needs to be opened. So the
> question is do I only need to open the port that named instance is
> listening on or do I have to open up some other ports too. I believe for
> named instances, there is something to do with UDP port too. Let me know
> if i have to open up UDP port 1434 too to get this to work.
>
>|||On the below thread and similar issue, how can I hard code SQL Instance to
use the same port number?
Any suggestions?
"Dan Guzman" wrote:
> > Let me know if i have to open up UDP port 1434 too to get this to work.
> Yes, you'll need to open up UDP port 1434 for named instance port
> enumeration as well as the named instance port TCP port. Alternatively, you
> can create an alias for the named instance on the client machine and specify
> the named instance port number. You won't need to open UDP 1434 in that
> case.
>
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Hassan" <hassan@.hotmail.com> wrote in message
> news:ueLdNA41HHA.1188@.TK2MSFTNGP04.phx.gbl...
> > We are trying to connect to a SQL Server across the WAN. We can manage to
> > ping the server and know that SQL Server is online on the other end as on
> > the own internal network, we can connect to it.. but across the WAN, we
> > cannot. We are thinking its a port issue that needs to be opened. So the
> > question is do I only need to open the port that named instance is
> > listening on or do I have to open up some other ports too. I believe for
> > named instances, there is something to do with UDP port too. Let me know
> > if i have to open up UDP port 1434 too to get this to work.
> >
> >
> >
>|||> On the below thread and similar issue, how can I hard code SQL Instance to
> use the same port number?
You can specify the server port number using the SQL Server Network Utility
(SQL 2000) or the SQL Server Configuration Manager (SQL 2005). See
http://support.microsoft.com/kb/823938.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Mehul" <Mehul@.discussions.microsoft.com> wrote in message
news:A80C2723-4EB2-4BD0-92D1-619DF2FCF527@.microsoft.com...
> On the below thread and similar issue, how can I hard code SQL Instance to
> use the same port number?
> Any suggestions?
> "Dan Guzman" wrote:
>> > Let me know if i have to open up UDP port 1434 too to get this to work.
>> Yes, you'll need to open up UDP port 1434 for named instance port
>> enumeration as well as the named instance port TCP port. Alternatively,
>> you
>> can create an alias for the named instance on the client machine and
>> specify
>> the named instance port number. You won't need to open UDP 1434 in that
>> case.
>>
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Hassan" <hassan@.hotmail.com> wrote in message
>> news:ueLdNA41HHA.1188@.TK2MSFTNGP04.phx.gbl...
>> > We are trying to connect to a SQL Server across the WAN. We can manage
>> > to
>> > ping the server and know that SQL Server is online on the other end as
>> > on
>> > the own internal network, we can connect to it.. but across the WAN, we
>> > cannot. We are thinking its a port issue that needs to be opened. So
>> > the
>> > question is do I only need to open the port that named instance is
>> > listening on or do I have to open up some other ports too. I believe
>> > for
>> > named instances, there is something to do with UDP port too. Let me
>> > know
>> > if i have to open up UDP port 1434 too to get this to work.
>> >
>> >
>> >
>>

Cannot seem to connect to named instance

We are trying to connect to a SQL Server across the WAN. We can manage to
ping the server and know that SQL Server is online on the other end as on
the own internal network, we can connect to it.. but across the WAN, we
cannot. We are thinking its a port issue that needs to be opened. So the
question is do I only need to open the port that named instance is listening
on or do I have to open up some other ports too. I believe for named
instances, there is something to do with UDP port too. Let me know if i have
to open up UDP port 1434 too to get this to work.> Let me know if i have to open up UDP port 1434 too to get this to work.
Yes, you'll need to open up UDP port 1434 for named instance port
enumeration as well as the named instance port TCP port. Alternatively, you
can create an alias for the named instance on the client machine and specify
the named instance port number. You won't need to open UDP 1434 in that
case.
Hope this helps.
Dan Guzman
SQL Server MVP
"Hassan" <hassan@.hotmail.com> wrote in message
news:ueLdNA41HHA.1188@.TK2MSFTNGP04.phx.gbl...
> We are trying to connect to a SQL Server across the WAN. We can manage to
> ping the server and know that SQL Server is online on the other end as on
> the own internal network, we can connect to it.. but across the WAN, we
> cannot. We are thinking its a port issue that needs to be opened. So the
> question is do I only need to open the port that named instance is
> listening on or do I have to open up some other ports too. I believe for
> named instances, there is something to do with UDP port too. Let me know
> if i have to open up UDP port 1434 too to get this to work.
>
>