Showing posts with label winxp. Show all posts
Showing posts with label winxp. Show all posts

Tuesday, March 27, 2012

Cannot Register the server

I've installed an Instance of MSDE on a Win2k Machine and and WinXP Machine.
I'm able to register the Instances locally through EM (v.8.0), but when I
try to register them from a different PC with EM on it, I get the following
error.
SQL Server does not exist or access is denied. ConnectionOpen (Connect()
Is MSDE limited to local Enterprise Management?
Wack
This message will self destruct.
hi Ray,
Ray Lewis wrote:
> I've installed an Instance of MSDE on a Win2k Machine and and WinXP
> Machine. I'm able to register the Instances locally through EM
> (v.8.0), but when I try to register them from a different PC with EM
> on it, I get the following error.
> SQL Server does not exist or access is denied. ConnectionOpen
> (Connect()
> Is MSDE limited to local Enterprise Management?
please verify the network protocols are enabled via Server Network Utility
(svrnetcn.exe)...
MSDE installs by default disabling network protocols in order to prevent
external connections/attacks... you have to provide the
DISABLENETWORKPROTOCOLS=0
parameter at install time in order to force network protocols to be enable,
or, later afte install, use svrnetcn.exe to enable and configure the desired
protocol
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks. I finally discovered that. Also, on XP SP2, you need to allow port
1433 through the firewall.
Wack
This message will self destruct.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:38p2mrF5riea7U1@.individual.net...
> hi Ray,
> Ray Lewis wrote:
> please verify the network protocols are enabled via Server Network Utility
> (svrnetcn.exe)...
> MSDE installs by default disabling network protocols in order to prevent
> external connections/attacks... you have to provide the
> DISABLENETWORKPROTOCOLS=0
> parameter at install time in order to force network protocols to be
enable,
> or, later afte install, use svrnetcn.exe to enable and configure the
desired
> protocol
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>

Wednesday, March 7, 2012

Cannot install SQL Server 2005 Standard WinXP Pro SP2

Hello,

I have SQL Server 2000 Developer Edition already installed. Before starting
the SQL Server 2005 Standard setup, I exited the SQL server agent running in
my system tray.

I am logged on as Administrator and no other desktop apps are running. SQL
Server 2005 Setup reports several "Setup failed." error messages after the
install. I am choosing (for now) ONLY the workstation tools and books online
check mark. The installation presents a screen that says that these products
were successfully installed ("Setup finished"):
- MSXML6
- OWC11
- SQL Server Backward-Compatibility Files
However, these items have a red x next to them:
- SQL Server Books Online
- SQL Server Support Files
- SQLXML4
- SQL Native Client
- Workstation Components, Books Online, ...

My Setup log file terminates with a few messages--one of which contains the
words "Configuration failed." (This is the ONLY mention of the word "fail" in
the Setup log--see the excerpt below.)

Any ideas? I'm stuck without SQL Server 2005 running so this is a
productivity killer for me.

More info: Here is what I have done, to no avail:

1) Installed the OWC11 components using a direct download from Microsoft.
That install worked. But when it runs again from the SQL Server 2005 DVD, it
fails.
2) Logged on not as a user with Admin rights, but as ADMINISTRATOR. Same
results--the SQL Server 2005 Standard setup failed.
3) Installed SQL Server 2005 Express successfully. Afterwards, tried again
to install SQL Server 2005 Standard, and that setup failed.
4) Cleared registry values for SQL Server 2005 under HKLM.../Software as
described in KB article. Also deleted the installation folder ...90. Tried
again to install SQL Server 2005 Standard, and that setup failed.
5) Tried the 180-day trial of SQL Server 2005 Enterprise--to no avail. Same
results.

Found error logs but they did not help me pinpoint the root cause for the
failed installation.

Thank you,
-- Jonathan

SQLSetup0004_zzzzz_SQLNCLI_1.log Excerpt:
============================+
MSI (s) (60:90) [12:01:14:390]: Note: 1: 1729
MSI (s) (60:90) [12:01:14:406]: Product: Microsoft SQL Server Native Client
-- Configuration failed.

MSI (s) (60:90) [12:01:14:406]: Cleaning up uninstalled install packages, if
any exist
MSI (s) (60:90) [12:01:14:406]: MainEngineThread is returning 1603
MSI (s) (60:68) [12:01:14:406]: Destroying RemoteAPI object.
MSI (s) (60:9C) [12:01:14:406]: Custom Action Manager thread ending.
=== Logging stopped: 2/8/2007 12:01:14 ===
MSI (c) (8C:4C) [12:01:14:406]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (8C:4C) [12:01:14:406]: MainEngineThread is returning 1603
=== Verbose logging stopped: 2/8/2007 12:01:14 ===

