connot connect to the repository with Analysis Service

I have a problem with Analysis Services.

When I open Analysis Manager and try to connect to the SQL server with Analysis Service, the following error message is displayed:

"connot connect to the repository. Error:Could not use ''; file already in use."

the server and my local machine all both using SQL server 2000 with SP4

any help will be appreciate, thanks in advance.

Benjamin

Looks like your repository is not migrated to SQL Server, but still in msmdrep.mdb file. Do you have enough permissions to open it ? Do you have access to $MsOlapRepository share ?

Connects but network error, Im behind Wingate

Hello.

I'm trying to connect to SQL Server using Enterprise manager. I'm behind a Wingate proxy.

I've configured an alias using TCP/IP, pointing to the (local network) IP of the Wingate box.

On the Wingate box I've set a TCP Mapping service on port 1433, pointing to the IP of the remote SQL Server on port 1433 too.

The error message is:
General network error. Changed language settings to us-english. ConnectionRead(Error SIO_KEEPALIVE_VALS())..

I assume at least *something* is right, as if I change the password to a bogus one I get "Login failed" instead of this network error.

Hope someone can point me in the right direction. Thanks,
- ManuelYou probably need to enable UDP port 1434 as well. See MSDN (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1zuc.asp) for a more complete explaination.

-PatP|||Hello.

Just added UDP mapping on 1434. Same error.

Read the MSDN article but couldn't figure what else to try. Just in case I didn't make myself clear, I'm trying to connect to a server outside my local network (as opposed to enabling a server on my network to be seen on the internet).

How can I debug this forward? What else can I do?

Thanks again,
- Manuel|||Check the Wingate log, and look to see what traffic is blocked from the workstation headed toward the server's IP address. It should be on port 1433 unless you are using a named instance of SQL Server, but look for anything, just in case.

Triple check to be sure that your Client Network Settings (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_client_7v03.asp) and the server's Server Network Settings (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_2epl.asp) are compatible, especially if they are using a Proxy (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_1_server_1y5u.asp).

-PatP|||As referred by Pat ensure both client & server's netlibs are similar, by chance are you running on cluster?

Try to use Named-pipes instead of Tcp/IP.

Information about Orphaned sessions (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/trblsql/tr_rptconsetup_5gmr.asp) from this mSDN link.

HTH

connectivity error while registering a new group

While registering sqlserver group I am getting the following
error message
"You must upgrade your SQL Enterprise Manager and SQL DMO (SQL-OLE) to SQL server (SQL DMO) to connect to server."
Can any one please guide me how to overcome this proble.
thanx regardsLook at Knowledge Base Article:

HOW TO: Administer Different Versions of SQL Server by Using SQL Server Enterprise Manager (http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q225/5/45.asp&NoWebContent=1)sqlsql

ConnectionManagerOleDb usage in a Script Component

Hi,

I have a need to use a shared connection manager of type OLEDB inside a Script Component. I guess that the right way to get the OLEDB connection is to override the AcquireConnections method, case the shared connection manager to the ConnectionManagerOleDb interface and call the AcquireConnection method.

The problem is in the return value of the AcquireConnection method (it’s Object). My assumption is that in case of OLEDB connection usage, the AcquireConnection method returns some OLE DB COM interface. Does some of you tried to cast it to some interface/class exposed by DTS (or some standard COM interface from MDAC)?

PS I’m aware about the possibility to use ADO.NET connection managers, however it’s not a case for me because of DataReader Source limitations (OLE DB Source suits my needs much better).

I would really appreciate your answer. Thanks in advance!

Regards,

Dmytro

Hi,

I am not using override acquireconnection method for sharing connections. Instead of that I have created a global connection and created a property for opening the connection. Inside the property, if it is null I will open a new connection, otherwise I will return the existing connection. I have overriden the 'releaseconnection' method, to release that connection. It is working fine. Hope this would help u.

|||

Hi,

I am facing similar situation. Have you got a solution. It will be great if you can share the way you resolved it.

Thanks

|||

Hi,

Thanks for your reply! What is the type of the global connection that you created and what would happen if your package is executed in a transaction? Do you take transactions into consideration?

