cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Problem connecting to SQL Server 2000 personal edition

Former Member
0 Kudos
312

Hi

I am using MS SQL Server 2000 personal edition, it is running fine in my local machine and I am trying to connect it with the xMII 11.5 but I am not able to do it.

If any one faced similar problem pls help me out with a solution.

This is the error log:

An error occurred while creating a DB connection. com.lighthammer.Illuminator.logging.LHException: An error occurred while creating a DB connection. at com.lighthammer.Illuminator.connectors.IDBC.IDBC.processRequest(Unknown Source) at com.lighthammer.Illuminator.services.handlers.IlluminatorService.processRequest(Unknown Source) at com.lighthammer.Illuminator.services.ServiceManager.runQuery(Unknown Source) at com.lighthammer.Illuminator.servlet.Illuminator.service(Unknown Source) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at com.newatlanta.servletexec.SERequestDispatcher.forwardServlet(SERequestDispatcher.java:638) at com.newatlanta.servletexec.SERequestDispatcher.forward(SERequestDispatcher.java:236) at com.newatlanta.servletexec.SERequestDispatcher.internalForward(SERequestDispatcher.java:283) at com.newatlanta.servletexec.SEFilterChain.doFilter(SEFilterChain.java:96) at com.lighthammer.cms.system.CMSFilter.doFilter(Unknown Source) at com.newatlanta.servletexec.SEFilterChain.doFilter(SEFilterChain.java:60) at com.newatlanta.servletexec.ApplicationInfo.filterApplRequest(ApplicationInfo.java:2159) at com.newatlanta.servletexec.ApplicationInfo.processApplRequest(ApplicationInfo.java:1823) at com.newatlanta.servletexec.ServerHostInfo.processApplRequest(ServerHostInfo.java:937) at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:1091) at com.newatlanta.servletexec.ServletExec.ProcessRequest(ServletExec.java:973) at com.newatlanta.servletexec.ServletExecService.processServletRequest(ServletExecService.java:167) at com.newatlanta.servletexec.ServletExecService.Run(ServletExecService.java:204) at com.newatlanta.servletexec.HttpServerRequest.run(HttpServerRequest.java:487)

Thanks

Regards

Senthil

Message was edited by:

Senthil Boomi

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

I have not connected to the personal edition of SQL Server 2000. But, I found some information stating "The other issue with these operating systems is that they don't have services, so certain functions such as the SQL Agent can't run when you're not logged on". Because of this, I would first make sure that you are logged into the server. Second, can you connect to the SQL Server from another computer's Enterprise Manager? Perhaps the personal edition only allows connections to it from Enterprise Manager on the same machine, and no other connections.

Former Member
0 Kudos

Hi Ryan

I am to connect to the Enterprise manager through the user "sa", I am on wireless and I have installed the personal edition in my local machine hence I am not able to test this sql server from other machines.

Thanks for your help.

Regards

Senthil

Former Member
0 Kudos

Senthil ,

To test the sql server from other machines, do the following:

Make sure that the SQL Server allows remote access and supports connections using TCP/IP (mixed authentication or user/password authentication).

[1] See if sql server is listening on port 1433,

on machine [sql server], open a command prompt window and type " telnet localhost 1433", if telnet connects, sql server is working fine. Check if you see the result of netstat -ano, "0.0.0.0 1433...." on machine [sql server]. Check if you see the result of netstat -ano, "xxx.xxx.xxx.xxx 1433...." on machine [sql server IP]. Otherwise, sql server is not listening on 1433 correctly from localhost and/or outside PCs.You can also test with "osql -E -Stcp:localhost,1433 on machine [sql server].

[2] Then, try type " telnet [sql server's IN] 1433", from any other PC on the network. If telnet connects, sql server is working fine and the issue is with the XMII configuration or with MS-SQL Instance Name broadcasting over the network.

[3] If it doesn't, try type " telnet [sql server's IP] 1433", from any other PC on the network. If telnet connects, sql server is working fine and the issue is with the XMII configuration or you have active some kind of firewall (win XP SP2 installs it automatically) on that wireless network connection.

Try remove the firewall (if it's active) during testing, then redo STEP [3].

If telnet connects, go into XMII configuration and update the connection string

<b>ServerURL = jdbc:inetdae:[sql server IP/IN]:1433?database=pubs&sql7=true</b>

to reflect the telnet successful connection case.

Make sure the "PUBS" database exists in your Personal MS-SQL installation. If it doesn't, just modify <b>database=pubs</b> above, reflecting one accessible database.

Note:

[sql server] : LTIIB00815 << is this correct ?

[sql server's IN] : Sql Server Instance Name (LTIIB00815)

[sql server's IP] : Sql Server IP Address (xxx.xxx.xxx.xxx)

Former Member
0 Kudos

Thanks Paul

I am getting a error in the port 1433, I am not sure how to open the port. Can you pls help in this.

Regards

Senthil

Former Member
0 Kudos

You can allow remote applications to access the local instance of SQL Server by configuring the firewall to forward network requests that specify the network address of the instance of SQL Server.

Default instances of SQL Server use TCP port 1433 by default. Named instances, however, dynamically assign an unused TCP port number the first time the instance is started. The named instance can also dynamically change it's TCP port address on a subsequent startup if the original TCP port number is being used by another application. SQL Server only dynamically changes to an unused TCP port if the port it is currently listening on was dynamically selected. That is, if the port was statically selected (manually), SQL Server will display an error and continue to listen on other ports. It is unlikely another application would attempt to use 1433 since that port is registered as a well-known address for SQL Server.

Have the network administrator configure your firewall to forward the IP address and TCP port the instance of SQL Server is listening on (using either 1433 for a default instance, or the TCP port you configured a named instance to listen on). Also configure the firewall to forward requests for UDP port 1434 on the same IP address. SQL Server 2000 uses UDP port 1434 to establish communications links from applications.

You didn't specify which type of firewall are you using so I can not give you any detailed advice about opening the ports. For testing purposes you can temporary disable it.

Former Member
0 Kudos

I have found an article describing how to configure Windows Firewall to allow SQL Server connections:

http://searchwindowssecurity.techtarget.com/tip/0,289483,sid45_gci1213416,00.html

Hope it helps,

Cheers.

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Senthil ,

Can you tell me what parameter you have given for connection and there value.

Regards

Vinod

Former Member
0 Kudos

Hi

This is what I have given

In ServerPackage = com.lighthammer.Illuminator.connectors.IDBC

In ServerURL = jdbc:inetdae:LTIIB00815:1433?database=pubs&sql7=true

If you need any other details pls let me know.

Regards

Senthil