As a first check have you disabled Anti-virus and Anti-firewall before installing?|||

Yes, anti-virus software is OFF and my XP Firewall is OFF.

I re-ran SQL Server 2005 Standard Setup, and here is some more information.

Setup Support files install properly.
Installation Wizard begins.
Status of ALL requirements is "Success".
Windows Installer launches.
I click Next on Serial Number screen after completing the form.
In Components to Install, I select only "Workstation components, Books Online and development tools"
A screen acknowledges that only Client Components will be installed.
I click Install.
A status dialog appears. Setup clearly begins to install files. Then it shows, one-by-one:

1. SQL Setup Support Files FAILED.
2. SQL Native Client FAILED.
3. OWC11 Setup finished.
4. Then I see "Removing backup files"
5. Then Sql Server Books Online failed, along with other failed statuses.

Any ideas?

|||

OK--If anyone cannot help on Microsoft TechNet, can anyone point me in the right direction on how to solve this issue?

1) Are there other web sites that might offer help?

2) Will Microsoft charge an incident fee for this issue since it appears to be a problem with Setup?

3) Does anyone have any suggestions?

This machine has Visual Studio 2003, Visual Studio 6, Macromedia 8, Adobe Photoshop CS2, IE7, and several other high-end products, such as InstallShield 12 Premium. All of those installed and are running without incident.

I can't imagine why SQL Server 2005 setup can't detect what's wrong and provide a successful installation.

Thank you.

|||Install sqlncli.msi before installing mssql2005.|||

Hello:

I ran the sqlncli.msi and received an error that I had a higher version already installed on my machine. I then used Add/Remove programs to remove the SQL Native Client--and then I re-ran sqlncli.msi successfully.

I then re-ran SQL Server 2005 Standard setup and received all the same installation errors already reported.

What now?

|||

I'm contacting Microsoft Support. I thank you for those who tried to help but it is a bit ridiculous to have a support group that can't even troubleshoot getting the product installed!

I will report the root cause here (if Microsoft is able to figure it out).

Thank you,

Jon500

Cannot install SQL Server 2005 Standard WinXP Pro SP2

Hello,

I have SQL Server 2000 Developer Edition already installed. Before starting
the SQL Server 2005 Standard setup, I exited the SQL server agent running in
my system tray.

I am logged on as Administrator and no other desktop apps are running. SQL
Server 2005 Setup reports several "Setup failed." error messages after the
install. I am choosing (for now) ONLY the workstation tools and books online
check mark. The installation presents a screen that says that these products
were successfully installed ("Setup finished"):
- MSXML6
- OWC11
- SQL Server Backward-Compatibility Files
However, these items have a red x next to them:
- SQL Server Books Online
- SQL Server Support Files
- SQLXML4
- SQL Native Client
- Workstation Components, Books Online, ...

My Setup log file terminates with a few messages--one of which contains the
words "Configuration failed." (This is the ONLY mention of the word "fail" in
the Setup log--see the excerpt below.)

Any ideas? I'm stuck without SQL Server 2005 running so this is a
productivity killer for me.

More info: Here is what I have done, to no avail:

1) Installed the OWC11 components using a direct download from Microsoft.
That install worked. But when it runs again from the SQL Server 2005 DVD, it
fails.
2) Logged on not as a user with Admin rights, but as ADMINISTRATOR. Same
results--the SQL Server 2005 Standard setup failed.
3) Installed SQL Server 2005 Express successfully. Afterwards, tried again
to install SQL Server 2005 Standard, and that setup failed.
4) Cleared registry values for SQL Server 2005 under HKLM.../Software as
described in KB article. Also deleted the installation folder ...90. Tried
again to install SQL Server 2005 Standard, and that setup failed.
5) Tried the 180-day trial of SQL Server 2005 Enterprise--to no avail. Same
results.

Found error logs but they did not help me pinpoint the root cause for the
failed installation.

Thank you,
-- Jonathan

SQLSetup0004_zzzzz_SQLNCLI_1.log Excerpt:
============================+
MSI (s) (60:90) [12:01:14:390]: Note: 1: 1729
MSI (s) (60:90) [12:01:14:406]: Product: Microsoft SQL Server Native Client
-- Configuration failed.

