I already installed SQL Server 2000 and choose Windows authentication during
the setup. Can i still change to sql authentication now? I couldnt see such
options in Enterprise Manager. Please advise! ThanksRight click on the server in Enterprise Manager. Choose properties. Choose
the Security tab.
I hope this helps!
--
Brian Moran
Principal Mentor
Solid Quality Learning
SQL Server MVP
http://www.solidqualitylearning.com
"Matthew Louden" <mattloude@.hotmail.com> wrote in message
news:eEvUu8DxDHA.1736@.TK2MSFTNGP09.phx.gbl...
> I already installed SQL Server 2000 and choose Windows authentication
during
> the setup. Can i still change to sql authentication now? I couldnt see
such
> options in Enterprise Manager. Please advise! Thanks
>
Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts
Sunday, March 25, 2012
Monday, March 19, 2012
Can the SQL Server 2005 be installed on Windows 2003 SP1?
I recently attempted to install Windows 2003 SP1 on a machine on which someone had previously installed SQL Server 2005. The build number for the SQL Server 2005 installation is 9.0.1116. (BTW, which CTP is this build number?)
The installation of the service pack seemed to go okay, but I soon got calls from users reporting that they could not log in to the instance. I investigated, and discovered that the SQL Server service had not started. We were unable to start the service, and had to remove SP1.
This was the message I found in Event Viewer:
Event Type: Error
Event Source: SQLDUMPER
Event Category: None
Event ID: 5000
Date: 8/15/2005
Time: 10:30:30
User: N/A
Computer: YKOADS3
Description:
EventType sql90exception, P1 sqlservr.exe, P2 2000.90.1116.0, P3 4258cf76, P4 msvcrt.dll, P5 7.0.3790.1830, P6 4243785e, P7 0, P8 00038944, P9 a3a034ae, P10 NIL.
My questions are:
1) What happened?
2) Can I install the current CTP on Windows 2003 SP1?
That version corresponds to the April CTP of SQL Server.
You could log that as a bug in Product Feedback:
http://lab.msdn.microsoft.com/productfeedback/
Regards,
Vikram|||Well, if my issue occurred with the April CTP I see no need to log the issue now. I'm currently installing the June CTP, whose documentation says it works with 2003 SP1. I'll post the build number when I'm finished, as well as let everyone know the results.
Thanks for the reply,
Ken|||The Build number for June CTP needs is 9.0.1187. I have it running successfully on machine with Win2003 server with SP1. I installed SQL Server 2005 after installing SP1.
Regards,
Vikram|||
I installed the June CTP on Windows 2003 SP1 and I am up and running. Thanks.
Ken
Sunday, March 11, 2012
Can SSRS 2005 be installed on Windows XP SP2?
I installed SQL Server 2005 Developer edition on a Windows XP SP2 to run side by side with SQL Server 2000 dev edition and SSRS 2000.
Can SSRS 2005 be installed to run on Windows XP SP2?
Thanks
Yes you can.
I have RS2005 installed on my portable computer (with Windows XP SP 2) and it's work fine - even the development tool (VS2005). Of course you need to have IIS installed on your computer.
Good luck.
Thursday, March 8, 2012
Can sql server run on XP Pro?
Hi could anybody advise if Microsoft SQL Server Database would run on Windows XP Professional or would I need to install some server OS first like 2000 Server?You can run SQL Server 2000 Evaluation Edition and Developer Edition on
Windows XP Professional.
Windows XP Professional.
Check the Url for more details:
http://www.microsoft.com/sql/evaluation/sysreqs/2000/default.asp|||Yes, it can run on XP Pro. I have done it before.|||Thanks, I have downloaded evaluation edition on XP. To Pjmcb: do you mean you run the full version on XP Pro?I can get free software from my college but they would not give it to me without Server OS(which they are out of + I would need to change OS)|||I have ran the Standard Edition of SQL Server 2000 on XP Pro and 2000 Pro, no problem.
Can SQL Server Make A call to a Windows Service?
I have an application which needs to be able to use our local SQL server
database to get data (go figure, what else would it do right?). When the
data being sought is NOT in the database I need to be able to connect to a
MySQL database which is located... oh maybe 1500km. from here.
I use a Windows Service to do some time based updates from this remote site
already. I would like to be able to have the process work like this:
SQL server does lookup.
Data does not exist.
SQL server calls Windows Service to update database.
Windows Service Updates tables and makes data available.
Can I do this?
Does it matter that the windows service is running on .Net?
The firewall rules dictate that we can get data from them, but they cannot
push data to us. Since the transfer medium is the Internet I don't want the
SQL server to talk directly to the remote server. (I want to keep that
access closed).
Thanks.Am Wed, 16 Nov 2005 11:10:44 -0500 schrieb Roger Twomey:
> I have an application which needs to be able to use our local SQL server
> database to get data (go figure, what else would it do right?). When the
> data being sought is NOT in the database I need to be able to connect to a
> MySQL database which is located... oh maybe 1500km. from here.
> I use a Windows Service to do some time based updates from this remote sit
e
> already. I would like to be able to have the process work like this:
> SQL server does lookup.
> Data does not exist.
> SQL server calls Windows Service to update database.
.. till here no problems, You can do all this
> Windows Service Updates tables and makes data available.
> Can I do this?
> Does it matter that the windows service is running on .Net?
> The firewall rules dictate that we can get data from them, but they cannot
> push data to us. Since the transfer medium is the Internet I don't want th
e
> SQL server to talk directly to the remote server. (I want to keep that
> access closed).
> Thanks.
You are still not complete safe. Because somebody could capture the data
transfered from MySQL to SQL-Server, change it and send it to SQL-Server.
The only safe way would be VPN or SSL.
bye,
Helmut|||If you're using SQL2005 you can create a .net stored proc to call the
windows service.
If you're using SQL2000 you'll need to create a COM wrapper for the .NET
call.
research into: sp_OACreate, sp_OADestroy, sp_OAMethod, sp_OAGetProperty.
etc.
Thanks,
- Becky
"Roger Twomey" <rogerdev@.vnet.on.ca> wrote in message
news:uuQXkis6FHA.4076@.tk2msftngp13.phx.gbl...
> I have an application which needs to be able to use our local SQL server
> database to get data (go figure, what else would it do right?). When the
> data being sought is NOT in the database I need to be able to connect to a
> MySQL database which is located... oh maybe 1500km. from here.
> I use a Windows Service to do some time based updates from this remote
site
> already. I would like to be able to have the process work like this:
> SQL server does lookup.
> Data does not exist.
> SQL server calls Windows Service to update database.
> Windows Service Updates tables and makes data available.
> Can I do this?
> Does it matter that the windows service is running on .Net?
> The firewall rules dictate that we can get data from them, but they cannot
> push data to us. Since the transfer medium is the Internet I don't want
the
> SQL server to talk directly to the remote server. (I want to keep that
> access closed).
> Thanks.
>|||IIS allows free https setup. Do you think that would make this person
secure?
> Am Wed, 16 Nov 2005 11:10:44 -0500 schrieb Roger Twomey:
>
> .. till here no problems, You can do all this
>
> You are still not complete safe. Because somebody could capture the data
> transfered from MySQL to SQL-Server, change it and send it to SQL-Server.
> The only safe way would be VPN or SSL.
> bye,
> Helmut
new|||I don't know if you are a C++ programmer. If you are then you'll want to
research into extended stored procedures. We use this for WinInet/Winsock
communications as well as http/ftp and many other uses. Very powerful, very
fast, very dangerous if you don't know what you are doing.
> I have an application which needs to be able to use our local SQL server
> database to get data (go figure, what else would it do right?). When the
> data being sought is NOT in the database I need to be able to connect to a
> MySQL database which is located... oh maybe 1500km. from here.
> I use a Windows Service to do some time based updates from this remote
> site already. I would like to be able to have the process work like this:
> SQL server does lookup.
> Data does not exist.
> SQL server calls Windows Service to update database.
> Windows Service Updates tables and makes data available.
> Can I do this?
> Does it matter that the windows service is running on .Net?
> The firewall rules dictate that we can get data from them, but they cannot
> push data to us. Since the transfer medium is the Internet I don't want
> the SQL server to talk directly to the remote server. (I want to keep that
> access closed).
> Thanks.
new|||We don't have IIS on our SQL servers. We try to keep each server to a single
purpose, then secure it as much as we can.
"beginthreadex" <beginthreadex@.hotmail.com> wrote in message
news:OK0wyOt6FHA.2600@.tk2msftngp13.phx.gbl...
> IIS allows free https setup. Do you think that would make this person
> secure?
>
> --
> new|||I most definately am NOT a c++ programmer. I use vb.Net primarily.
Maybe some day I will get into C++, but only if there is a need. My brain is
pretty much full already!
;)
"beginthreadex" <beginthreadex@.hotmail.com> wrote in message
news:%23TKEtPt6FHA.2600@.tk2msftngp13.phx.gbl...
>I don't know if you are a C++ programmer. If you are then you'll want to
> research into extended stored procedures. We use this for WinInet/Winsock
> communications as well as http/ftp and many other uses. Very powerful,
> very
> fast, very dangerous if you don't know what you are doing.
>
> --
> new|||Thanks for the suggestion. I think your answer sounds the most promising,
and the most re-useable. There could be many other uses for the knowlege
once I have it.
Thanks.
"Rebecca York" <rebecca.york {at} 2ndbyte.com> wrote in message
news:437b60ce$0$138$7b0f0fd3@.mistral.news.newnet.co.uk...
> If you're using SQL2005 you can create a .net stored proc to call the
> windows service.
>
> If you're using SQL2000 you'll need to create a COM wrapper for the .NET
> call.
> research into: sp_OACreate, sp_OADestroy, sp_OAMethod,
> sp_OAGetProperty.
> etc.
>
> Thanks,
> - Becky
>
> "Roger Twomey" <rogerdev@.vnet.on.ca> wrote in message
> news:uuQXkis6FHA.4076@.tk2msftngp13.phx.gbl...
> site
> the
>
database to get data (go figure, what else would it do right?). When the
data being sought is NOT in the database I need to be able to connect to a
MySQL database which is located... oh maybe 1500km. from here.
I use a Windows Service to do some time based updates from this remote site
already. I would like to be able to have the process work like this:
SQL server does lookup.
Data does not exist.
SQL server calls Windows Service to update database.
Windows Service Updates tables and makes data available.
Can I do this?
Does it matter that the windows service is running on .Net?
The firewall rules dictate that we can get data from them, but they cannot
push data to us. Since the transfer medium is the Internet I don't want the
SQL server to talk directly to the remote server. (I want to keep that
access closed).
Thanks.Am Wed, 16 Nov 2005 11:10:44 -0500 schrieb Roger Twomey:
> I have an application which needs to be able to use our local SQL server
> database to get data (go figure, what else would it do right?). When the
> data being sought is NOT in the database I need to be able to connect to a
> MySQL database which is located... oh maybe 1500km. from here.
> I use a Windows Service to do some time based updates from this remote sit
e
> already. I would like to be able to have the process work like this:
> SQL server does lookup.
> Data does not exist.
> SQL server calls Windows Service to update database.
.. till here no problems, You can do all this
> Windows Service Updates tables and makes data available.
> Can I do this?
> Does it matter that the windows service is running on .Net?
> The firewall rules dictate that we can get data from them, but they cannot
> push data to us. Since the transfer medium is the Internet I don't want th
e
> SQL server to talk directly to the remote server. (I want to keep that
> access closed).
> Thanks.
You are still not complete safe. Because somebody could capture the data
transfered from MySQL to SQL-Server, change it and send it to SQL-Server.
The only safe way would be VPN or SSL.
bye,
Helmut|||If you're using SQL2005 you can create a .net stored proc to call the
windows service.
If you're using SQL2000 you'll need to create a COM wrapper for the .NET
call.
research into: sp_OACreate, sp_OADestroy, sp_OAMethod, sp_OAGetProperty.
etc.
Thanks,
- Becky
"Roger Twomey" <rogerdev@.vnet.on.ca> wrote in message
news:uuQXkis6FHA.4076@.tk2msftngp13.phx.gbl...
> I have an application which needs to be able to use our local SQL server
> database to get data (go figure, what else would it do right?). When the
> data being sought is NOT in the database I need to be able to connect to a
> MySQL database which is located... oh maybe 1500km. from here.
> I use a Windows Service to do some time based updates from this remote
site
> already. I would like to be able to have the process work like this:
> SQL server does lookup.
> Data does not exist.
> SQL server calls Windows Service to update database.
> Windows Service Updates tables and makes data available.
> Can I do this?
> Does it matter that the windows service is running on .Net?
> The firewall rules dictate that we can get data from them, but they cannot
> push data to us. Since the transfer medium is the Internet I don't want
the
> SQL server to talk directly to the remote server. (I want to keep that
> access closed).
> Thanks.
>|||IIS allows free https setup. Do you think that would make this person
secure?
> Am Wed, 16 Nov 2005 11:10:44 -0500 schrieb Roger Twomey:
>
> .. till here no problems, You can do all this
>
> You are still not complete safe. Because somebody could capture the data
> transfered from MySQL to SQL-Server, change it and send it to SQL-Server.
> The only safe way would be VPN or SSL.
> bye,
> Helmut
new|||I don't know if you are a C++ programmer. If you are then you'll want to
research into extended stored procedures. We use this for WinInet/Winsock
communications as well as http/ftp and many other uses. Very powerful, very
fast, very dangerous if you don't know what you are doing.
> I have an application which needs to be able to use our local SQL server
> database to get data (go figure, what else would it do right?). When the
> data being sought is NOT in the database I need to be able to connect to a
> MySQL database which is located... oh maybe 1500km. from here.
> I use a Windows Service to do some time based updates from this remote
> site already. I would like to be able to have the process work like this:
> SQL server does lookup.
> Data does not exist.
> SQL server calls Windows Service to update database.
> Windows Service Updates tables and makes data available.
> Can I do this?
> Does it matter that the windows service is running on .Net?
> The firewall rules dictate that we can get data from them, but they cannot
> push data to us. Since the transfer medium is the Internet I don't want
> the SQL server to talk directly to the remote server. (I want to keep that
> access closed).
> Thanks.
new|||We don't have IIS on our SQL servers. We try to keep each server to a single
purpose, then secure it as much as we can.
"beginthreadex" <beginthreadex@.hotmail.com> wrote in message
news:OK0wyOt6FHA.2600@.tk2msftngp13.phx.gbl...
> IIS allows free https setup. Do you think that would make this person
> secure?
>
> --
> new|||I most definately am NOT a c++ programmer. I use vb.Net primarily.
Maybe some day I will get into C++, but only if there is a need. My brain is
pretty much full already!
;)
"beginthreadex" <beginthreadex@.hotmail.com> wrote in message
news:%23TKEtPt6FHA.2600@.tk2msftngp13.phx.gbl...
>I don't know if you are a C++ programmer. If you are then you'll want to
> research into extended stored procedures. We use this for WinInet/Winsock
> communications as well as http/ftp and many other uses. Very powerful,
> very
> fast, very dangerous if you don't know what you are doing.
>
> --
> new|||Thanks for the suggestion. I think your answer sounds the most promising,
and the most re-useable. There could be many other uses for the knowlege
once I have it.
Thanks.
"Rebecca York" <rebecca.york {at} 2ndbyte.com> wrote in message
news:437b60ce$0$138$7b0f0fd3@.mistral.news.newnet.co.uk...
> If you're using SQL2005 you can create a .net stored proc to call the
> windows service.
>
> If you're using SQL2000 you'll need to create a COM wrapper for the .NET
> call.
> research into: sp_OACreate, sp_OADestroy, sp_OAMethod,
> sp_OAGetProperty.
> etc.
>
> Thanks,
> - Becky
>
> "Roger Twomey" <rogerdev@.vnet.on.ca> wrote in message
> news:uuQXkis6FHA.4076@.tk2msftngp13.phx.gbl...
> site
> the
>
can sql server 7 be installed on a windows XP environment?
my pc just got infected with the redloaf virus and i have to reformat it. will sql server 7 run on windows xp? is it compatible? if not, what OS would sql server 7 be compatible?Howdy
I doubt it - SQL 2000 cant be installed, so SQL 7 would be the same I'd say.
Cheers
SG|||Hi there,
I am running SQL Server 2000 on a WinXP Pro machine. So i would assume SQL 7 should go together with XP Pro.
Greetings,
Carsten|||You need the developer edition to install SQL 2000 on Windows XP.
Standard Edition does not install.
Probably the same as with SQL Server 7.
I doubt it - SQL 2000 cant be installed, so SQL 7 would be the same I'd say.
Cheers
SG|||Hi there,
I am running SQL Server 2000 on a WinXP Pro machine. So i would assume SQL 7 should go together with XP Pro.
Greetings,
Carsten|||You need the developer edition to install SQL 2000 on Windows XP.
Standard Edition does not install.
Probably the same as with SQL Server 7.
Can SQL Server 2005 run on Windows XP SP2
Hi
In "http://www.microsoft.com/sql/editions/standard/sysreqs.mspx" I read that
SQL Server 2005 Standard Edition can run on Windows XP SP2.
I am sure that I read some place that SQL Server 2005 Standard edition must
run on a server operating system.
Is this correct?
Regards Kjell Arne JohansenSQL Server 2005 Standard is supported on Windows XP SP2. It says so
on the box (so to speak) and it runs fine for me.
Not that I would use XP for a production server, but it is supported.
Roy Harvey
Beacon Falls, CT
On Wed, 11 Apr 2007 02:22:02 -0700, Kjell Arne Johansen
<KjellArneJohansen@.discussions.microsoft.com> wrote:
>Hi
>In "http://www.microsoft.com/sql/editions/standard/sysreqs.mspx" I read tha
t
>SQL Server 2005 Standard Edition can run on Windows XP SP2.
>I am sure that I read some place that SQL Server 2005 Standard edition must
>run on a server operating system.
>Is this correct?
>Regards Kjell Arne Johansen
>|||The confusion might be that 2000 SE needed a server OS. I was also surprised
when 2005 was released
that SE was supported on client OS. Not that I've tested it, but I haven't s
een any official text
saying anything different.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Roy Harvey" <roy_harvey@.snet.net> wrote in message
news:r91q1359bucp42mla7vmqubie557rma9nk@.
4ax.com...[vbcol=seagreen]
> SQL Server 2005 Standard is supported on Windows XP SP2. It says so
> on the box (so to speak) and it runs fine for me.
> Not that I would use XP for a production server, but it is supported.
> Roy Harvey
> Beacon Falls, CT
> On Wed, 11 Apr 2007 02:22:02 -0700, Kjell Arne Johansen
> <KjellArneJohansen@.discussions.microsoft.com> wrote:
>
In "http://www.microsoft.com/sql/editions/standard/sysreqs.mspx" I read that
SQL Server 2005 Standard Edition can run on Windows XP SP2.
I am sure that I read some place that SQL Server 2005 Standard edition must
run on a server operating system.
Is this correct?
Regards Kjell Arne JohansenSQL Server 2005 Standard is supported on Windows XP SP2. It says so
on the box (so to speak) and it runs fine for me.
Not that I would use XP for a production server, but it is supported.
Roy Harvey
Beacon Falls, CT
On Wed, 11 Apr 2007 02:22:02 -0700, Kjell Arne Johansen
<KjellArneJohansen@.discussions.microsoft.com> wrote:
>Hi
>In "http://www.microsoft.com/sql/editions/standard/sysreqs.mspx" I read tha
t
>SQL Server 2005 Standard Edition can run on Windows XP SP2.
>I am sure that I read some place that SQL Server 2005 Standard edition must
>run on a server operating system.
>Is this correct?
>Regards Kjell Arne Johansen
>|||The confusion might be that 2000 SE needed a server OS. I was also surprised
when 2005 was released
that SE was supported on client OS. Not that I've tested it, but I haven't s
een any official text
saying anything different.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Roy Harvey" <roy_harvey@.snet.net> wrote in message
news:r91q1359bucp42mla7vmqubie557rma9nk@.
4ax.com...[vbcol=seagreen]
> SQL Server 2005 Standard is supported on Windows XP SP2. It says so
> on the box (so to speak) and it runs fine for me.
> Not that I would use XP for a production server, but it is supported.
> Roy Harvey
> Beacon Falls, CT
> On Wed, 11 Apr 2007 02:22:02 -0700, Kjell Arne Johansen
> <KjellArneJohansen@.discussions.microsoft.com> wrote:
>
Can SQL Server 2005 run on Windows XP SP2
Hi
In "http://www.microsoft.com/sql/editions/standard/sysreqs.mspx" I read that
SQL Server 2005 Standard Edition can run on Windows XP SP2.
I am sure that I read some place that SQL Server 2005 Standard edition must
run on a server operating system.
Is this correct?
Regards Kjell Arne Johansen
SQL Server 2005 Standard is supported on Windows XP SP2. It says so
on the box (so to speak) and it runs fine for me.
Not that I would use XP for a production server, but it is supported.
Roy Harvey
Beacon Falls, CT
On Wed, 11 Apr 2007 02:22:02 -0700, Kjell Arne Johansen
<KjellArneJohansen@.discussions.microsoft.com> wrote:
>Hi
>In "http://www.microsoft.com/sql/editions/standard/sysreqs.mspx" I read that
>SQL Server 2005 Standard Edition can run on Windows XP SP2.
>I am sure that I read some place that SQL Server 2005 Standard edition must
>run on a server operating system.
>Is this correct?
>Regards Kjell Arne Johansen
>
|||The confusion might be that 2000 SE needed a server OS. I was also surprised when 2005 was released
that SE was supported on client OS. Not that I've tested it, but I haven't seen any official text
saying anything different.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Roy Harvey" <roy_harvey@.snet.net> wrote in message
news:r91q1359bucp42mla7vmqubie557rma9nk@.4ax.com... [vbcol=seagreen]
> SQL Server 2005 Standard is supported on Windows XP SP2. It says so
> on the box (so to speak) and it runs fine for me.
> Not that I would use XP for a production server, but it is supported.
> Roy Harvey
> Beacon Falls, CT
> On Wed, 11 Apr 2007 02:22:02 -0700, Kjell Arne Johansen
> <KjellArneJohansen@.discussions.microsoft.com> wrote:
In "http://www.microsoft.com/sql/editions/standard/sysreqs.mspx" I read that
SQL Server 2005 Standard Edition can run on Windows XP SP2.
I am sure that I read some place that SQL Server 2005 Standard edition must
run on a server operating system.
Is this correct?
Regards Kjell Arne Johansen
SQL Server 2005 Standard is supported on Windows XP SP2. It says so
on the box (so to speak) and it runs fine for me.
Not that I would use XP for a production server, but it is supported.
Roy Harvey
Beacon Falls, CT
On Wed, 11 Apr 2007 02:22:02 -0700, Kjell Arne Johansen
<KjellArneJohansen@.discussions.microsoft.com> wrote:
>Hi
>In "http://www.microsoft.com/sql/editions/standard/sysreqs.mspx" I read that
>SQL Server 2005 Standard Edition can run on Windows XP SP2.
>I am sure that I read some place that SQL Server 2005 Standard edition must
>run on a server operating system.
>Is this correct?
>Regards Kjell Arne Johansen
>
|||The confusion might be that 2000 SE needed a server OS. I was also surprised when 2005 was released
that SE was supported on client OS. Not that I've tested it, but I haven't seen any official text
saying anything different.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Roy Harvey" <roy_harvey@.snet.net> wrote in message
news:r91q1359bucp42mla7vmqubie557rma9nk@.4ax.com... [vbcol=seagreen]
> SQL Server 2005 Standard is supported on Windows XP SP2. It says so
> on the box (so to speak) and it runs fine for me.
> Not that I would use XP for a production server, but it is supported.
> Roy Harvey
> Beacon Falls, CT
> On Wed, 11 Apr 2007 02:22:02 -0700, Kjell Arne Johansen
> <KjellArneJohansen@.discussions.microsoft.com> wrote:
Wednesday, March 7, 2012
Can SQL Server 2005 run on Windows XP SP2
Hi
In "http://www.microsoft.com/sql/editions/standard/sysreqs.mspx" I read that
SQL Server 2005 Standard Edition can run on Windows XP SP2.
I am sure that I read some place that SQL Server 2005 Standard edition must
run on a server operating system.
Is this correct?
Regards Kjell Arne JohansenSQL Server 2005 Standard is supported on Windows XP SP2. It says so
on the box (so to speak) and it runs fine for me.
Not that I would use XP for a production server, but it is supported.
Roy Harvey
Beacon Falls, CT
On Wed, 11 Apr 2007 02:22:02 -0700, Kjell Arne Johansen
<KjellArneJohansen@.discussions.microsoft.com> wrote:
>Hi
>In "http://www.microsoft.com/sql/editions/standard/sysreqs.mspx" I read that
>SQL Server 2005 Standard Edition can run on Windows XP SP2.
>I am sure that I read some place that SQL Server 2005 Standard edition must
>run on a server operating system.
>Is this correct?
>Regards Kjell Arne Johansen
>|||The confusion might be that 2000 SE needed a server OS. I was also surprised when 2005 was released
that SE was supported on client OS. Not that I've tested it, but I haven't seen any official text
saying anything different.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Roy Harvey" <roy_harvey@.snet.net> wrote in message
news:r91q1359bucp42mla7vmqubie557rma9nk@.4ax.com...
> SQL Server 2005 Standard is supported on Windows XP SP2. It says so
> on the box (so to speak) and it runs fine for me.
> Not that I would use XP for a production server, but it is supported.
> Roy Harvey
> Beacon Falls, CT
> On Wed, 11 Apr 2007 02:22:02 -0700, Kjell Arne Johansen
> <KjellArneJohansen@.discussions.microsoft.com> wrote:
>>Hi
>>In "http://www.microsoft.com/sql/editions/standard/sysreqs.mspx" I read that
>>SQL Server 2005 Standard Edition can run on Windows XP SP2.
>>I am sure that I read some place that SQL Server 2005 Standard edition must
>>run on a server operating system.
>>Is this correct?
>>Regards Kjell Arne Johansen
In "http://www.microsoft.com/sql/editions/standard/sysreqs.mspx" I read that
SQL Server 2005 Standard Edition can run on Windows XP SP2.
I am sure that I read some place that SQL Server 2005 Standard edition must
run on a server operating system.
Is this correct?
Regards Kjell Arne JohansenSQL Server 2005 Standard is supported on Windows XP SP2. It says so
on the box (so to speak) and it runs fine for me.
Not that I would use XP for a production server, but it is supported.
Roy Harvey
Beacon Falls, CT
On Wed, 11 Apr 2007 02:22:02 -0700, Kjell Arne Johansen
<KjellArneJohansen@.discussions.microsoft.com> wrote:
>Hi
>In "http://www.microsoft.com/sql/editions/standard/sysreqs.mspx" I read that
>SQL Server 2005 Standard Edition can run on Windows XP SP2.
>I am sure that I read some place that SQL Server 2005 Standard edition must
>run on a server operating system.
>Is this correct?
>Regards Kjell Arne Johansen
>|||The confusion might be that 2000 SE needed a server OS. I was also surprised when 2005 was released
that SE was supported on client OS. Not that I've tested it, but I haven't seen any official text
saying anything different.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Roy Harvey" <roy_harvey@.snet.net> wrote in message
news:r91q1359bucp42mla7vmqubie557rma9nk@.4ax.com...
> SQL Server 2005 Standard is supported on Windows XP SP2. It says so
> on the box (so to speak) and it runs fine for me.
> Not that I would use XP for a production server, but it is supported.
> Roy Harvey
> Beacon Falls, CT
> On Wed, 11 Apr 2007 02:22:02 -0700, Kjell Arne Johansen
> <KjellArneJohansen@.discussions.microsoft.com> wrote:
>>Hi
>>In "http://www.microsoft.com/sql/editions/standard/sysreqs.mspx" I read that
>>SQL Server 2005 Standard Edition can run on Windows XP SP2.
>>I am sure that I read some place that SQL Server 2005 Standard edition must
>>run on a server operating system.
>>Is this correct?
>>Regards Kjell Arne Johansen
Can SQL server 2000 Enterprise Edition run in Windows XP?
Please help me here...I am a new user of sql server 2000 and a beginner in asp...We are making a web application and I have some problems with sql server 2000 in my windows XP.
1. I'm not connected in a network.
2. When I try to connect to sql server 2000 using this code:
<%
Dim CN
Dim RS
Set CN=Server.CreateObject("ADODB.Connection")
CN.Open "Provider=SQLOLEDB.1;uid=sa;Initial Catalog=Planetchow;"
Set RS = CN.Execute ("SELECT Restaurant_Id FROM RestaurantInfo")
While Not RS.EOF
Response.Write "<TR>"
Response.Write "<TD>" & RS.Fields("Restaurant_Id") & "</TD>"
Response.Write"</TR>"
RS.MoveNext
Wend
%>
I get this error message:
"Error Type:
Microsoft OLE DB Provider for SQL Server (0x80004005)
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection."
3. How come? What configurations do I have to make to be able to avoid this...
4. How do I connect to SQL server 2000 in ASP vbscript code?
Please I really need some help here...thank you!Go to enterprise manager and right click on the server and select properties then go to the tab that says security and make sure "SQL Server and Windows" is checked.
1. I'm not connected in a network.
2. When I try to connect to sql server 2000 using this code:
<%
Dim CN
Dim RS
Set CN=Server.CreateObject("ADODB.Connection")
CN.Open "Provider=SQLOLEDB.1;uid=sa;Initial Catalog=Planetchow;"
Set RS = CN.Execute ("SELECT Restaurant_Id FROM RestaurantInfo")
While Not RS.EOF
Response.Write "<TR>"
Response.Write "<TD>" & RS.Fields("Restaurant_Id") & "</TD>"
Response.Write"</TR>"
RS.MoveNext
Wend
%>
I get this error message:
"Error Type:
Microsoft OLE DB Provider for SQL Server (0x80004005)
Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection."
3. How come? What configurations do I have to make to be able to avoid this...
4. How do I connect to SQL server 2000 in ASP vbscript code?
Please I really need some help here...thank you!Go to enterprise manager and right click on the server and select properties then go to the tab that says security and make sure "SQL Server and Windows" is checked.
Can SQL 2008 coexist with SQL2005?
I have a SQL 2005 installed on my laptop with Windows XP Media Center Edition with the following components:
Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.1318
Operating System 5.1.2600
Is upgrade the only option or can SQL 2008 can exist with SQL2005?
Any help in instlling this would be helpful.
(Jayaram Krishnaswamy@.discussions.microsoft.com) writes: > I have a SQL 2005 installed on my laptop with Windows XP Media Center > Edition with the following components: > > > > Microsoft SQL Server Management Studio 9.00.1399.00 > Microsoft Analysis Services Client Tools 2005.090.1399.00 > Microsoft Data Access Components (MDAC) 2000.085.1117.00 > (xpsp_sp2_rtm.040803-2158) > Microsoft MSXML 2.6 3.0 4.0 5.0 6.0 > Microsoft Internet Explorer 6.0.2900.2180 > Microsoft .NET Framework 2.0.50727.1318 > Operating System 5.1.2600 > > > > Is upgrade the only option or can SQL 2008 can exist with SQL2005? You should be able to do a side-by-side installation, since you only have the client tools. But I strongly recommend that you install Katmai, or any other beta software, on a virtual machine, or a machine that you can afford to scrap and reformat. And do definitely not upgrade, if you want to keep the machine. By the way, I notice that you have the RTM version of the SQL 2005 tools. I would recommend that you get hold of SP2 and install that. It does bring quite a few improvements. -- Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||Thamk you very much. Could you rpovide me with links for setting up on a virtual machine?|||(Jayaram Krishnaswamy@.discussions.microsoft.com) writes: > Thamk you very much. Could you rpovide me with links for setting up on a > virtual machine? It's not difficult at all. There's two products on the market I know of, Virtual PC from Microsoft and VMware. I stick to VMware myself. You can download VMware worksation from http://www.vmware.com. The most difficult part is probably the amount for the license... Once you have it installed, you use the wizard to create a new machine. To install the OS, just insert the OS in your DVD player, and VMware will pick it up. From there, it's very much like a regular install. VMware also has a VMware Player which is free. I'm uncertain whether it's good for creating new machines. Virtual PC comes with MSDN, so financially you may find it more attractive. I never used VPC myself, but rumour has it that VMware is a little more able. A tip when you set up your virtual machine, you first install the OS, activates it, and also add other programs that you don't want to be without. Before you actually slap any beta software on it, clone the machine, and install the beta software on the clone. That is, keep a template machine, so that you don't have to install the OS for each new CTP that comes out. A second tip is to make sure that you have sufficient with memory in your host machine. 1.5 GB is a minimum, if you give 250 MB to the virtual machine. -- Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se Books Online for SQL Server 2005 at http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx Books Online for SQL Server 2000 at http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||Thanks for the advice. Much obliged
Saturday, February 25, 2012
Can SQL 2000 and WID coexist
My question is can the new version of MSDE (Windows Internal Database or SQL Express) reside on the server along with SQL 2000 without causing problems? We cannot upgrade the SQL 2000 because of an older application that doesn't work with SQL 2005. Currently we run WSUS 2.0 using MSDE and have no problems.
See replies to your similar post in the Getting Started with SQL Server forum.
Often, the quality of the responses received is related to our ability to ‘bounce’ ideas off of each other. In the future, to make it easier for us to offer you assistance, and to prevent folks from wasting time on already answered questions, please don't post to multiple newsgroups. Choose the one that best fits your question and post there. Only post to another newsgroup if you get no answer in a day or two (or if you accidentally posted to the wrong newsgroup –and you indicate that you've already posted elsewhere).
Thursday, February 16, 2012
Can report results be filtered by Windows user login?
Good morning,
I'm in the process of creating a report to show employees and managers holiday and absence information. Is there a way of filtering the results of the report based on who is running the report, so that employees could only see their own information and managers could only see theirs and their subordinates information?
What I was hoping to do was create a lookup table which cross-references Windows logins with employee numbers and then use this information to pass a parameter to the SQL query, but I don't know how to retrieve the login from the machine being used to view the report.
I've heard about row level security and it seems ideal in theory but I fear the implimentation of row level security would be far beyond my meagre knowledge.
Any constructive suggestions welcomed.
Thanks,
Paul
Hello Paul,
Whenever you create an expression, take a look under the Globals node. One your options is User!UserID, this will give you the Windows login of the user running the report.
Hope this helps.
Jarret
|||Jarret,
I came across the same solution a little earlier, works a treat.
Thanks,
Paul
Tuesday, February 14, 2012
can not view DTS Packages and Jobs
I have SQL 2k SP4 on Windows 2003
Can A sqlserver user, with out having SA role, see the DTS packages, Job and
their status ?
RK
Yes, partially, through some workarounds.
If you make a SQL Server user a member of the msdb database
TargetServersRole, they will be able to see all jobs and their statuses, but
will not be able to create or modify jobs. (So this does not work for
someone who should be able to create his own jobs. This is an undocumented
sideeffect of the role and will not work in SQL Server 2005. But 2005 has
specific new roles for granting various degrees of access to SQL Agent
jobs.)
If, instead of storing DTS packages as SQL Server objects, you store them as
files on a file share, then anyone who has rights to the file share
(read/only if you want that) can examine the contents of the DTS package, as
well. (If there is a workaround for examining DTS packages stored on the
server, I don't know it.)
RLF
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
>I have SQL 2k SP4 on Windows 2003
> Can A sqlserver user, with out having SA role, see the DTS packages, Job
> and
> their status ?
> --
> RK
|||Thank you Russel
I stored the DTS as stuctures storage file. What application/viewer do you
use the examine the contents ?
RK
"Russell Fields" wrote:
> Yes, partially, through some workarounds.
> If you make a SQL Server user a member of the msdb database
> TargetServersRole, they will be able to see all jobs and their statuses, but
> will not be able to create or modify jobs. (So this does not work for
> someone who should be able to create his own jobs. This is an undocumented
> sideeffect of the role and will not work in SQL Server 2005. But 2005 has
> specific new roles for granting various degrees of access to SQL Agent
> jobs.)
> If, instead of storing DTS packages as SQL Server objects, you store them as
> files on a file share, then anyone who has rights to the file share
> (read/only if you want that) can examine the contents of the DTS package, as
> well. (If there is a workaround for examining DTS packages stored on the
> server, I don't know it.)
> RLF
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
>
>
|||RK,
From Enterprise Manager you right-click on Data Transformation Services and
choose Open Package. It will then open a package from a structured storage
file into the DTS editor.
RLF
"RK73" <RK@.discussions.microsoft.com> wrote in message
news:7B708C46-D5CB-46B3-BCA8-9A91FA26C035@.microsoft.com...[vbcol=seagreen]
> Thank you Russel
> I stored the DTS as stuctures storage file. What application/viewer do you
> use the examine the contents ?
> --
> RK
>
> "Russell Fields" wrote:
Can A sqlserver user, with out having SA role, see the DTS packages, Job and
their status ?
RK
Yes, partially, through some workarounds.
If you make a SQL Server user a member of the msdb database
TargetServersRole, they will be able to see all jobs and their statuses, but
will not be able to create or modify jobs. (So this does not work for
someone who should be able to create his own jobs. This is an undocumented
sideeffect of the role and will not work in SQL Server 2005. But 2005 has
specific new roles for granting various degrees of access to SQL Agent
jobs.)
If, instead of storing DTS packages as SQL Server objects, you store them as
files on a file share, then anyone who has rights to the file share
(read/only if you want that) can examine the contents of the DTS package, as
well. (If there is a workaround for examining DTS packages stored on the
server, I don't know it.)
RLF
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
>I have SQL 2k SP4 on Windows 2003
> Can A sqlserver user, with out having SA role, see the DTS packages, Job
> and
> their status ?
> --
> RK
|||Thank you Russel
I stored the DTS as stuctures storage file. What application/viewer do you
use the examine the contents ?
RK
"Russell Fields" wrote:
> Yes, partially, through some workarounds.
> If you make a SQL Server user a member of the msdb database
> TargetServersRole, they will be able to see all jobs and their statuses, but
> will not be able to create or modify jobs. (So this does not work for
> someone who should be able to create his own jobs. This is an undocumented
> sideeffect of the role and will not work in SQL Server 2005. But 2005 has
> specific new roles for granting various degrees of access to SQL Agent
> jobs.)
> If, instead of storing DTS packages as SQL Server objects, you store them as
> files on a file share, then anyone who has rights to the file share
> (read/only if you want that) can examine the contents of the DTS package, as
> well. (If there is a workaround for examining DTS packages stored on the
> server, I don't know it.)
> RLF
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
>
>
|||RK,
From Enterprise Manager you right-click on Data Transformation Services and
choose Open Package. It will then open a package from a structured storage
file into the DTS editor.
RLF
"RK73" <RK@.discussions.microsoft.com> wrote in message
news:7B708C46-D5CB-46B3-BCA8-9A91FA26C035@.microsoft.com...[vbcol=seagreen]
> Thank you Russel
> I stored the DTS as stuctures storage file. What application/viewer do you
> use the examine the contents ?
> --
> RK
>
> "Russell Fields" wrote:
can not view DTS Packages and Jobs
I have SQL 2k SP4 on Windows 2003
Can A sqlserver user, with out having SA role, see the DTS packages, Job and
their status ?
--
RKYes, partially, through some workarounds.
If you make a SQL Server user a member of the msdb database
TargetServersRole, they will be able to see all jobs and their statuses, but
will not be able to create or modify jobs. (So this does not work for
someone who should be able to create his own jobs. This is an undocumented
sideeffect of the role and will not work in SQL Server 2005. But 2005 has
specific new roles for granting various degrees of access to SQL Agent
jobs.)
If, instead of storing DTS packages as SQL Server objects, you store them as
files on a file share, then anyone who has rights to the file share
(read/only if you want that) can examine the contents of the DTS package, as
well. (If there is a workaround for examining DTS packages stored on the
server, I don't know it.)
RLF
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
>I have SQL 2k SP4 on Windows 2003
> Can A sqlserver user, with out having SA role, see the DTS packages, Job
> and
> their status ?
> --
> RK|||Thank you Russel
I stored the DTS as stuctures storage file. What application/viewer do you
use the examine the contents ?
--
RK
"Russell Fields" wrote:
> Yes, partially, through some workarounds.
> If you make a SQL Server user a member of the msdb database
> TargetServersRole, they will be able to see all jobs and their statuses, b
ut
> will not be able to create or modify jobs. (So this does not work for
> someone who should be able to create his own jobs. This is an undocumented
> sideeffect of the role and will not work in SQL Server 2005. But 2005 has
> specific new roles for granting various degrees of access to SQL Agent
> jobs.)
> If, instead of storing DTS packages as SQL Server objects, you store them
as
> files on a file share, then anyone who has rights to the file share
> (read/only if you want that) can examine the contents of the DTS package,
as
> well. (If there is a workaround for examining DTS packages stored on the
> server, I don't know it.)
> RLF
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
>
>|||RK,
From Enterprise Manager you right-click on Data Transformation Services and
choose Open Package. It will then open a package from a structured storage
file into the DTS editor.
RLF
"RK73" <RK@.discussions.microsoft.com> wrote in message
news:7B708C46-D5CB-46B3-BCA8-9A91FA26C035@.microsoft.com...[vbcol=seagreen]
> Thank you Russel
> I stored the DTS as stuctures storage file. What application/viewer do you
> use the examine the contents ?
> --
> RK
>
> "Russell Fields" wrote:
>
Can A sqlserver user, with out having SA role, see the DTS packages, Job and
their status ?
--
RKYes, partially, through some workarounds.
If you make a SQL Server user a member of the msdb database
TargetServersRole, they will be able to see all jobs and their statuses, but
will not be able to create or modify jobs. (So this does not work for
someone who should be able to create his own jobs. This is an undocumented
sideeffect of the role and will not work in SQL Server 2005. But 2005 has
specific new roles for granting various degrees of access to SQL Agent
jobs.)
If, instead of storing DTS packages as SQL Server objects, you store them as
files on a file share, then anyone who has rights to the file share
(read/only if you want that) can examine the contents of the DTS package, as
well. (If there is a workaround for examining DTS packages stored on the
server, I don't know it.)
RLF
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
>I have SQL 2k SP4 on Windows 2003
> Can A sqlserver user, with out having SA role, see the DTS packages, Job
> and
> their status ?
> --
> RK|||Thank you Russel
I stored the DTS as stuctures storage file. What application/viewer do you
use the examine the contents ?
--
RK
"Russell Fields" wrote:
> Yes, partially, through some workarounds.
> If you make a SQL Server user a member of the msdb database
> TargetServersRole, they will be able to see all jobs and their statuses, b
ut
> will not be able to create or modify jobs. (So this does not work for
> someone who should be able to create his own jobs. This is an undocumented
> sideeffect of the role and will not work in SQL Server 2005. But 2005 has
> specific new roles for granting various degrees of access to SQL Agent
> jobs.)
> If, instead of storing DTS packages as SQL Server objects, you store them
as
> files on a file share, then anyone who has rights to the file share
> (read/only if you want that) can examine the contents of the DTS package,
as
> well. (If there is a workaround for examining DTS packages stored on the
> server, I don't know it.)
> RLF
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
>
>|||RK,
From Enterprise Manager you right-click on Data Transformation Services and
choose Open Package. It will then open a package from a structured storage
file into the DTS editor.
RLF
"RK73" <RK@.discussions.microsoft.com> wrote in message
news:7B708C46-D5CB-46B3-BCA8-9A91FA26C035@.microsoft.com...[vbcol=seagreen]
> Thank you Russel
> I stored the DTS as stuctures storage file. What application/viewer do you
> use the examine the contents ?
> --
> RK
>
> "Russell Fields" wrote:
>
can not view DTS Packages and Jobs
I have SQL 2k SP4 on Windows 2003
Can A sqlserver user, with out having SA role, see the DTS packages, Job and
their status ?
--
RKYes, partially, through some workarounds.
If you make a SQL Server user a member of the msdb database
TargetServersRole, they will be able to see all jobs and their statuses, but
will not be able to create or modify jobs. (So this does not work for
someone who should be able to create his own jobs. This is an undocumented
sideeffect of the role and will not work in SQL Server 2005. But 2005 has
specific new roles for granting various degrees of access to SQL Agent
jobs.)
If, instead of storing DTS packages as SQL Server objects, you store them as
files on a file share, then anyone who has rights to the file share
(read/only if you want that) can examine the contents of the DTS package, as
well. (If there is a workaround for examining DTS packages stored on the
server, I don't know it.)
RLF
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
>I have SQL 2k SP4 on Windows 2003
> Can A sqlserver user, with out having SA role, see the DTS packages, Job
> and
> their status ?
> --
> RK|||Thank you Russel
I stored the DTS as stuctures storage file. What application/viewer do you
use the examine the contents ?
--
RK
"Russell Fields" wrote:
> Yes, partially, through some workarounds.
> If you make a SQL Server user a member of the msdb database
> TargetServersRole, they will be able to see all jobs and their statuses, but
> will not be able to create or modify jobs. (So this does not work for
> someone who should be able to create his own jobs. This is an undocumented
> sideeffect of the role and will not work in SQL Server 2005. But 2005 has
> specific new roles for granting various degrees of access to SQL Agent
> jobs.)
> If, instead of storing DTS packages as SQL Server objects, you store them as
> files on a file share, then anyone who has rights to the file share
> (read/only if you want that) can examine the contents of the DTS package, as
> well. (If there is a workaround for examining DTS packages stored on the
> server, I don't know it.)
> RLF
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
> >I have SQL 2k SP4 on Windows 2003
> > Can A sqlserver user, with out having SA role, see the DTS packages, Job
> > and
> > their status ?
> > --
> > RK
>
>|||RK,
From Enterprise Manager you right-click on Data Transformation Services and
choose Open Package. It will then open a package from a structured storage
file into the DTS editor.
RLF
"RK73" <RK@.discussions.microsoft.com> wrote in message
news:7B708C46-D5CB-46B3-BCA8-9A91FA26C035@.microsoft.com...
> Thank you Russel
> I stored the DTS as stuctures storage file. What application/viewer do you
> use the examine the contents ?
> --
> RK
>
> "Russell Fields" wrote:
>> Yes, partially, through some workarounds.
>> If you make a SQL Server user a member of the msdb database
>> TargetServersRole, they will be able to see all jobs and their statuses,
>> but
>> will not be able to create or modify jobs. (So this does not work for
>> someone who should be able to create his own jobs. This is an
>> undocumented
>> sideeffect of the role and will not work in SQL Server 2005. But 2005
>> has
>> specific new roles for granting various degrees of access to SQL Agent
>> jobs.)
>> If, instead of storing DTS packages as SQL Server objects, you store them
>> as
>> files on a file share, then anyone who has rights to the file share
>> (read/only if you want that) can examine the contents of the DTS package,
>> as
>> well. (If there is a workaround for examining DTS packages stored on the
>> server, I don't know it.)
>> RLF
>> "RK73" <RK73@.discussions.microsoft.com> wrote in message
>> news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
>> >I have SQL 2k SP4 on Windows 2003
>> > Can A sqlserver user, with out having SA role, see the DTS packages,
>> > Job
>> > and
>> > their status ?
>> > --
>> > RK
>>
Can A sqlserver user, with out having SA role, see the DTS packages, Job and
their status ?
--
RKYes, partially, through some workarounds.
If you make a SQL Server user a member of the msdb database
TargetServersRole, they will be able to see all jobs and their statuses, but
will not be able to create or modify jobs. (So this does not work for
someone who should be able to create his own jobs. This is an undocumented
sideeffect of the role and will not work in SQL Server 2005. But 2005 has
specific new roles for granting various degrees of access to SQL Agent
jobs.)
If, instead of storing DTS packages as SQL Server objects, you store them as
files on a file share, then anyone who has rights to the file share
(read/only if you want that) can examine the contents of the DTS package, as
well. (If there is a workaround for examining DTS packages stored on the
server, I don't know it.)
RLF
"RK73" <RK73@.discussions.microsoft.com> wrote in message
news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
>I have SQL 2k SP4 on Windows 2003
> Can A sqlserver user, with out having SA role, see the DTS packages, Job
> and
> their status ?
> --
> RK|||Thank you Russel
I stored the DTS as stuctures storage file. What application/viewer do you
use the examine the contents ?
--
RK
"Russell Fields" wrote:
> Yes, partially, through some workarounds.
> If you make a SQL Server user a member of the msdb database
> TargetServersRole, they will be able to see all jobs and their statuses, but
> will not be able to create or modify jobs. (So this does not work for
> someone who should be able to create his own jobs. This is an undocumented
> sideeffect of the role and will not work in SQL Server 2005. But 2005 has
> specific new roles for granting various degrees of access to SQL Agent
> jobs.)
> If, instead of storing DTS packages as SQL Server objects, you store them as
> files on a file share, then anyone who has rights to the file share
> (read/only if you want that) can examine the contents of the DTS package, as
> well. (If there is a workaround for examining DTS packages stored on the
> server, I don't know it.)
> RLF
> "RK73" <RK73@.discussions.microsoft.com> wrote in message
> news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
> >I have SQL 2k SP4 on Windows 2003
> > Can A sqlserver user, with out having SA role, see the DTS packages, Job
> > and
> > their status ?
> > --
> > RK
>
>|||RK,
From Enterprise Manager you right-click on Data Transformation Services and
choose Open Package. It will then open a package from a structured storage
file into the DTS editor.
RLF
"RK73" <RK@.discussions.microsoft.com> wrote in message
news:7B708C46-D5CB-46B3-BCA8-9A91FA26C035@.microsoft.com...
> Thank you Russel
> I stored the DTS as stuctures storage file. What application/viewer do you
> use the examine the contents ?
> --
> RK
>
> "Russell Fields" wrote:
>> Yes, partially, through some workarounds.
>> If you make a SQL Server user a member of the msdb database
>> TargetServersRole, they will be able to see all jobs and their statuses,
>> but
>> will not be able to create or modify jobs. (So this does not work for
>> someone who should be able to create his own jobs. This is an
>> undocumented
>> sideeffect of the role and will not work in SQL Server 2005. But 2005
>> has
>> specific new roles for granting various degrees of access to SQL Agent
>> jobs.)
>> If, instead of storing DTS packages as SQL Server objects, you store them
>> as
>> files on a file share, then anyone who has rights to the file share
>> (read/only if you want that) can examine the contents of the DTS package,
>> as
>> well. (If there is a workaround for examining DTS packages stored on the
>> server, I don't know it.)
>> RLF
>> "RK73" <RK73@.discussions.microsoft.com> wrote in message
>> news:4401345C-6ABC-44EA-9756-EDD1133CDCE1@.microsoft.com...
>> >I have SQL 2k SP4 on Windows 2003
>> > Can A sqlserver user, with out having SA role, see the DTS packages,
>> > Job
>> > and
>> > their status ?
>> > --
>> > RK
>>
Sunday, February 12, 2012
Can not start SQL Agent
When I try to start SQL AGent I get the Following:
"An error 1722 (The RPC server is unavailable)"
Windows 2000, SQL 2000 sp3a.
The sql agent service is running.
Thanks
Dave.Make sure RPC services is running on the server but it may
be more likely that you have a problem with the permissions
set for the service account for SQL Agent. You can find the
required permissions in the following:
HOW TO: Change the SQL Server or SQL Server Agent Service
Account Without Using SQL Enterprise Manager in SQL Server
2000
http://support.microsoft.com/?id=283811
You can also find information on the permissions and service
accounts in books online under services accounts.
-Sue
On Fri, 24 Oct 2003 05:57:38 -0700, "David"
<anonymous@.discussions.microsoft.com> wrote:
>When I try to start SQL AGent I get the Following:
>"An error 1722 (The RPC server is unavailable)"
>Windows 2000, SQL 2000 sp3a.
>The sql agent service is running.
>Thanks
>Dave.
"An error 1722 (The RPC server is unavailable)"
Windows 2000, SQL 2000 sp3a.
The sql agent service is running.
Thanks
Dave.Make sure RPC services is running on the server but it may
be more likely that you have a problem with the permissions
set for the service account for SQL Agent. You can find the
required permissions in the following:
HOW TO: Change the SQL Server or SQL Server Agent Service
Account Without Using SQL Enterprise Manager in SQL Server
2000
http://support.microsoft.com/?id=283811
You can also find information on the permissions and service
accounts in books online under services accounts.
-Sue
On Fri, 24 Oct 2003 05:57:38 -0700, "David"
<anonymous@.discussions.microsoft.com> wrote:
>When I try to start SQL AGent I get the Following:
>"An error 1722 (The RPC server is unavailable)"
>Windows 2000, SQL 2000 sp3a.
>The sql agent service is running.
>Thanks
>Dave.
Can not start Service on install
Hi,
I've been looking for the past 4 hours why SQL Express doesn't install on my Windows XP home and Pro.
Almost at the end of install, the setup try to start the SQL Server Service. I can press either retry or cancel. Retry simply show again this message box, cancel rollback the last step (sql engine setup).
While the setup is at this message box, i've look around my system to see what can be wrong.
When i start the service manualy, it stop immediatly. But, if i copy paste the command line "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe" -sSQLEXPRESS
into a "cmd", it told me it can not open file "mssqlsystemresource.mdf" located on "d:\windows\temp\mkmaster_result\".
My D drive is my cd-rom which i did not used at all during setup (i download SQLEXPR from MSDN). To make it run, i unmap my cdrom and I "subst d: c:\".
The next error was about the other database files, so i copy everything.
Finaly, SQL Express start on the command box.
There was no way to connect to it, I try osql, sqlcmd and even telnet. Nothing work, telnet only connect, the two other can not find the server.
I then stoped the sqlservr.exe, and i try starting the service. It fail with the exact same error.
Both system are clean from other beta (only .NET 2 and SQL Express). But i did try C# express, which is uninstalled and did not cause any other problem on install.
I've look at a lot of place on internet, no install failure where identical to my problem.
I have no PDC (i'm in a workgroup).
Both system are Windows XP French, one is Home Ed. the other is Professional Ed.
The home Ed. have MSVS .NET 2003, the Pro Ed. have MSVS 6.
So here the logs:
- # MSSQL.1\MSSQL\LOG\ERRORLOG
2005-08-20 13:05:04.54 Server Microsoft SQL Server 2005 - 9.00.1187.07 (Intel X86)
May 24 2005 18:22:46
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2005-08-20 13:05:04.54 Server (c) 2005 Microsoft Corporation.
2005-08-20 13:05:04.56 Server All rights reserved.
2005-08-20 13:05:04.56 Server Server process ID is 4084.
2005-08-20 13:05:04.56 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2005-08-20 13:05:04.56 Server This instance of SQL Server last reported using a process ID of 3720 at 20/08/2005 11:52:46 (local) 20/08/2005 15:52:46 (UTC). This is an informational message only; no user action is required.
2005-08-20 13:05:04.56 Server Registry startup parameters:
2005-08-20 13:05:04.56 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2005-08-20 13:05:04.56 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2005-08-20 13:05:04.56 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2005-08-20 13:05:04.56 Server Command Line Startup Parameters:
2005-08-20 13:05:04.56 Server -s SQLEXPRESS
2005-08-20 13:05:04.57 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2005-08-20 13:05:04.59 Server Detected 1 CPUs. This is an informational message; no user action is required.
2005-08-20 13:05:04.60 Server Error: 8316, Severity: 16, State: 1.
2005-08-20 13:05:04.60 Server Cannot open registry key 'HKLM\SYSTEM\CurrentControlSet\Services\MSSQL$SQLEXPRESS\Performance'. SQL Server performance counters are disabled.
2005-08-20 13:05:04.65 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2005-08-20 13:05:04.68 Server Database mirroring has been enabled on this instance of SQL Server.
2005-08-20 13:05:04.70 spid5s Starting up database 'master'.
2005-08-20 13:05:04.85 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2005-08-20 13:05:04.96 spid5s SQL Trace ID 1 was started by login "sa".
2005-08-20 13:05:04.99 spid5s Starting up database 'mssqlsystemresource'.
2005-08-20 13:05:05.03 spid5s Error: 17207, Severity: 16, State: 1.
2005-08-20 13:05:05.03 spid5s FCB::Open: Operating system error 21(Le priphrique n'est pas prêt.) occurred while creating or opening file 'D:\WINDOWS\TEMP\mkmastr_result\mssqlsystemresource.mdf'. Diagnose and correct the operating system error, and retry the operation.
2005-08-20 13:05:05.04 spid5s Error: 17204, Severity: 16, State: 1.
2005-08-20 13:05:05.04 spid5s FCB::Open failed: Could not open file D:\WINDOWS\TEMP\mkmastr_result\mssqlsystemresource.mdf for file number 1. OS error: 21(Le priphrique n'est pas prêt.).
2005-08-20 13:05:05.04 spid5s Error: 5120, Severity: 16, State: 101.
2005-08-20 13:05:05.04 spid5s Unable to open the physical file "D:\WINDOWS\TEMP\mkmastr_result\mssqlsystemresource.mdf". Operating system error 21: "21(Le priphrique n'est pas prêt.)".
2005-08-20 13:05:05.07 spid5s Error: 17207, Severity: 16, State: 1.
2005-08-20 13:05:05.07 spid5s FileMgr::StartLogFiles: Operating system error 2(Le fichier spcifi est introuvable.) occurred while creating or opening file 'D:\WINDOWS\TEMP\mkmastr_result\mssqlsystemresource.ldf'. Diagnose and correct the operating system error, and retry the operation.
2005-08-20 13:05:05.09 spid5s File activation failure. The physical file name "D:\WINDOWS\TEMP\mkmastr_result\mssqlsystemresource.ldf" may be incorrect.
2005-08-20 13:05:05.09 spid5s Error: 945, Severity: 14, State: 2.
2005-08-20 13:05:05.09 spid5s Database 'mssqlsystemresource' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2005-08-20 13:05:05.10 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
-- #90\Setup Bootstrap\LOG\File\SQLSetup0010_SPITFIRE_SQL.log
Error Code: 1068
MSI (s) (B8!64) [14:21:05:562]: Product: Microsoft SQL Server 2005 Express Edition CTP -- 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 (1068) Le service ou le groupe de dpendance n'a pas pu dmarrer.
.
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 (1068) Le service ou le groupe de dpendance n'a pas pu dmarrer.
.
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_sqlScript
PerfTime Start: Do_sqlScript : Sat Aug 20 14:21:05 2005
Service MSSQL$SQLEXPRESS with parameters '-m -Q -qFrench_CI_AS -T4022 -T3659 -T3610 -T4010' is being started at Sat Aug 20 14:21:05 2005
Warning: VerQueryValue failed to get OriginalFileName for
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Bin\{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}sqlca.dll
with error
Info 1813.1813
Unable to start service (1068)
Error Code: 0x8007042c (1068)
Windows Error Text: Le service ou le groupe de dpendance n'a pas pu dmarrer.
Source File Name: sqlsetuplib\service.cpp
Compiler Timestamp: Tue May 10 13:18:21 2005
Function Name: sqls::Service::Start
Source Line Number: 303
((Translation)
Le service ou le groupe de dpendance n'a pas pu dmarrer.
The service or the dependencies group could not start.
)
--
Events Logs: I'll copy some event that are related to the issue.
Application:
The SQL Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b. Administrator should deregister this SPN manually to avoid client authentication errors.
System:
Le service SQL Server (SQLEXPRESS) dpend du service Ouverture de session rseau qui n'a pas pu dmarrer en raison de l'erreur : %%0
(SQL Service Server depends on "network session opening" which could not start due to error %%0)
Cet ordinateur est configur en tant que membre d'un groupe de travail, et non en tant que membre d'un domaine. Il n'est pas ncessaire d'excuter le service Accès rseau dans cette configuration.
(This computer is setup as a workgroup computer and not as a domain member. It's useless to run Network Access in this configuration)
--
With all these informmation, i don't know where to go. The Network Session service is not start and could not be start (lsass.exe). But, it is in my Process in Task Manager. Is it started or not? But since it's a Domain tool, i don't need it.
In the Requirement, I can not see anywhere we need to be on a Domain. Plus, it's impossible to connect a Win XP Home to a Domain, Win XP Home is supported.
I think i write all information i have on this failure.
Thanks,
Robert.
rlvladbob@.hotmail.com
Due to the length of time since this issue was posted, I'm marking it as resolved. If you're still in need of help, please respond here.
Paul
|||I'm having the same problem installing SQL Server 2005 Express on Windows XP. At the end of the installation, a message box appears stating:
TITLE: Microsoft SQL Server 2005 Setup
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."
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=setup.rll&EvtID=29503&EvtType=sqlsetuplib%5cservice.cpp%40Do_sqlScript%40sqls%3a%3aService%3a%3aStart%40x42b
BUTTONS:
&Retry
Cancel
I have tried to start the service manually several different ways. I also checked the service log on credentials and group policies.
In the event viewer, these are the errors:
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: 07/17/2007
Time: 11:16:28 PM
Description:
Product: Microsoft SQL Server 2005 Express Edition -- Error 29503. 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) The process terminated unexpectedly.
Any help? I've tried re-installing about 10 times.
|||Another user with the same problem. Windows application log says it can't write to the SQL ERRORLOG; changing the startup account to Local System gives error saying SQL trying to write to a non-existent drive. Anybody? I've cleaned the registry, retried, no luck.|||I also updated all my windows components, shut off my antivirus & spyware, made sure group policies & services were at default settings.
I was installing using the SQL Express default settings and even tried it from the administrator account.
Everything appeared to be installing correctly until it tried to start the service, then it failed and rolled back the installation every time.
I am not having any other problems on my computer. All the other Visual Studio 2005 Express programs installed flawlessly.
|||I also updated all my windows components, shut off my antivirus & spyware, made sure group policies & services were at default settings.
I was installing using the SQL Express default settings and even tried it from the administrator account.
Everything appeared to be installing correctly until it tried to start the service, then it failed and rolled back the installation every time.
I am not having any other problems on my computer. All the other Visual Studio 2005 Express programs installed flawlessly.
Appreciate any help.
|||
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Fri Sep 07 11:52:17 2007
Machine : SONYDESKTOP
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQLSupport_1.log
--
Machine : SONYDESKTOP
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQLNCLI_1.log
--
Machine : SONYDESKTOP
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SqlWriter_1.log
--
Machine : SONYDESKTOP
Product : MSXML 6.0 Parser
Product Version : 6.10.1129.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_MSXML6_1.log
--
Machine : SONYDESKTOP
Product : SQL Server Database Services
Error : 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."
--
Machine : SONYDESKTOP
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.2.3042.00
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQL.log
Last Action : InstallFinalize
Error String : 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 (1058) The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Error Number : 29503
--
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time : Fri Sep 07 11:56:47 2007
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_Core(Local).log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQLSupport_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQLNCLI_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SqlWriter_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_MSXML6_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQL.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SNAC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_Support.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SCC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_WI.log
I am running Windows Server 2003 R2 with SP2 installed. The server is 800 MHz, 1 GB Ram, 500 GB HDD. The preinstallation check said that it fulfilled minimum hardware requirements.
Exactly as what was stated initially in this forum, the SQL service fails to start. What's even more odd, before the installation starts, you can tell setup to not start the server automatically at the end of installation by unchecking the box for SQL server service. What makes this odd is setup actually ignores this setting and tries to start the service anyways, which forces me to hit cancel and rollback the installation.
My goal is to setup a demo of sharepoint on the server to use for a possible company intranet. It requires a database backend which normally comes with it, but sharepoint setup also crashes during installation for unknown reasons.
I would definitely like to know why none of these things work on a server OS...The server is currently acting as a DC, but I read that it doesn't matter.
Microsoft, can you please resolve this problem?! Thank you.
Can not start Service on install
Hi,
I've been looking for the past 4 hours why SQL Express doesn't install on my Windows XP home and Pro.
Almost at the end of install, the setup try to start the SQL Server Service. I can press either retry or cancel. Retry simply show again this message box, cancel rollback the last step (sql engine setup).
While the setup is at this message box, i've look around my system to see what can be wrong.
When i start the service manualy, it stop immediatly. But, if i copy paste the command line "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe" -sSQLEXPRESS
into a "cmd", it told me it can not open file "mssqlsystemresource.mdf" located on "d:\windows\temp\mkmaster_result\".
My D drive is my cd-rom which i did not used at all during setup (i download SQLEXPR from MSDN). To make it run, i unmap my cdrom and I "subst d: c:\".
The next error was about the other database files, so i copy everything.
Finaly, SQL Express start on the command box.
There was no way to connect to it, I try osql, sqlcmd and even telnet. Nothing work, telnet only connect, the two other can not find the server.
I then stoped the sqlservr.exe, and i try starting the service. It fail with the exact same error.
Both system are clean from other beta (only .NET 2 and SQL Express). But i did try C# express, which is uninstalled and did not cause any other problem on install.
I've look at a lot of place on internet, no install failure where identical to my problem.
I have no PDC (i'm in a workgroup).
Both system are Windows XP French, one is Home Ed. the other is Professional Ed.
The home Ed. have MSVS .NET 2003, the Pro Ed. have MSVS 6.
So here the logs:
- # MSSQL.1\MSSQL\LOG\ERRORLOG
2005-08-20 13:05:04.54 Server Microsoft SQL Server 2005 - 9.00.1187.07 (Intel X86)
May 24 2005 18:22:46
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2005-08-20 13:05:04.54 Server (c) 2005 Microsoft Corporation.
2005-08-20 13:05:04.56 Server All rights reserved.
2005-08-20 13:05:04.56 Server Server process ID is 4084.
2005-08-20 13:05:04.56 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2005-08-20 13:05:04.56 Server This instance of SQL Server last reported using a process ID of 3720 at 20/08/2005 11:52:46 (local) 20/08/2005 15:52:46 (UTC). This is an informational message only; no user action is required.
2005-08-20 13:05:04.56 Server Registry startup parameters:
2005-08-20 13:05:04.56 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2005-08-20 13:05:04.56 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2005-08-20 13:05:04.56 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2005-08-20 13:05:04.56 Server Command Line Startup Parameters:
2005-08-20 13:05:04.56 Server -s SQLEXPRESS
2005-08-20 13:05:04.57 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2005-08-20 13:05:04.59 Server Detected 1 CPUs. This is an informational message; no user action is required.
2005-08-20 13:05:04.60 Server Error: 8316, Severity: 16, State: 1.
2005-08-20 13:05:04.60 Server Cannot open registry key 'HKLM\SYSTEM\CurrentControlSet\Services\MSSQL$SQLEXPRESS\Performance'. SQL Server performance counters are disabled.
2005-08-20 13:05:04.65 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2005-08-20 13:05:04.68 Server Database mirroring has been enabled on this instance of SQL Server.
2005-08-20 13:05:04.70 spid5s Starting up database 'master'.
2005-08-20 13:05:04.85 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2005-08-20 13:05:04.96 spid5s SQL Trace ID 1 was started by login "sa".
2005-08-20 13:05:04.99 spid5s Starting up database 'mssqlsystemresource'.
2005-08-20 13:05:05.03 spid5s Error: 17207, Severity: 16, State: 1.
2005-08-20 13:05:05.03 spid5s FCB::Open: Operating system error 21(Le priphrique n'est pas prêt.) occurred while creating or opening file 'D:\WINDOWS\TEMP\mkmastr_result\mssqlsystemresource.mdf'. Diagnose and correct the operating system error, and retry the operation.
2005-08-20 13:05:05.04 spid5s Error: 17204, Severity: 16, State: 1.
2005-08-20 13:05:05.04 spid5s FCB::Open failed: Could not open file D:\WINDOWS\TEMP\mkmastr_result\mssqlsystemresource.mdf for file number 1. OS error: 21(Le priphrique n'est pas prêt.).
2005-08-20 13:05:05.04 spid5s Error: 5120, Severity: 16, State: 101.
2005-08-20 13:05:05.04 spid5s Unable to open the physical file "D:\WINDOWS\TEMP\mkmastr_result\mssqlsystemresource.mdf". Operating system error 21: "21(Le priphrique n'est pas prêt.)".
2005-08-20 13:05:05.07 spid5s Error: 17207, Severity: 16, State: 1.
2005-08-20 13:05:05.07 spid5s FileMgr::StartLogFiles: Operating system error 2(Le fichier spcifi est introuvable.) occurred while creating or opening file 'D:\WINDOWS\TEMP\mkmastr_result\mssqlsystemresource.ldf'. Diagnose and correct the operating system error, and retry the operation.
2005-08-20 13:05:05.09 spid5s File activation failure. The physical file name "D:\WINDOWS\TEMP\mkmastr_result\mssqlsystemresource.ldf" may be incorrect.
2005-08-20 13:05:05.09 spid5s Error: 945, Severity: 14, State: 2.
2005-08-20 13:05:05.09 spid5s Database 'mssqlsystemresource' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2005-08-20 13:05:05.10 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
-- #90\Setup Bootstrap\LOG\File\SQLSetup0010_SPITFIRE_SQL.log
Error Code: 1068
MSI (s) (B8!64) [14:21:05:562]: Product: Microsoft SQL Server 2005 Express Edition CTP -- 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 (1068) Le service ou le groupe de dpendance n'a pas pu dmarrer.
.
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 (1068) Le service ou le groupe de dpendance n'a pas pu dmarrer.
.
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_sqlScript
PerfTime Start: Do_sqlScript : Sat Aug 20 14:21:05 2005
Service MSSQL$SQLEXPRESS with parameters '-m -Q -qFrench_CI_AS -T4022 -T3659 -T3610 -T4010' is being started at Sat Aug 20 14:21:05 2005
Warning: VerQueryValue failed to get OriginalFileName for
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Bin\{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}sqlca.dll
with error
Info 1813.1813
Unable to start service (1068)
Error Code: 0x8007042c (1068)
Windows Error Text: Le service ou le groupe de dpendance n'a pas pu dmarrer.
Source File Name: sqlsetuplib\service.cpp
Compiler Timestamp: Tue May 10 13:18:21 2005
Function Name: sqls::Service::Start
Source Line Number: 303
((Translation)
Le service ou le groupe de dpendance n'a pas pu dmarrer.
The service or the dependencies group could not start.
)
--
Events Logs: I'll copy some event that are related to the issue.
Application:
The SQL Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b. Administrator should deregister this SPN manually to avoid client authentication errors.
System:
Le service SQL Server (SQLEXPRESS) dpend du service Ouverture de session rseau qui n'a pas pu dmarrer en raison de l'erreur : %%0
(SQL Service Server depends on "network session opening" which could not start due to error %%0)
Cet ordinateur est configur en tant que membre d'un groupe de travail, et non en tant que membre d'un domaine. Il n'est pas ncessaire d'excuter le service Accès rseau dans cette configuration.
(This computer is setup as a workgroup computer and not as a domain member. It's useless to run Network Access in this configuration)
--
With all these informmation, i don't know where to go. The Network Session service is not start and could not be start (lsass.exe). But, it is in my Process in Task Manager. Is it started or not? But since it's a Domain tool, i don't need it.
In the Requirement, I can not see anywhere we need to be on a Domain. Plus, it's impossible to connect a Win XP Home to a Domain, Win XP Home is supported.
I think i write all information i have on this failure.
Thanks,
Robert.
rlvladbob@.hotmail.com
Due to the length of time since this issue was posted, I'm marking it as resolved. If you're still in need of help, please respond here.
Paul
|||I'm having the same problem installing SQL Server 2005 Express on Windows XP. At the end of the installation, a message box appears stating:
TITLE: Microsoft SQL Server 2005 Setup
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."
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=setup.rll&EvtID=29503&EvtType=sqlsetuplib%5cservice.cpp%40Do_sqlScript%40sqls%3a%3aService%3a%3aStart%40x42b
BUTTONS:
&Retry
Cancel
I have tried to start the service manually several different ways. I also checked the service log on credentials and group policies.
In the event viewer, these are the errors:
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: 07/17/2007
Time: 11:16:28 PM
Description:
Product: Microsoft SQL Server 2005 Express Edition -- Error 29503. 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) The process terminated unexpectedly.
Any help? I've tried re-installing about 10 times.
|||Another user with the same problem. Windows application log says it can't write to the SQL ERRORLOG; changing the startup account to Local System gives error saying SQL trying to write to a non-existent drive. Anybody? I've cleaned the registry, retried, no luck.|||I also updated all my windows components, shut off my antivirus & spyware, made sure group policies & services were at default settings.
I was installing using the SQL Express default settings and even tried it from the administrator account.
Everything appeared to be installing correctly until it tried to start the service, then it failed and rolled back the installation every time.
I am not having any other problems on my computer. All the other Visual Studio 2005 Express programs installed flawlessly.
|||I also updated all my windows components, shut off my antivirus & spyware, made sure group policies & services were at default settings.
I was installing using the SQL Express default settings and even tried it from the administrator account.
Everything appeared to be installing correctly until it tried to start the service, then it failed and rolled back the installation every time.
I am not having any other problems on my computer. All the other Visual Studio 2005 Express programs installed flawlessly.
Appreciate any help.
|||
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Fri Sep 07 11:52:17 2007
Machine : SONYDESKTOP
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQLSupport_1.log
--
Machine : SONYDESKTOP
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQLNCLI_1.log
--
Machine : SONYDESKTOP
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SqlWriter_1.log
--
Machine : SONYDESKTOP
Product : MSXML 6.0 Parser
Product Version : 6.10.1129.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_MSXML6_1.log
--
Machine : SONYDESKTOP
Product : SQL Server Database Services
Error : 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."
--
Machine : SONYDESKTOP
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.2.3042.00
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQL.log
Last Action : InstallFinalize
Error String : 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 (1058) The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Error Number : 29503
--
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time : Fri Sep 07 11:56:47 2007
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_Core(Local).log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQLSupport_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQLNCLI_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SqlWriter_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_MSXML6_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQL.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SNAC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_Support.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SCC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_WI.log
Can not start Service on install
Hi,
I've been looking for the past 4 hours why SQL Express doesn't install on my Windows XP home and Pro.
Almost at the end of install, the setup try to start the SQL Server Service. I can press either retry or cancel. Retry simply show again this message box, cancel rollback the last step (sql engine setup).
While the setup is at this message box, i've look around my system to see what can be wrong.
When i start the service manualy, it stop immediatly. But, if i copy paste the command line "C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe" -sSQLEXPRESS
into a "cmd", it told me it can not open file "mssqlsystemresource.mdf" located on "d:\windows\temp\mkmaster_result\".
My D drive is my cd-rom which i did not used at all during setup (i download SQLEXPR from MSDN). To make it run, i unmap my cdrom and I "subst d: c:\".
The next error was about the other database files, so i copy everything.
Finaly, SQL Express start on the command box.
There was no way to connect to it, I try osql, sqlcmd and even telnet. Nothing work, telnet only connect, the two other can not find the server.
I then stoped the sqlservr.exe, and i try starting the service. It fail with the exact same error.
Both system are clean from other beta (only .NET 2 and SQL Express). But i did try C# express, which is uninstalled and did not cause any other problem on install.
I've look at a lot of place on internet, no install failure where identical to my problem.
I have no PDC (i'm in a workgroup).
Both system are Windows XP French, one is Home Ed. the other is Professional Ed.
The home Ed. have MSVS .NET 2003, the Pro Ed. have MSVS 6.
So here the logs:
- # MSSQL.1\MSSQL\LOG\ERRORLOG
2005-08-20 13:05:04.54 Server Microsoft SQL Server 2005 - 9.00.1187.07 (Intel X86)
May 24 2005 18:22:46
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 5.1 (Build 2600: Service Pack 2)
2005-08-20 13:05:04.54 Server (c) 2005 Microsoft Corporation.
2005-08-20 13:05:04.56 Server All rights reserved.
2005-08-20 13:05:04.56 Server Server process ID is 4084.
2005-08-20 13:05:04.56 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2005-08-20 13:05:04.56 Server This instance of SQL Server last reported using a process ID of 3720 at 20/08/2005 11:52:46 (local) 20/08/2005 15:52:46 (UTC). This is an informational message only; no user action is required.
2005-08-20 13:05:04.56 Server Registry startup parameters:
2005-08-20 13:05:04.56 Server -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2005-08-20 13:05:04.56 Server -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2005-08-20 13:05:04.56 Server -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2005-08-20 13:05:04.56 Server Command Line Startup Parameters:
2005-08-20 13:05:04.56 Server -s SQLEXPRESS
2005-08-20 13:05:04.57 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2005-08-20 13:05:04.59 Server Detected 1 CPUs. This is an informational message; no user action is required.
2005-08-20 13:05:04.60 Server Error: 8316, Severity: 16, State: 1.
2005-08-20 13:05:04.60 Server Cannot open registry key 'HKLM\SYSTEM\CurrentControlSet\Services\MSSQL$SQLEXPRESS\Performance'. SQL Server performance counters are disabled.
2005-08-20 13:05:04.65 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2005-08-20 13:05:04.68 Server Database mirroring has been enabled on this instance of SQL Server.
2005-08-20 13:05:04.70 spid5s Starting up database 'master'.
2005-08-20 13:05:04.85 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2005-08-20 13:05:04.96 spid5s SQL Trace ID 1 was started by login "sa".
2005-08-20 13:05:04.99 spid5s Starting up database 'mssqlsystemresource'.
2005-08-20 13:05:05.03 spid5s Error: 17207, Severity: 16, State: 1.
2005-08-20 13:05:05.03 spid5s FCB::Open: Operating system error 21(Le priphrique n'est pas prêt.) occurred while creating or opening file 'D:\WINDOWS\TEMP\mkmastr_result\mssqlsystemresource.mdf'. Diagnose and correct the operating system error, and retry the operation.
2005-08-20 13:05:05.04 spid5s Error: 17204, Severity: 16, State: 1.
2005-08-20 13:05:05.04 spid5s FCB::Open failed: Could not open file D:\WINDOWS\TEMP\mkmastr_result\mssqlsystemresource.mdf for file number 1. OS error: 21(Le priphrique n'est pas prêt.).
2005-08-20 13:05:05.04 spid5s Error: 5120, Severity: 16, State: 101.
2005-08-20 13:05:05.04 spid5s Unable to open the physical file "D:\WINDOWS\TEMP\mkmastr_result\mssqlsystemresource.mdf". Operating system error 21: "21(Le priphrique n'est pas prêt.)".
2005-08-20 13:05:05.07 spid5s Error: 17207, Severity: 16, State: 1.
2005-08-20 13:05:05.07 spid5s FileMgr::StartLogFiles: Operating system error 2(Le fichier spcifi est introuvable.) occurred while creating or opening file 'D:\WINDOWS\TEMP\mkmastr_result\mssqlsystemresource.ldf'. Diagnose and correct the operating system error, and retry the operation.
2005-08-20 13:05:05.09 spid5s File activation failure. The physical file name "D:\WINDOWS\TEMP\mkmastr_result\mssqlsystemresource.ldf" may be incorrect.
2005-08-20 13:05:05.09 spid5s Error: 945, Severity: 14, State: 2.
2005-08-20 13:05:05.09 spid5s Database 'mssqlsystemresource' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2005-08-20 13:05:05.10 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
-- #90\Setup Bootstrap\LOG\File\SQLSetup0010_SPITFIRE_SQL.log
Error Code: 1068
MSI (s) (B8!64) [14:21:05:562]: Product: Microsoft SQL Server 2005 Express Edition CTP -- 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 (1068) Le service ou le groupe de dpendance n'a pas pu dmarrer.
.
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 (1068) Le service ou le groupe de dpendance n'a pas pu dmarrer.
.
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_sqlScript
PerfTime Start: Do_sqlScript : Sat Aug 20 14:21:05 2005
Service MSSQL$SQLEXPRESS with parameters '-m -Q -qFrench_CI_AS -T4022 -T3659 -T3610 -T4010' is being started at Sat Aug 20 14:21:05 2005
Warning: VerQueryValue failed to get OriginalFileName for
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Bin\{2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}sqlca.dll
with error
Info 1813.1813
Unable to start service (1068)
Error Code: 0x8007042c (1068)
Windows Error Text: Le service ou le groupe de dpendance n'a pas pu dmarrer.
Source File Name: sqlsetuplib\service.cpp
Compiler Timestamp: Tue May 10 13:18:21 2005
Function Name: sqls::Service::Start
Source Line Number: 303
((Translation)
Le service ou le groupe de dpendance n'a pas pu dmarrer.
The service or the dependencies group could not start.
)
--
Events Logs: I'll copy some event that are related to the issue.
Application:
The SQL Network Interface library could not deregister the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b. Administrator should deregister this SPN manually to avoid client authentication errors.
System:
Le service SQL Server (SQLEXPRESS) dpend du service Ouverture de session rseau qui n'a pas pu dmarrer en raison de l'erreur : %%0
(SQL Service Server depends on "network session opening" which could not start due to error %%0)
Cet ordinateur est configur en tant que membre d'un groupe de travail, et non en tant que membre d'un domaine. Il n'est pas ncessaire d'excuter le service Accès rseau dans cette configuration.
(This computer is setup as a workgroup computer and not as a domain member. It's useless to run Network Access in this configuration)
--
With all these informmation, i don't know where to go. The Network Session service is not start and could not be start (lsass.exe). But, it is in my Process in Task Manager. Is it started or not? But since it's a Domain tool, i don't need it.
In the Requirement, I can not see anywhere we need to be on a Domain. Plus, it's impossible to connect a Win XP Home to a Domain, Win XP Home is supported.
I think i write all information i have on this failure.
Thanks,
Robert.
rlvladbob@.hotmail.com
Due to the length of time since this issue was posted, I'm marking it as resolved. If you're still in need of help, please respond here.
Paul
|||I'm having the same problem installing SQL Server 2005 Express on Windows XP. At the end of the installation, a message box appears stating:
TITLE: Microsoft SQL Server 2005 Setup
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."
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=setup.rll&EvtID=29503&EvtType=sqlsetuplib%5cservice.cpp%40Do_sqlScript%40sqls%3a%3aService%3a%3aStart%40x42b
BUTTONS:
&Retry
Cancel
I have tried to start the service manually several different ways. I also checked the service log on credentials and group policies.
In the event viewer, these are the errors:
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: 07/17/2007
Time: 11:16:28 PM
Description:
Product: Microsoft SQL Server 2005 Express Edition -- Error 29503. 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) The process terminated unexpectedly.
Any help? I've tried re-installing about 10 times.
|||Another user with the same problem. Windows application log says it can't write to the SQL ERRORLOG; changing the startup account to Local System gives error saying SQL trying to write to a non-existent drive. Anybody? I've cleaned the registry, retried, no luck.|||I also updated all my windows components, shut off my antivirus & spyware, made sure group policies & services were at default settings.
I was installing using the SQL Express default settings and even tried it from the administrator account.
Everything appeared to be installing correctly until it tried to start the service, then it failed and rolled back the installation every time.
I am not having any other problems on my computer. All the other Visual Studio 2005 Express programs installed flawlessly.
|||I also updated all my windows components, shut off my antivirus & spyware, made sure group policies & services were at default settings.
I was installing using the SQL Express default settings and even tried it from the administrator account.
Everything appeared to be installing correctly until it tried to start the service, then it failed and rolled back the installation every time.
I am not having any other problems on my computer. All the other Visual Studio 2005 Express programs installed flawlessly.
Appreciate any help.
|||
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Fri Sep 07 11:52:17 2007
Machine : SONYDESKTOP
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQLSupport_1.log
--
Machine : SONYDESKTOP
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQLNCLI_1.log
--
Machine : SONYDESKTOP
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SqlWriter_1.log
--
Machine : SONYDESKTOP
Product : MSXML 6.0 Parser
Product Version : 6.10.1129.0
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_MSXML6_1.log
--
Machine : SONYDESKTOP
Product : SQL Server Database Services
Error : 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."
--
Machine : SONYDESKTOP
Product : Microsoft SQL Server 2005 Express Edition
Product Version : 9.2.3042.00
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQL.log
Last Action : InstallFinalize
Error String : 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 (1058) The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Error Number : 29503
--
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time : Fri Sep 07 11:56:47 2007
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_Core(Local).log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQLSupport_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQLNCLI_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SqlWriter_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_MSXML6_1.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SQL.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SNAC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_Support.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_SCC.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_SONYDESKTOP_WI.log
Subscribe to:
Posts (Atom)