Subject:Still can not get "integrated security" login to work for SQL Server Author:William Findlater Date:28 Sep 2007 03:54 PM
Upgraded to Stylus Studio 2007 XML Enterprise Suite build M, but
still can not get "integrated security" login to work for SQL Server
2005 sqlexpress, which was supposted to be fixed in build k.
"eis2\sqlexpress,1433" works for other applications eg Access, or Excel, but does not work for Stylus.
tryed:
"eis2\sqlexpress,1433;AuthenticationMethod=Type2" with space for username, blank for password.
also tryed "eis2\sqlexpress;AuthenticationMethod=Type2", and
"eis2\sqlexpress:1433;AuthenticationMethod=Type2"
Subject:Still can not get Author:William Findlater Date:01 Oct 2007 01:13 PM
No, I am not running SQL Server on my local XP box. It is on a Windows 2003 server. As a matter of fact I installed the Enterprise on the Server and it made the connection using integrated security. The problem is making the connection from my XP box.
Have a number of other applications, and commercial programs (like Excel) that make the connection from my XP box.
Have you tested it on a remote SQL server with integrated security?
Subject:Still can not get Author:William Findlater Date:01 Oct 2007 02:51 PM
The firewall may have something to do with the problem. For my other apps I have to specify the port number (1433). So the connection string I am currently trying with Stylus is:
I am able to ping:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\0061882>ping eis2
Pinging eis2.ful.us.ray.com [147.19.99.17] with 32 bytes of data:
Reply from 147.19.99.17: bytes=32 time<1ms TTL=125
Reply from 147.19.99.17: bytes=32 time<1ms TTL=125
Reply from 147.19.99.17: bytes=32 time<1ms TTL=125
Reply from 147.19.99.17: bytes=32 time<1ms TTL=125
Ping statistics for 147.19.99.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Documents and Settings\0061882>
Is the SQL Server you test on a 2003 Windows server? It starts out with all security choices at least risk in contrast to Windows 2000 server.
Subject:Still can not get Author:Ivan Pedruzzi Date:01 Oct 2007 04:15 PM
To indicate the port number you have to use ":" not ",".
In any case 1433 is the default therefore can be omitted.
You don't need AuthenticationType=2 because the driver will default to that when the user is not provided.
Please use the following in the server URL and leave user and password empty: eis2\sqlexpress:1433
Just to be use we are on the same page could you post a screenshot of the Stylus Studio connection dialog with the above data?
You mention before that you have installed Stylus Studio on the same machine where SQL Server is running and you have been able to connect.
Which server URL did you use there?
Subject:Still can not get Author:William Findlater Date:02 Oct 2007 12:32 PM
The "Windows Firewall" is not running on the 2003 Server. This version introduced the
Security Configuration Wizard
Security Configuration Wizard (SCW) is an attack surface reduction tool for members of the Microsoft® Windows® Server 2003 family with Service Pack 1 (SP1). SCW determines the minimum functionality required for a server's role or roles, and disables functionality that is not required.
For more technical guidance about SCW, see "Security Configuration Wizard for Windows Server 2003" at the Microsoft Windows Server 2003 Web site. (http://go.microsoft.com/fwlink/?LinkID=42434)
SCW does the following:
Disables unneeded services.
Blocks unused ports.
Allows further address or security restrictions for ports that are left open.
Prohibits unnecessary IIS web extensions, if applicable.
Reduces protocol exposure to server message block (SMB), LanMan, and Lightweight Directory Access Protocol (LDAP).
Defines a high signal-to-noise audit policy.
Subject:Still can not get Author:William Findlater Date:02 Oct 2007 06:56 PM
Sorry, but I can not turn off my winxp firewall. That option is turned off by the company I work for. We know that there is a ping connection, and that other DB apps work.
What does Stylus Studio require to make a connection?
Have you tested it on a Windows 2003 or later server?
Subject:Still can not get Author:Minollo I. Date:02 Oct 2007 08:44 PM
As Ivan already replied, yes, we do test against Windows Server 2003; as a matter of fact, our QA and development servers run Windows Server 2003, and we use them to test database connections quite frequently against a variety of servers.
Stylus (as any other JDBC client) needs to reach the server through TCP/IP on port 1433; evidence seems to suggest that currently Stylus Studio is unable to establish that connection; and the simplest explanation would seem that Stylus Studio is blocked in its attempts by a firewall.
I would suggest that you try asking IT in your company to make sure that on your machine Stylus Studio is excluded from the firewall limitations.
Subject:Still can not get Author:Ivan Pedruzzi Date:02 Oct 2007 09:58 PM
Unfortunately having other applications be able to connect doesn't prove a lot.
For example most of Microsoft applications use by default the named pipe protocol.
Another interesting test would be to disable all protocols except TCP-IP then re-start SQL Server and see if you are still be able to connect using those apps.