Thanks!

/Dmytro

|||

Hi,

Unfortunately I haven't found a way how to solve this issue yet. If I find it, I would definitely post a solution here.

/Dmytro

|||

Dmytro Kryvko wrote:

I have a need to use a shared connection manager of type OLEDB inside a Script Component.
...
My assumption is that in case of OLEDB connection usage, the AcquireConnection method returns some OLE DB COM interface.

This is correct, the object is the OLEDB COM object, namely OLEDB session created by IDBCreateSession::CreateSession call. For using it, see OLEDB reference in MSDN.

Note that these interfaces are not meant to be used from .NET. If you really need to use it, you should create a custom component in C++, rather than using script component.

Connectiong to SQL Server 2000 over VPN

Hi, hoping someone can help me out here. I am opening enterprise manager and trying to register a new server for which I have permissions. When I use windows authentication I get "Login Failed for user "(null)" and when I use SQL Server Authentication I get "Login failed for user "sa".

I am VPN'd in to the companies network. I am not on their domain, I am on a domain at my current location. I think the problem is that I am not logged on to their domain therefore it can't see me as the user I am on that domain. Is there any way to trick this, or simply to get it to work?

Thanks in advance.Can you reach the server on the VPN (ping it) ?
if not, you need to reconfigurate your network settings(IP of the switch connectiong to the VPN)
if you can ping it, you should have no problem using SQL server Authentication (unless firewall filter the SQL Server port)

Originally posted by kevin86
Hi, hoping someone can help me out here. I am opening enterprise manager and trying to register a new server for which I have permissions. When I use windows authentication I get "Login Failed for user "(null)" and when I use SQL Server Authentication I get "Login failed for user "sa".

I am VPN'd in to the companies network. I am not on their domain, I am on a domain at my current location. I think the problem is that I am not logged on to their domain therefore it can't see me as the user I am on that domain. Is there any way to trick this, or simply to get it to work?

Thanks in advance.|||I can ping the server. I can also access shared folders on this server. When I use SQL Authentication I have tried using SA, our Admin account, and an account set up for me and they all say login failed for user.

How could I check to see if the firewall is blocking it? I don't think this is the problem but I guess it could be?|||I think you have to ask to the system admin for the firewall.

Do you asked someone on the domain (not using the VPN) to try login SQL server with the same users you tried ?

Originally posted by kevin86
I can ping the server. I can also access shared folders on this server. When I use SQL Authentication I have tried using SA, our Admin account, and an account set up for me and they all say login failed for user.

How could I check to see if the firewall is blocking it? I don't think this is the problem but I guess it could be?|||Someone on the domain was able to log in using the id's I tried.

I just spoke to our network admin and these ports are not blocked. Any other suggestions?|||Originally posted by kevin86
Someone on the domain was able to log in using the id's I tried.

I just spoke to our network admin and these ports are not blocked. Any other suggestions?

You cannot register as windows nt user (trusted) cos you might not be added to that server as a user, and as you are able to ping the server , you are suppose to register the server using sql login, the only reason i would say you are not able to register is the sa password is wrong, try overwriting the password froom any of the machines where its already connected and then register it ...you should be able to connect ...

Connectiong to MSDE 2000

I installed MSDE 2000 on my machine running XP home
edition.
I can connect with all client utilities, include, query
analiser, enterprise manager, odbc, etc if i use the
builtin/administrator id, but i cant connect in the SQL
MODE.
If i set up an odbc connection for test, i get the
following error
Attempting connection
[Microsoft][ODBC SQL Server Driver][SQL Server]Login
failed for user 'sa'. Reason: Not associated with a
trusted SQL Server connection.
The ODBC error returns a state 28000 error, with is an
authenticaton error, please how can i correct thisMSDE is installed by default with Windows authentication, not with mixed
authentication, so you can't login with a SQL login, like 'sa'. You can
change this from Enterprise Manager by rightclicking the server, choosing
properties, and change the Authentication on the Security tab. You ahve to
restart SQL Server for the setting to take effect.
Jacco Schalkwijk
SQL Server MVP
"Lanre" <larry548997@.yahoo.com_anonymous> wrote in message
news:1b8701c3fc16$8a0ec650$a401280a@.phx.gbl...
> I installed MSDE 2000 on my machine running XP home
> edition.
> I can connect with all client utilities, include, query
> analiser, enterprise manager, odbc, etc if i use the
> builtin/administrator id, but i cant connect in the SQL
> MODE.
> If i set up an odbc connection for test, i get the
> following error
> Attempting connection
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login
> failed for user 'sa'. Reason: Not associated with a
> trusted SQL Server connection.
> The ODBC error returns a state 28000 error, with is an
> authenticaton error, please how can i correct this|||If you don't have Enterprise Manager, you can change the setting with the
steps from this article:
285097 INF: How to Change the Default Login Authentication Mode to SQL While
http://support.microsoft.com/?id=285097
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.