MSI (s) (60:90) [12:01:14:406]: Cleaning up uninstalled install packages, if
any exist
MSI (s) (60:90) [12:01:14:406]: MainEngineThread is returning 1603
MSI (s) (60:68) [12:01:14:406]: Destroying RemoteAPI object.
MSI (s) (60:9C) [12:01:14:406]: Custom Action Manager thread ending.
=== Logging stopped: 2/8/2007 12:01:14 ===
MSI (c) (8C:4C) [12:01:14:406]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (8C:4C) [12:01:14:406]: MainEngineThread is returning 1603
=== Verbose logging stopped: 2/8/2007 12:01:14 ===

As a first check have you disabled Anti-virus and Anti-firewall before installing?|||

Yes, anti-virus software is OFF and my XP Firewall is OFF.

I re-ran SQL Server 2005 Standard Setup, and here is some more information.

Setup Support files install properly.
Installation Wizard begins.
Status of ALL requirements is "Success".
Windows Installer launches.
I click Next on Serial Number screen after completing the form.
In Components to Install, I select only "Workstation components, Books Online and development tools"
A screen acknowledges that only Client Components will be installed.
I click Install.
A status dialog appears. Setup clearly begins to install files. Then it shows, one-by-one:

1. SQL Setup Support Files FAILED.
2. SQL Native Client FAILED.
3. OWC11 Setup finished.
4. Then I see "Removing backup files"
5. Then Sql Server Books Online failed, along with other failed statuses.

Any ideas?

|||

OK--If anyone cannot help on Microsoft TechNet, can anyone point me in the right direction on how to solve this issue?

1) Are there other web sites that might offer help?

2) Will Microsoft charge an incident fee for this issue since it appears to be a problem with Setup?

3) Does anyone have any suggestions?

This machine has Visual Studio 2003, Visual Studio 6, Macromedia 8, Adobe Photoshop CS2, IE7, and several other high-end products, such as InstallShield 12 Premium. All of those installed and are running without incident.

I can't imagine why SQL Server 2005 setup can't detect what's wrong and provide a successful installation.

Thank you.

|||Install sqlncli.msi before installing mssql2005.|||

Hello:

I ran the sqlncli.msi and received an error that I had a higher version already installed on my machine. I then used Add/Remove programs to remove the SQL Native Client--and then I re-ran sqlncli.msi successfully.

I then re-ran SQL Server 2005 Standard setup and received all the same installation errors already reported.

What now?

|||

I'm contacting Microsoft Support. I thank you for those who tried to help but it is a bit ridiculous to have a support group that can't even troubleshoot getting the product installed!

I will report the root cause here (if Microsoft is able to figure it out).

Thank you,

Jon500

Cannot install SQL Server 2005 CTP on WinXP Pro machine

Hi all,

I have tried to install SQL Server 2005 CTP version on my machine WinXP Pro
-1GB RAM but it gave me the following error.

/**********************************
The SQL Server System Configuration Checker cannot be executed due to WMI
configuration on the machine USPC180 Error:2147749896 (0x80041008).
*********************/

I have tried to do the following things but nothing helps.
A. To rebuild WMI
Start|Run|Command
1. type Mofcomp.exe %windir%\system32\wbem\cimwin32.mof and press enter.
2. type Regsvr32 wbemupgd.dll and press enter.
3. type regsvr32 wbemsvc.dll and press enter.

but step 1 was failed with access denied

B. To rebuild the WMI http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/reinstalling_wmi.asp

If you have any suggestions, please email to me at john_dang@.dril-quip.com

Regards,

John Dang

The following link has information on how to repair WMI

http://windowsxp.mvps.org/repairwmi.htm

Cannot install SQL Server 2005 CTP on WinXP Pro machine

Hi all,

I have tried to install SQL Server 2005 CTP version on my machine WinXP Pro
-1GB RAM but it gave me the following error.

/**********************************
The SQL Server System Configuration Checker cannot be executed due to WMI
configuration on the machine USPC180 Error:2147749896 (0x80041008).
*********************/

I have tried to do the following things but nothing helps.
A. To rebuild WMI
Start|Run|Command
1. type Mofcomp.exe %windir%\system32\wbem\cimwin32.mof and press enter.
2. type Regsvr32 wbemupgd.dll and press enter.
3. type regsvr32 wbemsvc.dll and press enter.

but step 1 was failed with access denied

B. To rebuild the WMI http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wmisdk/wmi/reinstalling_wmi.asp

If you have any suggestions, please email to me at john_dang@.dril-quip.com

Regards,

John Dang

The following link has information on how to repair WMI

http://windowsxp.mvps.org/repairwmi.htm

Cannot install SQL Server 2005 CTP on WinXP Pro machine

