I have 3 NT Workstations that will not connect to my SMS database using NT Integrated Security. The SQL 6.5 server is set up to use mixed security. The only way to connect to the server is to use a standard sql account. Any ideas? THis happens to all users even administrators.
I've inherited a SQL 6.5 server running on Windows NT 4.0. An application was written (I believe in VB 6.0) to access tables on the server. From the documentation that I have received, I believe that the Security mode for this server is supposed to be "Standard". When I first got my hands on the server, the security mode was set to "Integrated". I have since changed it "Standard" but the users still get the same error:
Connection failed: SQL State" '08004' SQL Server Error: 18450 [Microsoft][ODBC SQL Server Driver][SQL Server] Login failed. User: MCLEANC Reason: Not Defined as a valid user of a trusted SQL Server connection.
I looked in the Microsoft Knowledgebase and read an article on SQL Server Error 18450 (http://support.microsoft.com/default.aspx?scid=kb;en-us;Q164167). I followed all of their suggestions but the server still seems to be stuck in "Integrated" mode.
I am trying to verify that the ability to use the security extension to use Forms based authentication is available (or not) with SQL 2005 Standard. I have read a few books and articles that state that only the Enterprise edition will allow us to use the security extensions to customize authentication and authorization. But a few recently have told me otherwise.
Does anyone know for sure? We use Standard edition...and would like to customize our security.
I have an app that queries the same SQL Server, instance and database. In one execution of the app, it makes multiple queries against the database in two different runs, each run being approx. 10 seconds apart. The app app does remote logins to the SQL Server using Standard Security. Each run makes twenty (20) connection attempts and all connection attempts between the two runs are using the same SQL account/password€¦(when successful) there is a .5 second delay between each attempt. So, here is a visual description:
The problem I€™m seeing is: All connection attempts in Run 1 are successful in connecting to the SQL Server. All connection attempts in Run 2 are UNSUCCESFFUL when connecting to SQL Server (error message is €œSQL Server cannot be found or Access Denied€?). Remember, ALL connection attempts are using the same SQL account and password.
As an added note: When I switched from using SQL Standard Security to Windows Security, ALL connection attempts in each Run was successful.
Does see anything wrong with this? Is Standard SQL Security limited in the number of simultaneous connections or in some other kind of way?
We have experienced an issue with back backup / restore of a database originating from SQL Server 2000 to SQL Server 2003.
We have the following setup:
SQL Server 2000
- DatabaseA
- asdfUser (SQL User)
- asdfUser is (dbowner) of DatabaseA
- DatabaseB
- asdfUser (SQL User)
- asdfUser is (dbowner) of DatabaseB
SQL Server 2005 Standard
-asdfUser is NOT Setup as a user yet.
-We restore DatabaseA and DatabaseB to the SQL Server 2005 Standard. The databases are restored with the security permissions of asdfUser being the DB Owner of DatabaseA and DatabaseB.
-We create a new SQL user named asdfUser on the SQL Server 2005 box. We then try to add the UserMapping of DBOWNER for the DatabaseA and DatabaseB. We receive an error message stating that the asdfUser already have permissions to the databases. We proceed with the user creation without those permissions.
-We proceed to the login properties of the asdfuser and view their UserMappings. The asdfUser does not have access to DatabaseA or DatabaseB. We then add the UserMapping of DBOWNER to both DatabaseA and DatabaseB. We Try to select OK and we receive an error message that states that the user already has those permissions.
-When we query the UserID's of the asdfUser that is in the database and the UserID of the asdfUser that is created, they are two different values.
We have several SQL servers in our network. When we try to connect to any of these servers with SQL profiler, the connection is always made with the same server, irrespective of the servername we use. There is no default server name used in the setting of SQL profiler application.
Hi, I want to receive a mail when a specific user connects. How can this be done best? Raise an alert? How? Btw, the 'Login auditing' is set to 'Failed logins only'. Suggestions are very welcome! Cheers, E
Hi~! i use my computer to create a project for my UMPC(with Tablet PC system). i want to use SQL server compact 3.1 and VB2005 to finish the work.. i need to upload some data from UMPC to SERVER. How can i do? The UMPC can not connect to PC by ActiveSync. so how can i move the data?
I am facing a SQL 2005 SSIS problem. I have an SSIS package that downloads some data from an AS400 and places the data into a SQL 2005 table. I use Client Access ODBC connection as my Source. When I run the package from Business Intelligence - Visual Studio, it works fine. However when I schedule the SSIS package as a job, it falls over with the following error:
Description: System.Data.Odbc.OdbcException: ERROR [08S01] [IBM][iSeries Access ODBC Driver]Communication link failure. comm rc=11004 - CWBCO1011 - Remote port could not be resolved
Please can someone help me......
Ric
By the way this is the full error message below:
Error: 2007-08-08 14:00:47.85 Code: 0xC0047062 Source: Data Flow Task DataReader Source [893] Description: System.Data.Odbc.OdbcException: ERROR [08S01] [IBM][iSeries Access ODBC Driver]Communication link failure. comm rc=11004 - CWBCO1011 - Remote port could not be resolved at System.Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCode retcode) at System.Data.Odbc.OdbcConnectionHandle..ctor(OdbcConnection connection, OdbcConnectionString constr, OdbcEnvironmentHandle environmentHandle) at System.Data.Odbc.OdbcConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject) at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.Odbc.OdbcConnection.Open() at Microsoft.SqlServer.Dts.Runtime.ManagedHelper.GetManagedConnection(String assemblyQualifiedName, String connStr, Object transaction) at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSConnectionManager90.AcquireConnection(Object pTransaction) at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.AcquireConnections(Object transaction) at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostAcquireConnections(IDTSManagedComponentWrapper90 wrapper, Object transaction) End Error Error: 2007-08-08 14:00:47.87 Code: 0xC0047017 Source: Data Flow Task DTS.Pipeline Description: component "DataReader Source" (893) failed validation and returned error code 0x80131937. End Error
I have a package that I want to run as a scheduled job in sql server 2005. The job runs fine in the studio. I am convinced that it is not a password or security issue as I set the protectionlevel to do not save sensitive data and can still run the job in the studio. The User running the job has SA privileges as does the SQL Server Agent. The job reads a flat file, runs it through a script and than inserts the rows into a table. The job runs successfully only if the flat file is empty. The job history says: The return value was unknown. The process exit code was -1073741795. The step failed.
Hi, By using ssis script can I make connection with MS Aceess Database.I want to establish the conection with data base and i want to manipulate the record via script code. Can any one help me for writing the script.
I've got a page that uses an SqlDataSource to populate a simple DataList of inventory. It has been working just fine until yesterday. All of the sudden when I run the page from Visual Studio, it fails to connect to the database with an SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) If I choose to configure the SqlDataSource in the designer, I select the stored procedure and on the last page of the wizard click the Test button and it brings back the results correctly. It turns out, all of the pages in this project are unable to connect at runtime. It's like there's a runtime firewall...
Hi all, Now, I using Windows200o & SQL7.0. I want to permission a client connect to my server, and with his login, he only works with a specify datatbase. When he connects to my server, although he can't work other databases, but he can list of them in server - using EM (and I don't want he knows this). How can I solve this problem? Thanks.
Hi, I want to receive a mail when a specific user connects. How can this be done best? Raise an alert? How? Btw, the 'Login auditing' is set to 'Failed logins only'. Suggestions are very welcome! Cheers, E
I would like to ask how can I create a subscription for a report that connects to Analysis Services?
I was able to create a subscription but the report's datasource is SQL Server 2005 using the built-in "sa" credential. But when I am connected to SSAS the option to use the SQL login is greyed out.
Note: but even the connection string "serverBserverA,2040" also connects to Instance "serverB", when i try to connect from SSMS, In SSMS it shows the wrong instance name like, "serverBserverB", but it actually connects to  Instance "serverA"
i.what is the reason behind this? ii.Is there any way to avoid this connection, by performing server property changes, if any ?
We've been running a mirrored database (using certificates since we don't have a domain) and it's all working well. Last week we decided to add a witness for automatic failovers, but for some reason I just can not get the witness to connect to the Partner2 server.
See screenshot here
Please help me troubleshoot this - I re-created the endpoints / users / certificates but it's still not working. Where can I get more information on what exactly the problem is? Can I test the endpoints somehow?
I am connecting to a MsAccess-database using ODBC. While developing the package we have changed mappings for this database. The ODBC was changed accordingly and the old definitions were deleted. However SSIS is still using the old ODBC-links even when deleting all existing connections and adding a new connection. Somehow the old settings have been saved and are being reused in the DataReader Source. If so where are they saved and how can I change/delete them ???? Note: I suspect the Server Explorer because every time I add a data connection using the ODBC, the Datareader Source starts using the wrong definition (even when Server Explorer uses the correct one).
I recently installed VB6.0 Enterprise on my system. As a part of the installation is the option to install SQL Server 6.5 Development. I elected to install SQL. The install went without any glitches. Upon going into SQL Enterprise Manager, I was asked to register the server where SQL was running. My understanding was that SQL would allow me to register the name of my host system. (This is a stand alone system with VB6.0 and Sql development 6.5 installed - no network attached). SQL will not allow me to register my server's name as the host server. It says that if cannot connect to the named server. SQLSERVER and SQL EXEC services appear to be running without any problems. Anyone have any idea where I should start or what could be disallowing my connection/registeration of my server. Any help would be greatly appreciated..... Thanks... Tom
Developers wanting to access sql server developer edition on XP workstation in small office network (workgroup) will have problems using windows authentication (trusted connection) if the XP "server" machine has "simple file sharing" enabled.
Simple file sharing in XP can be disabled in control panel - folder options.
For this sneak mode to work accounts with the same user and password should exist on both "client" and "server".
Hi all!Is there any function in SQL that I can use to get current date fromworkstation? All functions which I tried (now(), getdate() etc.)returns current date from server but I need date from workstation.Regards,Mirnes Lemes
I would like to know if one can adminiter SQL server remotely using MMC on NT workstation? If so, how do you install the MMC and SQL Enterprise Manager Add-in on NT workstation?
How can I configure my workstation running WIN95 to used the SQL Enterprise Manager from the server end and other utilities. I have installed the client network utility.
Reason to use enterprise manager because I wanted to perform administrative tasks on my workstation and I've installed SQL SERVER 7.0(Standard version with 5 clients)on the WINNT 4.0 server.
Hi all;I am trying to replicate our database by using the merge replication.[color=blue]>From server side I tried to connect to the workstation. I have[/color]installed MSDE to the client machine. I can see the machine name on theSQL Server Group however I wasnt able to create the conncetion betweenthe machines. I have checked my network connection, there is no problemI can see the machine and I can connect it through the network. I triedto use Client Network Utility with Named Pipes and TCP/IP but not agood news. I couldnt achieve to connect to the machine. So couldsomeone please help me out with this problem. I am really in trouble Ihave to find out this end of this week.RegardsAs
I've got VS 2008 Pro installed, as well as SQL Sever 200 (which I must keep installed). When I run the install for SQL Server 2005 developer edition, it continually fails to install
I had a perfectly good working copy of SQL Server 2005 installed. However, at some point I needed the Report Services Designer so I could edit my reports in Visual Studio. I inserted the CD and selected the feature from the list and it installed. Only problem being that it has completely removed my Management Studio and practically every other tool I didnt explicitly checked when installing the RS Designer.
When I tried to run the same Setup again and check everything, it tells me that there is no change between what I have selected and what is installed, which sounds like total bs to me, since my pc doesnt have a management studio etc anymore.
Out of pure misery I decided to remove my entire SQL Server installation, inc Instance, hoping to start anew and achieve the result I wanted with the least amount of frustration. I ended up here and followed it all the way: http://support.microsoft.com/kb/909967
When I started reinstalling, I ran into something new. The installer refuses to let me install anything but the Workstation components, books online and development tools. All the other options are greyed out and not even available.
Someone please help me get my SQL Server back up and running because I'm getting hopeless.
It appears that there is no way to install SQL Server 2005 Workstation Components on an x86 operating system (XP in this case) if you have the x64 install disks (Standard Edition). Can someone verify this?
I am finding it hard to believe that workstation components for a standard Windows client environment are not distributed with the version of SQL Server that matches Windows 2003 x64.