Connection to the server is lost.

Hi
I have just installed SQL Server 2000 SP3 on 2000 server
.. I am attempting to connect to the Server through the
Analysis Manager, and I am getting an error of:
Cannot connect to the Analysis server on
computer 'computer name'
Connection to the server is lost.
I am able to connect if I use a administrator ID.
Using my ID I can connect using the Enterprise Manager to
the SQL server. On the server itself, I can't get into
Analysis Manager. Can anyone help?
My ID is listed inside the OLAP Administrators local group
on the server.
One more thing is after SP3 instllation, I have installed
and uninstalled EXCEL 2003. To get rid of one
error "version may not be valid" while connecting from
EXCEL To ANalysis Manager. Now this message has gone.
Thanks in advance for any help regarding this
Regards
Sajith
.Have you applied SP3 for SQL and Analysis Services on your client as well as
the server ?
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Sajith S" <sajith_sudhi@.hotmail.com> wrote in message
news:1229a01c3f5e1$94476720$a401280a@.phx
.gbl...
> Hi
> I have just installed SQL Server 2000 SP3 on 2000 server
> .. I am attempting to connect to the Server through the
> Analysis Manager, and I am getting an error of:
> Cannot connect to the Analysis server on
> computer 'computer name'
> Connection to the server is lost.
> I am able to connect if I use a administrator ID.
> Using my ID I can connect using the Enterprise Manager to
> the SQL server. On the server itself, I can't get into
> Analysis Manager. Can anyone help?
> My ID is listed inside the OLAP Administrators local group
> on the server.
> One more thing is after SP3 instllation, I have installed
> and uninstalled EXCEL 2003. To get rid of one
> error "version may not be valid" while connecting from
> EXCEL To ANalysis Manager. Now this message has gone.
> Thanks in advance for any help regarding this
> Regards
> Sajith
> .
>|||I did. But still the same error message.
So I have done the following workarounds
1. Uninstalled Analysis manager, Deleted the Olap
Administrators ID.
2. Installed Analysis Manager,Olap Administrator ID
created again by Analysis Manager. Applied SP3a.
Now everything found to be working...Thanks for the help.

>--Original Message--
>Have you applied SP3 for SQL and Analysis Services on
your client as well as
>the server ?
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
>"Sajith S" <sajith_sudhi@.hotmail.com> wrote in message
> news:1229a01c3f5e1$94476720$a401280a@.phx
.gbl...
to
group
installed
>
>.
>

Connection to Server