Hi all,
I have tried to install SQL Server 2005 CTP version on my machine WinXP Pro
-1GB RAM but it gave me the following error.
/**********************************
The SQL Server System Configuration Checker cannot be executed due to WMI
configuration on the machine USPC180 Error:2147749896 (0x80041008).
*********************/
I have tried to do the following things but nothing helps.
A. To rebuild WMI
Start|Run|Command
1. type Mofcomp.exe %windir%\system32\wbem\cimwin32.mof and press enter.
2. type Regsvr32 wbemupgd.dll and press enter.
3. type regsvr32 wbemsvc.dll and press enter.
but step 1 was failed with access denied
B. To rebuild the WMI
http://msdn.microsoft.com/library/de...alling_wmi.asp
If you have any suggestions, please email to me at john_dang@.dril-quip.com
Regards,
John Dang
Since SQL 2005 is still in beta, you'll want to post this in the Community
Newsgroups:
http://communities.microsoft.com/new...r2005&slcid=us
--Brian
(Please reply to the newsgroups only.)
"jdang" <jdang@.discussions.microsoft.com> wrote in message
news:0F2AA951-7079-482D-9621-51834198E769@.microsoft.com...
> Hi all,
> I have tried to install SQL Server 2005 CTP version on my machine WinXP
> Pro
> -1GB RAM but it gave me the following error.
> /**********************************
> The SQL Server System Configuration Checker cannot be executed due to WMI
> configuration on the machine USPC180 Error:2147749896 (0x80041008).
> *********************/
> I have tried to do the following things but nothing helps.
>
> A. To rebuild WMI
> Start|Run|Command
> 1. type Mofcomp.exe %windir%\system32\wbem\cimwin32.mof and press enter.
> 2. type Regsvr32 wbemupgd.dll and press enter.
> 3. type regsvr32 wbemsvc.dll and press enter.
> but step 1 was failed with access denied
> B. To rebuild the WMI
> http://msdn.microsoft.com/library/de...alling_wmi.asp
> If you have any suggestions, please email to me at john_dang@.dril-quip.com
> Regards,
> John Dang
>

Tuesday, February 14, 2012

Cannot generate SSPI context on laptop from different domain

Hi All,
I have Domain A with several SQL servers installed. One WinXP Pro laptop
user reports that he can't connect to any SQL server instances using Windows
authentication (the servers run win2k3 OS SP1 with SQL 2000 sp4 & 2005 sp1)
and gets the error:
Cannot generate SSPI context. (.Net SqlClient Data Provider)
His laptop is unique in that it's part of another domain, Domain B which has
no trust relationship with Domain A, nor should it. When he is in the office
at Domain A, he logs in to his laptop using cached domain credentials for
Domain B,and has entered a Managed Network Password entry for the SQL server
s
in Domain A.
It appears that if I have him log into his laptop using a local account
rather than his domain account (from Domain B) the Managed Network Password
entry works and he can successfully connect to the SQL servers on Domain A.
Any suggestions on how I can get the Windows security token of the user
account to successfully connect to SQL Server in this situation where he is
using cached domain credentials (Domain B) with a Managed Network Password
(For Domain A). I would prefer not to make a trust between the domains while
still allowing him to connect to SQL using his existing laptop profile.
Thanks!Hi,
I understand that you would like to establish a connection from your laptop
computer in domain B to your SQL Server instance in domain A. The two
separated domains are non-trusted.
If I have misunderstood, please let me know.
As far as I know, if two separated domains have no trust relationship, any
one of the two domains could not connect to the other's SQL Server
instances with Windows Authentication by using its peer domain's user
account. To establish a connection, you can create a same local user
account with the same password on both of the computers which belong to the
two different domains. Cached domain account may have permission to access
the share resources in domain B; however it could not be used to connect to
SQL Server instance. That is not secure.
Appreciate your understanding on this limitation. If you have any other
questions or concerns, please feel free to let us know. Have a good day!
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscript...t/default.aspx.
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Hi,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Charles Wang
Microsoft Online Community Support
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============|||Hey Charles,
Thanks for the suggestion and explanation.
If I understand the workaround you suggest it's similar to the workaround I
implemented in that the user logs into his laptop using a local account
rather than his domain account (cached from Domain B), I then added a Manage
d
Network Password entry for a domain user account for the user in Domain A an
d
he can then successfully connect to the SQL servers on Domain A.
The problem is caused by the fact that the laptop is part of Domain B and
there is no trust relationship set up between the domains. I wanted to solve
the problem by getting the Managed Network Password entry to work while he i
s
logged in to his laptop with his domain account cached from Domain B.
However, I understand from your explanation that this is not feasible.
"Charles Wang[MSFT]" wrote:

