Hope someone can explain why this happened.
I installed MSDE on a Winxp workstation.
I then setup clients to access MSDE via TCP/IP using the (Static) IP Address
address of the workstation.
Connection successful
I then removed MSDE2000 and installed MSDE2000 sp3a
Went I to connect to MSDE via TCP/IP and could not connect using the IP
When I changed to The machine name I could connect to MSDE2000
Anyone with any idea.
Server was winXP and workstations Win98 and Win08se.
Regards
Jeff
--
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.538 / Virus Database: 333 - Release Date: 10/11/2003Jeff Williams wrote:
> Hope someone can explain why this happened.
> I installed MSDE on a Winxp workstation.
> I then setup clients to access MSDE via TCP/IP using the (Static) IP
> Address address of the workstation.
> Connection successful
> I then removed MSDE2000 and installed MSDE2000 sp3a
> Went I to connect to MSDE via TCP/IP and could not connect using the
> IP When I changed to The machine name I could connect to MSDE2000
> Anyone with any idea.
> Server was winXP and workstations Win98 and Win08se.
> Regards
> Jeff
>
> --
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.538 / Virus Database: 333 - Release Date: 10/11/2003
Check that the Server (via sql server network utility) is configured to
use TCP/IP. Also check your client is configured like this too (client
network utility).
Br,
Mark Broadbent
mcdba , mcse+i
=============
Showing posts with label workstation. Show all posts
Showing posts with label workstation. Show all posts
Monday, March 19, 2012
Friday, February 24, 2012
Connecting legacy application to remote instance of SQL 2005 Express
Hi,
I've just done my first install of SQL 2005 Express and am having
problems connecting from a remote workstation using a VB6 application
that I believe used OLE DB/ADO.
I did get the application to connect, but only by installing an
instance on SQL Express on the remote workstation. I really think
there should be a lighter install that gets the required client
components onto the workstation.
I'm pasting a post I had made to another group below - this has all of
the steps I took in trying to get things connected.
Does anyone know of a better way to get remote workstations connected?
Thanks!
Glenn
I just did my first install of SQL 2005 Express yesterday (I know I'm
about a year behind!).
I ran into a problem connecting to the database from SO Administrator
from another workstation. Just wondering if anyone else has run into
this and found a better solution than I have...
1) Install SQL Server 2005 Express on the 'server'
2) Use the Surface Area Configuration tool to activate remote
connections over TCP/IP or Named Pipes.
3) Set the SQL Server Instance and the SQL Server Broser service to
auto
start
4) Restart SQL Server and Browser
5) At this point I can connect to the server usong SO Admin from my
laptop - which has SQL Server 2005 Developer Edition installed.
6) Attempt to connect from a workstation that has Store Operations 1.3
R1 and hotfix 1.3.1005 installed fails with the following message:
"You must connect to this server using SQL Server Managemnet
Studio or
SQL Server Management Objects (SMO)"
7) downloaded and installed "SQL Native Client" which appears to be
the
only thing that is supposed to be needed for a client to connect to a
SQL 2005 server. Same message from SO Administrator
8) ran the SQL Express installer on the workstation - selected ONLY
The
Client Components part of the install (deselected the default SQL
Engine
install). Same message from SO Admin
9) Ran SQL Express installer again, this time went ahead with the SQL
Engine install. SO Admin will now connect!
10) Ininstall SQL Express - Select to uninstall the SQL Engine
Instance,
but leave the Client Components. SO Admin Still connects!
This seems weird... Has anyone found a less convoluted way of getting
an RMS workstation to connect to a remote SQL 2005 Express database?
Thanks,
Glenn
Glenn Adams
Tiber Creek Consulting
http://www.tibercreek.com
glenn@.tibercreek.com
---
Please DO NOT respond to me directly but post all responses here in
the
newsgroup so that all can share the information.
Glenn Adams
Tiber Creek Consulting
http://www.tibercreek.com
glenn@.tibercreek.com
---
Please DO NOT respond to me directly but post all responses here in the
newsgroup so that all can share the information.If you are new to express these links should help. The first 3 are directly
related to your issue.
http://www.datamasker.com/SSE2005_NetworkCfg.htm Configuring Express
for Remote Access
https://blogs.msdn.com/sqlexpress/a.../05/415084.aspx
Configuring Remote Access
http://www.kbalertz.com/Feedback_914277.aspx Configuring SQL2005 for
remote access
http://msdn.microsoft.com/library/d...r />
rview.asp
Express Overview
http://msdn2.microsoft.com/en-us/library/ms165672.aspx Comparing Express
with MSDE
http://msdn.microsoft.com/sql/defau... />
erinst.asp
User Instances
http://msdn.microsoft.com/sql/expre...qlexcustapp.asp
Embedding Express in Apps
http://blogs.msdn.com/rogerwolterbl.../13/575974.aspx
Backing up Express
Automating Database maintenance in SQL 2005 Express Edition Part I
http://www.sqldbatips.com/showarticle.asp?ID=27
Automating Database maintenance in SQL 2005 Express Edition Part II
http://www.sqldbatips.com/showarticle.asp?ID=29
Andrew J. Kelly SQL MVP
"Glenn Adams [MVP - Retail Mgmt]" <glenn@.nospam.tibercreek.com> wrote in
message news:7pmpd2ticone4b2hpria46o035a4th1rge@.
4ax.com...
> Hi,
> I've just done my first install of SQL 2005 Express and am having
> problems connecting from a remote workstation using a VB6 application
> that I believe used OLE DB/ADO.
> I did get the application to connect, but only by installing an
> instance on SQL Express on the remote workstation. I really think
> there should be a lighter install that gets the required client
> components onto the workstation.
> I'm pasting a post I had made to another group below - this has all of
> the steps I took in trying to get things connected.
> Does anyone know of a better way to get remote workstations connected?
> Thanks!
> Glenn
> I just did my first install of SQL 2005 Express yesterday (I know I'm
> about a year behind!).
> I ran into a problem connecting to the database from SO Administrator
> from another workstation. Just wondering if anyone else has run into
> this and found a better solution than I have...
> 1) Install SQL Server 2005 Express on the 'server'
> 2) Use the Surface Area Configuration tool to activate remote
> connections over TCP/IP or Named Pipes.
> 3) Set the SQL Server Instance and the SQL Server Broser service to
> auto
> start
> 4) Restart SQL Server and Browser
> 5) At this point I can connect to the server usong SO Admin from my
> laptop - which has SQL Server 2005 Developer Edition installed.
> 6) Attempt to connect from a workstation that has Store Operations 1.3
> R1 and hotfix 1.3.1005 installed fails with the following message:
> "You must connect to this server using SQL Server Managemnet
> Studio or
> SQL Server Management Objects (SMO)"
> 7) downloaded and installed "SQL Native Client" which appears to be
> the
> only thing that is supposed to be needed for a client to connect to a
> SQL 2005 server. Same message from SO Administrator
> 8) ran the SQL Express installer on the workstation - selected ONLY
> The
> Client Components part of the install (deselected the default SQL
> Engine
> install). Same message from SO Admin
> 9) Ran SQL Express installer again, this time went ahead with the SQL
> Engine install. SO Admin will now connect!
> 10) Ininstall SQL Express - Select to uninstall the SQL Engine
> Instance,
> but leave the Client Components. SO Admin Still connects!
> This seems weird... Has anyone found a less convoluted way of getting
> an RMS workstation to connect to a remote SQL 2005 Express database?
> Thanks,
> Glenn
> --
> Glenn Adams
> Tiber Creek Consulting
> http://www.tibercreek.com
> glenn@.tibercreek.com
> ---
> Please DO NOT respond to me directly but post all responses here in
> the
> newsgroup so that all can share the information.
> Glenn Adams
> Tiber Creek Consulting
> http://www.tibercreek.com
> glenn@.tibercreek.com
> ---
> Please DO NOT respond to me directly but post all responses here in the
> newsgroup so that all can share the information.
I've just done my first install of SQL 2005 Express and am having
problems connecting from a remote workstation using a VB6 application
that I believe used OLE DB/ADO.
I did get the application to connect, but only by installing an
instance on SQL Express on the remote workstation. I really think
there should be a lighter install that gets the required client
components onto the workstation.
I'm pasting a post I had made to another group below - this has all of
the steps I took in trying to get things connected.
Does anyone know of a better way to get remote workstations connected?
Thanks!
Glenn
I just did my first install of SQL 2005 Express yesterday (I know I'm
about a year behind!).
I ran into a problem connecting to the database from SO Administrator
from another workstation. Just wondering if anyone else has run into
this and found a better solution than I have...
1) Install SQL Server 2005 Express on the 'server'
2) Use the Surface Area Configuration tool to activate remote
connections over TCP/IP or Named Pipes.
3) Set the SQL Server Instance and the SQL Server Broser service to
auto
start
4) Restart SQL Server and Browser
5) At this point I can connect to the server usong SO Admin from my
laptop - which has SQL Server 2005 Developer Edition installed.
6) Attempt to connect from a workstation that has Store Operations 1.3
R1 and hotfix 1.3.1005 installed fails with the following message:
"You must connect to this server using SQL Server Managemnet
Studio or
SQL Server Management Objects (SMO)"
7) downloaded and installed "SQL Native Client" which appears to be
the
only thing that is supposed to be needed for a client to connect to a
SQL 2005 server. Same message from SO Administrator
8) ran the SQL Express installer on the workstation - selected ONLY
The
Client Components part of the install (deselected the default SQL
Engine
install). Same message from SO Admin
9) Ran SQL Express installer again, this time went ahead with the SQL
Engine install. SO Admin will now connect!
10) Ininstall SQL Express - Select to uninstall the SQL Engine
Instance,
but leave the Client Components. SO Admin Still connects!
This seems weird... Has anyone found a less convoluted way of getting
an RMS workstation to connect to a remote SQL 2005 Express database?
Thanks,
Glenn
Glenn Adams
Tiber Creek Consulting
http://www.tibercreek.com
glenn@.tibercreek.com
---
Please DO NOT respond to me directly but post all responses here in
the
newsgroup so that all can share the information.
Glenn Adams
Tiber Creek Consulting
http://www.tibercreek.com
glenn@.tibercreek.com
---
Please DO NOT respond to me directly but post all responses here in the
newsgroup so that all can share the information.If you are new to express these links should help. The first 3 are directly
related to your issue.
http://www.datamasker.com/SSE2005_NetworkCfg.htm Configuring Express
for Remote Access
https://blogs.msdn.com/sqlexpress/a.../05/415084.aspx
Configuring Remote Access
http://www.kbalertz.com/Feedback_914277.aspx Configuring SQL2005 for
remote access
http://msdn.microsoft.com/library/d...r />
rview.asp
Express Overview
http://msdn2.microsoft.com/en-us/library/ms165672.aspx Comparing Express
with MSDE
http://msdn.microsoft.com/sql/defau... />
erinst.asp
User Instances
http://msdn.microsoft.com/sql/expre...qlexcustapp.asp
Embedding Express in Apps
http://blogs.msdn.com/rogerwolterbl.../13/575974.aspx
Backing up Express
Automating Database maintenance in SQL 2005 Express Edition Part I
http://www.sqldbatips.com/showarticle.asp?ID=27
Automating Database maintenance in SQL 2005 Express Edition Part II
http://www.sqldbatips.com/showarticle.asp?ID=29
Andrew J. Kelly SQL MVP
"Glenn Adams [MVP - Retail Mgmt]" <glenn@.nospam.tibercreek.com> wrote in
message news:7pmpd2ticone4b2hpria46o035a4th1rge@.
4ax.com...
> Hi,
> I've just done my first install of SQL 2005 Express and am having
> problems connecting from a remote workstation using a VB6 application
> that I believe used OLE DB/ADO.
> I did get the application to connect, but only by installing an
> instance on SQL Express on the remote workstation. I really think
> there should be a lighter install that gets the required client
> components onto the workstation.
> I'm pasting a post I had made to another group below - this has all of
> the steps I took in trying to get things connected.
> Does anyone know of a better way to get remote workstations connected?
> Thanks!
> Glenn
> I just did my first install of SQL 2005 Express yesterday (I know I'm
> about a year behind!).
> I ran into a problem connecting to the database from SO Administrator
> from another workstation. Just wondering if anyone else has run into
> this and found a better solution than I have...
> 1) Install SQL Server 2005 Express on the 'server'
> 2) Use the Surface Area Configuration tool to activate remote
> connections over TCP/IP or Named Pipes.
> 3) Set the SQL Server Instance and the SQL Server Broser service to
> auto
> start
> 4) Restart SQL Server and Browser
> 5) At this point I can connect to the server usong SO Admin from my
> laptop - which has SQL Server 2005 Developer Edition installed.
> 6) Attempt to connect from a workstation that has Store Operations 1.3
> R1 and hotfix 1.3.1005 installed fails with the following message:
> "You must connect to this server using SQL Server Managemnet
> Studio or
> SQL Server Management Objects (SMO)"
> 7) downloaded and installed "SQL Native Client" which appears to be
> the
> only thing that is supposed to be needed for a client to connect to a
> SQL 2005 server. Same message from SO Administrator
> 8) ran the SQL Express installer on the workstation - selected ONLY
> The
> Client Components part of the install (deselected the default SQL
> Engine
> install). Same message from SO Admin
> 9) Ran SQL Express installer again, this time went ahead with the SQL
> Engine install. SO Admin will now connect!
> 10) Ininstall SQL Express - Select to uninstall the SQL Engine
> Instance,
> but leave the Client Components. SO Admin Still connects!
> This seems weird... Has anyone found a less convoluted way of getting
> an RMS workstation to connect to a remote SQL 2005 Express database?
> Thanks,
> Glenn
> --
> Glenn Adams
> Tiber Creek Consulting
> http://www.tibercreek.com
> glenn@.tibercreek.com
> ---
> Please DO NOT respond to me directly but post all responses here in
> the
> newsgroup so that all can share the information.
> Glenn Adams
> Tiber Creek Consulting
> http://www.tibercreek.com
> glenn@.tibercreek.com
> ---
> Please DO NOT respond to me directly but post all responses here in the
> newsgroup so that all can share the information.
Tuesday, February 14, 2012
Connect to SSAS from SQL Management Studio
I'm trying to connect to an SSAS 2005 cube from my XP SP2 workstation. This is at a client's site & my workstation is not connected to their domain but they have given me a domain account & password that has access to the cube. My colleagues who are also running XP SP2 are able to browse to a UNC path on the SSAS server then when prompted enter the account & password. Then they go into SQL Management Studio to create a connection to the SSAS machine. But I can't locate anything different between our configurations. I'm also running Windows OneCare so I'm not sure if that may be the problem. Can you offer any suggestion please?
The trick with opening UNC share, entering credentials and then connecting to SSAS only works with NTLM authentication. Please make sure you are not on Kerberos. Also, it is important that you document the exact steps you do and exact outcomes (i.e. error messages if any etc) in order for the forum to help you.|||
I wasn't aware of that trick you mentioned. I would suggest one of the following:
1. Create yourself a shortcut with the following path:
C:\WINDOWS\SYSTEM32\RUNAS.EXE /net /user:TheirDomain\UserName "C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\SqlWb.exe"
That will launch Mgmt Studio under the credentials of the right domain account (not the account you've logged onto your laptop). Then you should be able to connect to SSAS on their server.
2. An alternative is if they've got Microsoft VPN, if you VPN to their network, then you don't have to bother with the runas command. (This appears to work when using Microsoft VPN, but not Cisco VPN, for example.)
Subscribe to:
Posts (Atom)