I have installed Microsoft SQL Server 2000. I am now
thoroughly confused. :-(
When I click on Start/Continue button (in the SQL Server
Service Manager window), I encounter the following error:
- The service did not start due to logon failure.
- An error 1069 - (The service did not start due to a
logon failure) occurred while performing this service
operation on the SQSQLServer service.
Did I miss a set up step?
I'm also confused as to where I set up new users.
I am running Microsoft XP.
Any help will be most appreciated.
Thanks
Carolinehas the account that runs your SQL Service recently changed it's password?
You can reset the password in ctrl panel/admin tools/services
Ray Higdon MCSE, MCDBA, CCNA
--
"Caroline" <clydec@.comcast.net> wrote in message
news:9b8401c4061f$a88cd050$a001280a@.phx.gbl...
> I have installed Microsoft SQL Server 2000. I am now
> thoroughly confused. :-(
> When I click on Start/Continue button (in the SQL Server
> Service Manager window), I encounter the following error:
> - The service did not start due to logon failure.
> - An error 1069 - (The service did not start due to a
> logon failure) occurred while performing this service
> operation on the SQSQLServer service.
> Did I miss a set up step?
> I'm also confused as to where I set up new users.
> I am running Microsoft XP.
> Any help will be most appreciated.
> Thanks
>
> Caroline
>|||I went to Services, but wasn't sure what I needed to do
there. No passwords have been changed since I bought my
laptop.
SQL Server is installed on my home laptop and it is only a
single instance use.
Any other suggestions?
Thanks
Caroline

>--Original Message--
>has the account that runs your SQL Service recently
changed it's password?
>You can reset the password in ctrl panel/admin
tools/services
>--
>Ray Higdon MCSE, MCDBA, CCNA
>--
>"Caroline" <clydec@.comcast.net> wrote in message
>news:9b8401c4061f$a88cd050$a001280a@.phx.gbl...
error:
>
>.
>|||In services go to MSSQLServer service. If it using a login, change it to use
local system and try to start the service, if it starts then you have an
account or password problem with the other account
Ray Higdon MCSE, MCDBA, CCNA
--
"Caroline" <clydec@.comcast.net> wrote in message
news:a8e501c406bc$0c14bb00$a101280a@.phx.gbl...
> I went to Services, but wasn't sure what I needed to do
> there. No passwords have been changed since I bought my
> laptop.
> SQL Server is installed on my home laptop and it is only a
> single instance use.
> Any other suggestions?
> Thanks
>
> Caroline
>
> changed it's password?
> tools/services
> error:

Connection to oracle / sqlserver / db2 databases

Hi All,

Is there a way in SSIS to change the database connection to sqlserver or oracle or db2 without choosing the connection manager in the source.

For e.g. I ran a package which is reading data from sqlserver and later i want to connect to oracle to read the data but without changing the connection manager in the source.

Basically, i want to find out from you gurus is about a way to switch between databases without changing the connection managers. OR the only way is to make different sets of packages for oracle / db2 and sqlserver sources ?

Thanks,

Vipul

Vipul123 wrote:

Hi All,

Is there a way in SSIS to change the database connection to sqlserver or oracle or db2 without choosing the connection manager in the source.

For e.g. I ran a package which is reading data from sqlserver and later i want to connect to oracle to read the data but without changing the connection manager in the source.

Basically, i want to find out from you gurus is about a way to switch between databases without changing the connection managers. OR the only way is to make different sets of packages for oracle / db2 and sqlserver sources ?

Thanks,

Vipul

You could use a configuration and change it in there. Judging by another post of yours you have already done this hence, could you lock this thread? If you don't have permission to lock the thread, let me know. I will be able to do it.

-Jamie

|||

Jamie,

Please lock the thread as i dont have the permisssion to do it.

Thanks,

Vipul

Connection string

hi. I have trying to load packages from SQL server using "load from SQL comman" and then programmatically changing the connection manager's certain properties(as this property has to be changed in run time.

It works fine when these packages are running from same database but when programmatically I am changing its initial catalogue to some other database, then this is not reflecting even after changing the initial catalogue. Its referring to database which these are created upon. If anyone has some idea please reply back

Is your catalog hardcoded somewhere in the package (like in a table name)?

I would suggest you open your package, try to change the connection string manually and then debug your package step by step.

HTH.

|||

thanks for your reply ,

Well yes the database name is getting added along with the table name.

is ther any way to place just table name or a way to remove the database name ?

Thanks,

|||

Could you give us more details? What component are you referring to? Is it OLE DB Source/Destination?

Most probably it can be fixed; just tell us what component has the catalog name hard-coded.

Thanks.

|||

Anshu nautiyal wrote:

thanks for your reply ,

Well yes the database name is getting added along with the table name.

is ther any way to place just table name or a way to remove the database name ?

Thanks,

That is your problem; make sure all sql statements in the package do not have the dabase name as they may be diffrent when you change the connection strings. Just edit the sql statements and remove the database part of the name.

|||

Anshu nautiyal wrote:

thanks for your reply ,

Well yes the database name is getting added along with the table name.

is ther any way to place just table name or a way to remove the database name ?

Thanks,

That is your problem; make sure all sql statements in the package do not have the dabase name as they may be diffrent when you change the connection strings. Just edit the sql statements and remove the database part of the name.

Connection still apperas in SQLServer Entreprise Manager over Locks / process ID

Hello,
i have a doubt here, after a close the connection, i still can see the last stored procedure active in the LOCKS/PROCESSID in enterprise manager of SQL SERVER.
I think i'm closing the connection well

Try

IfMe.ID > 0Then

Dim strSqlAsString = "SP_CHANGECLASSCONTENTS"

Dim sqlcommandAsNew SqlCommand(strSql,New SqlConnection(ConnStr))

sqlcommand.CommandType = CommandType.StoredProcedure

sqlcommand.Parameters.Add("@.PerformActivation", SqlDbType.Bit).Value = 0

sqlcommand.Parameters.Add("@.PerformInactivation", SqlDbType.Bit).Value = 0

sqlcommand.Parameters.Add("@.PerformDelete", SqlDbType.Bit).Value = 1

sqlcommand.Parameters.Add("@.PerformUndelete", SqlDbType.Bit).Value = 0

sqlcommand.Parameters.Add("@.PermanentDelete", SqlDbType.Bit).Value = CBit(PermanentDelete)

sqlcommand.Parameters.Add("@.Class_ID", SqlDbType.Int).Value = _id

sqlcommand.Connection.Open()

sqlcommand.ExecuteNonQuery()

sqlcommand.Connection.Close()

Else

Err.Raise(10205, "CLASS", "CLASS ID is empty")

EndIf

Catch exAs Exception

_err = ex.Message

Return Err.Number

EndTry

Hi,

.NET Framework SQl data provider utilizes database connection pooling (there's one pool per unique connection string). When you close a SqlConnection, it is returned to this pool (there are min amount of connections in the pool ) and the hard connection to the db is not necessarily closed (connection ).
E.g this way usage of connections is kept efficient and opening & closing of "real connections" is kept minimum.
Here's more details
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconconnectionpoolingforsqlservernetdataprovider.asp

|||ok tks,
but what if i use many procedures like this one several times, and each one creates it's own connection. Even if i close the connection well it still appears several processes concerning this procedures in SQLSERVER. does this degrades the performance ?
tks|||

Hi,
see the previous link for exact details.
Anyways, it happens within the limits of the connection pool. If there are free connections in the pool, they are utilized to fullfill those which you instantiate and run e.g even if you instantiate new connections in code, the pool might be able to deal with them without increasing its size (the actual pooled connections are of type SqlInternalConnection not those which SqlConnection objects which you instantiate).
If the pool cannot deal with new connection requests, it starts creating new ones (within the max limit of the pool). If max limit is reached then new connection requests are queued. Note also that after a burst usage of connections, they are also dropped from the pool to the mimum limit when lifetime has expired or connectiion is severed.

E.g the pools are there to keep connection count in control in situation like these.

Connection Prodlem-with instance node

Hi
I have an active/passive sql server 2000 cluster. Most of the time I remote-login into the server and use the enterprise manager to work. But now when I click on either of the node I get the following error:
Encryption not supported on SQL Server ConnectionOpen (PreLoginHandshake())
But I'm able to connect to the server from my desktop.
Any help in this regard?
Thanks,
This means that the "Enable Protocol Encryption" option was set on the
machine you're using as a client.
Use the SQL Client Network Utility to uncheck this.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Hi Kevin
Thank you so much it worked.
Razi
"Kevin McDonnell [MSFT]" wrote:

> This means that the "Enable Protocol Encryption" option was set on the
> machine you're using as a client.
> Use the SQL Client Network Utility to uncheck this.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>
|||You're welcome!
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Connection Prodlem-with instance node

Hi
I have an active/passive sql server 2000 cluster. Most of the time I remote-
login into the server and use the enterprise manager to work. But now when I
click on either of the node I get the following error:
Encryption not supported on SQL Server ConnectionOpen (PreLoginHandshake())
But I'm able to connect to the server from my desktop.
Any help in this regard?
Thanks,This means that the "Enable Protocol Encryption" option was set on the
machine you're using as a client.
Use the SQL Client Network Utility to uncheck this.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Hi Kevin
Thank you so much it worked.
Razi
"Kevin McDonnell [MSFT]" wrote:

> This means that the "Enable Protocol Encryption" option was set on the
> machine you're using as a client.
> Use the SQL Client Network Utility to uncheck this.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>|||You're welcome!
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.

Connection problem. Business Scorecard Manager 2005 and SSAS 2005.

Hello, I have a problem creating a ADOMD connection from BSM 2005 to SSAS 2005. (Choosing standard connection) It seems like it's connecting but I cant choose "database name", or it does'nt list any database names. No error messages. When I click Cube name I get the error stating: The business scorecard manager server could not connect to the database. Verify that all data has been entered in the boxes and the connection info is correct.

Any suggestions?

// Richard

I suspect this is security-related problem.

Try and see how BSM connecting to Analysis Server. Run SQL Profiler against Analysis Server and see what is the name of the user establishing connection and if this user has any rights to access databases. I suspect BSM establishing conection under Anonymous user.

Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi Edward,

I used the SQL Profiler and I can see that it is not me as the user who is trying to connect, so far so good but how can I change that. The NTUserName == Network Service.

Can you tell me how to change this?

Thank you,

Christian Lorenz

|||

I added NT AUTHORITY/Authenticated Users to cube reader-role and then it worked.

Connection problem to MSDE

Hi,
I installed MSDE in my server and I have tried to connect
to my server over the Internet using Query Analyser and
Enterprise Manager. Both fail during the connection.
Testing the connection to MSDE locally in the server shows
me I can connect using the server
name "dedbxx\machinename", but I can't connect using the
server IP address.
Why is this happening?
I have already ran c:\Program Files\Microsoft SQL Server\80
\Tools\Binn\SVRNETCN.exe to configure the Net Protocols
supported by my server instance, including TCP/IP, but
nothing happens using IP to connect to the server.
Also tried to configure a ODBC entry in the server using
the IP address, but it shows me this message:
Coonection Failed:
SQLState: '01000'
SQL Server Error: 14
Coonection Failed:
SQLState: '08001'
SQL Server Error: 14
[Microsoft][ODBC SQL Server Driver][DBNETLIB] Invalid
connection
And here is the server log:
2004-04-29 13:02:08.28 server Microsoft SQL Server 2000 -
8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.2 (Build 3790: )
2004-04-29 13:02:08.32 server Copyright (C) 1988-2002
Microsoft Corporation.
2004-04-29 13:02:08.32 server All rights reserved.
2004-04-29 13:02:08.32 server Server Process ID is 208.
2004-04-29 13:02:08.32 server Logging SQL Server messages
in file 'D:\MSSQLMSSQL$WKS\LOG\ERRORLOG'.
2004-04-29 13:02:08.43 server SQL Server is starting at
priority class 'normal'(1 CPU detected).
2004-04-29 13:02:10.37 server SQL Server configured for
thread mode processing.
2004-04-29 13:02:10.39 server Using dynamic lock
allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2004-04-29 13:02:10.60 spid3 Starting up database 'master'.
2004-04-29 13:02:11.17 server Using 'SSNETLIB.DLL'
version '8.0.766'.
2004-04-29 13:02:11.17 spid5 Starting up database 'model'.
2004-04-29 13:02:11.26 spid3 Server name is 'DEDBxx\WKS'.
2004-04-29 13:02:11.26 spid3 Skipping startup of clean
database id 4
2004-04-29 13:02:11.35 spid5 Clearing tempdb database.
2004-04-29 13:02:11.84 server SQL server listening on
65.110.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
65.110.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
65.110.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
65.110.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
216.197.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
216.197.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
216.197.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
216.197.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
216.197.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
216.197.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
216.197.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
216.197.xx.xx: 1433.
2004-04-29 13:02:11.84 server SQL server listening on
127.0.0.1: 1433.
2004-04-29 13:02:12.45 spid5 Starting up database 'tempdb'.
2004-04-29 13:02:12.68 spid3 Recovery complete.
2004-04-29 13:02:12.68 spid3 SQL global counter collection
task is created.
2004-04-29 13:02:27.15 server SQL server listening on TCP,
Shared Memory, Named Pipes.
2004-04-29 13:02:27.15 server SQL Server is ready for
client connections
Any ideas?
Thanks,
Do you mean over the internet using a VPN?
If so, is the VPN giving you full access to the remote network?
Is the ServerIP address the public IP address, or the LAN IP?
Cheers,
James Goodman
"Rogerio" <anonymous@.discussions.microsoft.com> wrote in message
news:620e01c42e13$8e873b20$a301280a@.phx.gbl...
> Hi,
> I installed MSDE in my server and I have tried to connect
> to my server over the Internet using Query Analyser and
> Enterprise Manager. Both fail during the connection.
> Testing the connection to MSDE locally in the server shows
> me I can connect using the server
> name "dedbxx\machinename", but I can't connect using the
> server IP address.
> Why is this happening?
> I have already ran c:\Program Files\Microsoft SQL Server\80
> \Tools\Binn\SVRNETCN.exe to configure the Net Protocols
> supported by my server instance, including TCP/IP, but
> nothing happens using IP to connect to the server.
> Also tried to configure a ODBC entry in the server using
> the IP address, but it shows me this message:
> Coonection Failed:
> SQLState: '01000'
> SQL Server Error: 14
> Coonection Failed:
> SQLState: '08001'
> SQL Server Error: 14
> [Microsoft][ODBC SQL Server Driver][DBNETLIB] Invalid
> connection
> And here is the server log:
> 2004-04-29 13:02:08.28 server Microsoft SQL Server 2000 -
> 8.00.760 (Intel X86)
> Dec 17 2002 14:22:05
> Copyright (c) 1988-2003 Microsoft Corporation
> Desktop Engine on Windows NT 5.2 (Build 3790: )
> 2004-04-29 13:02:08.32 server Copyright (C) 1988-2002
> Microsoft Corporation.
> 2004-04-29 13:02:08.32 server All rights reserved.
> 2004-04-29 13:02:08.32 server Server Process ID is 208.
> 2004-04-29 13:02:08.32 server Logging SQL Server messages
> in file 'D:\MSSQLMSSQL$WKS\LOG\ERRORLOG'.
> 2004-04-29 13:02:08.43 server SQL Server is starting at
> priority class 'normal'(1 CPU detected).
> 2004-04-29 13:02:10.37 server SQL Server configured for
> thread mode processing.
> 2004-04-29 13:02:10.39 server Using dynamic lock
> allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
> 2004-04-29 13:02:10.60 spid3 Starting up database 'master'.
> 2004-04-29 13:02:11.17 server Using 'SSNETLIB.DLL'
> version '8.0.766'.
> 2004-04-29 13:02:11.17 spid5 Starting up database 'model'.
> 2004-04-29 13:02:11.26 spid3 Server name is 'DEDBxx\WKS'.
> 2004-04-29 13:02:11.26 spid3 Skipping startup of clean
> database id 4
> 2004-04-29 13:02:11.35 spid5 Clearing tempdb database.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 65.110.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 65.110.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 65.110.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 65.110.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 216.197.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 216.197.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 216.197.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 216.197.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 216.197.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 216.197.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 216.197.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 216.197.xx.xx: 1433.
> 2004-04-29 13:02:11.84 server SQL server listening on
> 127.0.0.1: 1433.
> 2004-04-29 13:02:12.45 spid5 Starting up database 'tempdb'.
> 2004-04-29 13:02:12.68 spid3 Recovery complete.
> 2004-04-29 13:02:12.68 spid3 SQL global counter collection
> task is created.
> 2004-04-29 13:02:27.15 server SQL server listening on TCP,
> Shared Memory, Named Pipes.
> 2004-04-29 13:02:27.15 server SQL Server is ready for
> client connections
> Any ideas?
> Thanks,
>