> Hi,
> I am interested in this issue. Would you mind letting me know the result o
f
> the suggestions? If you need further assistance, feel free to let me know.
> I will be more than happy to be of assistance.
> Charles Wang
> Microsoft Online Community Support
> ========================================
==============
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ========================================
==============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> ========================================
==============
>|||Hi Matt,
Thanks for your response.
Appreciate your understanding that this is a by design limitation. If it is
allowed, SQL Server may face many security issues. At least a simple
scenario that we can imagine is that any other users can use this cache
accout to attack SQL Server.
Your workaround is similar as my suggested workaround. Both of them are
safe, since any user who wants to use the user account to log in SQL Server
must know the correct password. For a cache account, we may just know its
user name, but do not know its password, so there may be potential security
problem if it is allowed to be used to connect to SQL Server.
Please feel free to let me know if you need further assistance on this
issue. Have a good day!
Best regards,
Charles Wang
Microsoft Online Community Support
========================================
=============
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscript...ault.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscript...t/default.aspx.
========================================
==============
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
========================================
==============
This posting is provided "AS IS" with no warranties, and confers no rights.
========================================
==============

Cannot generate SSPI context on laptop from different domain

Hi All,
I have Domain A with several SQL servers installed. One WinXP Pro laptop
user reports that he can't connect to any SQL server instances using Windows
authentication (the servers run win2k3 OS SP1 with SQL 2000 sp4 & 2005 sp1)
and gets the error:
Cannot generate SSPI context. (.Net SqlClient Data Provider)
His laptop is unique in that it's part of another domain, Domain B which has
no trust relationship with Domain A, nor should it. When he is in the office
at Domain A, he logs in to his laptop using cached domain credentials for
Domain B,and has entered a Managed Network Password entry for the SQL servers
in Domain A.
It appears that if I have him log into his laptop using a local account
rather than his domain account (from Domain B) the Managed Network Password
entry works and he can successfully connect to the SQL servers on Domain A.
Any suggestions on how I can get the Windows security token of the user
account to successfully connect to SQL Server in this situation where he is
using cached domain credentials (Domain B) with a Managed Network Password
(For Domain A). I would prefer not to make a trust between the domains while
still allowing him to connect to SQL using his existing laptop profile.
Thanks!
Hi,
I understand that you would like to establish a connection from your laptop
computer in domain B to your SQL Server instance in domain A. The two
separated domains are non-trusted.
If I have misunderstood, please let me know.
As far as I know, if two separated domains have no trust relationship, any
one of the two domains could not connect to the other's SQL Server
instances with Windows Authentication by using its peer domain's user
account. To establish a connection, you can create a same local user
account with the same password on both of the computers which belong to the
two different domains. Cached domain account may have permission to access
the share resources in domain B; however it could not be used to connect to
SQL Server instance. That is not secure.
Appreciate your understanding on this limitation. If you have any other
questions or concerns, please feel free to let us know. Have a good day!
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Hi,
I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.
Charles Wang
Microsoft Online Community Support
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====
|||Hey Charles,
Thanks for the suggestion and explanation.
If I understand the workaround you suggest it's similar to the workaround I
implemented in that the user logs into his laptop using a local account
rather than his domain account (cached from Domain B), I then added a Managed
Network Password entry for a domain user account for the user in Domain A and
he can then successfully connect to the SQL servers on Domain A.
The problem is caused by the fact that the laptop is part of Domain B and
there is no trust relationship set up between the domains. I wanted to solve
the problem by getting the Managed Network Password entry to work while he is
logged in to his laptop with his domain account cached from Domain B.
However, I understand from your explanation that this is not feasible.
"Charles Wang[MSFT]" wrote:

> Hi,
> I am interested in this issue. Would you mind letting me know the result of
> the suggestions? If you need further assistance, feel free to let me know.
> I will be more than happy to be of assistance.
> Charles Wang
> Microsoft Online Community Support
> ================================================== ====
> When responding to posts, please "Reply to Group" via
> your newsreader so that others may learn and benefit
> from this issue.
> ================================================== ====
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ================================================== ====
>
|||Hi Matt,
Thanks for your response.
Appreciate your understanding that this is a by design limitation. If it is
allowed, SQL Server may face many security issues. At least a simple
scenario that we can imagine is that any other users can use this cache
accout to attack SQL Server.
Your workaround is similar as my suggested workaround. Both of them are
safe, since any user who wants to use the user account to log in SQL Server
must know the correct password. For a cache account, we may just know its
user name, but do not know its password, so there may be potential security
problem if it is allowed to be used to connect to SQL Server.
Please feel free to let me know if you need further assistance on this
issue. Have a good day!
Best regards,
Charles Wang
Microsoft Online Community Support
================================================== ===
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
================================================== ====
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== ====