I recently migrated our database from Access to SQL Server 2005. All the WinXP users can connect to the new SQL2005 database. But all the Win2K machines fail to log on. To diagnose the problem, I tried to connect from a Wind2K machine using an .udl file. The connection failed because "a provider failed to initialize".
The SQL2005 server is residing on a WinXP machine. Users log on via SQL Server authentication layer using a dedicated login that only has read/write privileges to one specific database.
I have had this issue just pop up. I have local users who can connect fine, but my users that require connection by VPN cannot connect. I get the server not available or access denied error. I did confirm that the VPN'ers are connected to the network correctly and can see that their shares and mappings are correct. Any ideas? Thanking you all in advance!!
HiI'm new this .I' using SQL 2005 VWD05.Could some body tell me how to upload to my host server database to to run a membership user account.I dont know what are the procedure to do on my pc in order to transfer the file on the database.Thanks
Today I have task to move all UDB's including matser,msdb form Windows 2000 server to Windows 2003 Advacned Server with 64bit(8 Hours Down time)
Present Plan
1.Install same Version of SQL Server in Destination Server 2.Take all Databases Backup 2.Move DTS,JOB and Scripts with same location 3.Stop both servers SQL Server's 4.Deattch all Databses and Move to Destination Server 5.Place all Databases(Same Loaction i.e Soruce Server master DB is C:<folders>.. Place in Destination Server C:<folder>..) 6.Start the Databse Servers(Destination) 7.Port the Apllication and Test.
Note:for our project we are using windows users,so that no problem with Orphan users.
Please some body Advice me, or suggest me ..it is ok
Sql server type: database engine server name: authentication: sql server authentication login: sa password: xxxxx
I remember the server name being sqlexpress (I think that was the default name during the install).
OR are they asking for my computer name? because I tried that also and it gave me an error saying "the default installation doesn't allow remote connections"
Excuse the cross post (to VBexpress fourum) but maybe someone here will have a different take?
have searched all around can't seem to see how to configure a SQL2005 developer ed so I can use vb express to develop a local front end. keep getting "the user instance login flag is not supported on this version of sql server" I have configured the .net framework via aspnet_regsql.exe. Also I configured the "Machine.config" file. but so far no luck.
Selecting sql2005 as the server thru the add new database connection in advanced area yields the error message
surely there is away.
So far still no joy,
While Scotty indicates that the connection to SQL2005 is intentionally hampered other posters indicate that the user instance problem can be solved by running the .net config tool to add the asp database to sql server, which I have done.
However this does not yet work.
I cannot get the code to spark yet.
Again my configuration cannot be any simpler. sql express sp1 and sqldeveloper on the same machine using windows security (all installed with default cofigurations)
In the absence of other ideas I may try to get sql express downloaded and going, I'm not sure what issues that will present re: what I'm trying to develop.
I'm trying to develop the skills to replace some fairly involved reporting and some user table interface that I had going in access2003, I hate to pruchace a big piece of sw when I don't know if it will remove the current roadblocks...
Appreciate the help here, but doesn't someone have a "simpler" complete answer? I.e. one that would get the developer database to accept the connection wizard? (user instance issue)
I am trying to remotely connect to a SQL 2005 Instance on a cluster. I see the following error:
No retry on exception System.Data.SqlClient.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)
I have enabled TCP/IP , Named Pipes on the node. I have turned off IPSec on the clients as well. I am using the following connection string : "Integrated Security=SSPI;server=servernameinstancename;Pooling=false;database=TrialDB"
I have an interesting problem. I am running xp pro and when I try to connect to an instance of SQL2005 running on WIN2003 using SQL Sevrer Management Studio, I get the following error:
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: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (.Net SqlClient Data Provider)
This instance is protected by a vpn and is running on a clustered environment. I can connect to other SQL2000 servers that are running on a clustered environment and SQL2005 that is not clustered.
After adding a host file entry, I was able to connect to the server using OSQL. I was able to telnet into the port the server is listening on.
Others in my group can connect to the server using SQL Server Management Studio with no problems. They are running Win2003 Server. I originally could connect to this server, but I needed to change my password. After that I lost my remote connectivity. I can RDP into the server and map drives to the server. I map to a local administrator of this machine.
i'll try to explain the problem with my bad english, so sorry.
In my firm i have a server (W2003 Server) with IIS 6.0 and SQL Server 2005 EE an it is joined in the main domain as all users and their workstation (window XP) are joined too.
The main role for this server is to be a web server and with IIS Manager I configured to verify user identities with Windows Integrated authentication without any anonymous access to web pages (ASP scripts).
I made a group called "Web Users" with read right on ASP scripts and his only one member is "Domain Users".
"Web Users" has of course rights to access this server from network.
This group is also a SQL Server login because it has rights to wiew an modify data at least in one db table trought ASP pages using ADO, but the problem is that they can also connect using ODBC.
Configuring SQL to accept only local connection i can avoid this, but as SQL Admin i can't connect too. So how is possible for web users interact with SQL only trought web pages ? Thank you very much
Hello our organization has never had any problems getting users to connect to our SQL servers but we have grown a lot over the past year or two. Does SQL Server actually block connections if they go over the license limit? I don't have access to the servers to see the model used but I have been asked to look into this. I couldn't find any information on this so I decided to ask you guys. Thanks in advance.
We are running SQL Server 2005 in a Windows 2003 domain and I have a situation where some of my users are unable to connect to the SQL Server unless they are a member of the sysadmin group. Any attempts by these users to login result in a login failed,
Error: 18456, Severity: 14, State: 11
Which indicates that it is a valid user who does not have access to this SQL Server.
I have been able to narrow the failures down to the following situation:
Create a user, TestUser1, as a member of 1 domain local group TestGroup1
Give TestGroup1 access to SQL (standard public access to master)
All good. Login succeeds.
Add TestUser1 to another domain local group TestGroup2
Attempt to login to SQL Server -> login failed.
Add the user explicitly -> login failed
Add one of the groups to sysadmin -> login succeeds
It seems that as long as the user is a member of more than one AD group, and none of those groups is a member of the sysadmin server role then the user is unable to login. Obviously having all of the users as sysadmin isn't a workable solution, has anyone seen this issue before?
I have been able to replicate a similar situation in our test domain, but in that case the issue is resolved by adding the users explicitly to SQL Server (still not an ideal solution).
Interestingly, if I run the same test in our test domain but use global groups, it works. But unfortunately the network admin tells me the groups must stay as local.
We replicate a SQL2000 database (DataBaseA) to a SQL2000 database (DataBaseB) by using the Restore function and hasn't change its logical name but only the physical data path and file name. It is running fine for a year. We use the same way to migrate the DataBaseB to a new SQL2005 server with the Restore function and the daily operation is running perfect. However, when we do the Backup of DatabaseB in the SQL2005, it just prompt the error message
System.Data.SqlClient.SqlError: The backup of full-text catalog 'DataBaseA' is not permitted because it is not online. Check errorlog file for the reason that full-text catalog became offline and bring it online. Or BACKUP can be performed by using the FILEGROUP or FILE clauses to restrict the selection to include only online data. (Microsoft.SqlServer.Smo)
Please note we left the DataBaseA in the old SQL2000 server.
Please help on how we can delete the Full-text catalog from DatabaseB so we can do a backup
Can't connect to local server instance MSSQLSERVER in SQL Server Management Studio (SQL2005 sp2/Vista).
SQL Server Configuration Manager reports SQL Server2005 services: SQL Server (MSSQLSERVER) Running. This would indicate the name of the SQL server is "MSSQLSERVER" correct? I chose "default" instance during the install and that is the name it gave itself.
I tried connecting to the server using the following for the Server Name: MSSQLSERVER and .MSSQLSERVER neither works.
The only thing that works for my installation is just plain "." (no quotes) and nothing else. Can this be correct because I can't find any reference to this. Thanks.
I have a medical records system, SoapWare v4.90, that uses MSDE (SQL2000) databases. Due to the 2gb limitation, I am trying to migrate over to SQL 2005 (Standard or Express) which I have heard works fine. The SoapWare has a datamanager that allows me to log in to the MSDE instance, detach the SoapWare databases from msde (as well as do backups, etc) which I can confirm are detached.
Then I log back into a SQL2005 database instance using the datamanager and try to attach the database. This is what their pictured instructions demonstrate. However, I get the following error:
Database 'sw_charts' cannot be upgraded because it is read-only or has read-only files. Make the database or files writeable, and rerun recovery.
Of course, some of the entries will be read only, since doctors have to sign off the charts and are not allowed to subsequently change them. But I should still be able to switch over to sql 2005?!?!?!?
Or... is there a way to attach the databases to SQLExpress manually?
Starting with Win2k you are not suppossed to have to install MDAC, as it comes with the OS. What about when I install SQL7 and it automatically installs MDAC. Do I have to reinstall MDAC in this case?
I have a medical records system, SoapWare v4.90, that uses MSDE (SQL2000) databases. Due to the 2gb limitation, I am trying to migrate over to SQL 2005 (Standard or Express) which the company says works fine. The SoapWare has a datamanager that allows me to log in to the MSDE instance, detach the SoapWare databases from msde (as well as do backups, etc) which I can confirm are detached.
Then I log back into a SQL2005 database instance using the datamanager and try to attach the database. This is what their pictured instructions demonstrate. However, I get an error:
Database 'sw_charts' cannot be upgraded because it is read-only or has read-only files. Make the database or files writeable, and rerun recovery.
Or... is there a way to attach the databases to SQLExpress manually?
In a development server you take a backup and you want to move the entire database to a production server. The production server does not contain the database, users, or logins in master.
When you restore the backup to production in 7.0, the users get moved to DBO because the logins do not exist and then you cannot delete them.
We are having to drop the users from the database on development, back up the database and restore it to production, then recreate the users on production.
This is bogus and did not happen in 6.5 because of the aliases.
Does anyone know the 'trick' in getting sqlmail (sqlserver 7.0) to work with Outlook 2000 on a windows 2000 server machine. I've setup a mail profile on Outlook, but it is not listed in the dropdown menu in the sqlmail properties. Outlook communicates with my smtp/pop3 mail server - no problem. I can't get sqlmail to interface with outlook. Basically it is telling me that it cannot find ANY profiles on the server.
My shop is thinking of migrating from NT4 to Win2K. Is anyone running SQL7 on Windows 2000 (which edition?)? How's you're experience been? Anyone hear any anecdotes of particular things that don't work (well)?
I am new to MSDE and want to deploy it in my company (because it is free).However, when I install it in a W2K professional machine, there is a messagebox saying that a "strong SA password is required". How can I solve theproblem?Arthur Cheung(The MSDE engine was downloaded from the microsoft sql server web page)
Hi,I am new to Win2k and SQL server and need to back up everything each night.I used the supplied NT backup utility to schedule a backup but this missedsome files that were open or in use.I am more used to Unix/Informix where I could backup everything whether itwas in use or not.How or what would you recommend I use to do my backups?Thanks.
Hiya! I'm having a problem installing SQL Server 7 Enterprise Edition (no service pack)on a Windows 2000 Server SP 2 machine (256 MB RAM,40 GB drive) off an original MSDN CD. Only the client components get installed. This is the output from the SQLStp.log file: 15:19:51 Begin Setup 15:19:51 7.00.623 15:19:51 Mode=Normal 15:19:51 ModeType=NORMAL 15:19:51 ValueFTS returned: 1 15:19:51 ValuePID returned: 1 15:19:51 ValueLic returned: 1 15:19:51 GetDefinitionEx returned: 0, Extended: 0xf000000 15:19:51 System: Windows NT Server 15:19:51 SQL Server ProductType: Enterprise Edition [0x3] 15:19:51 Begin Action: SetupInitialize 15:19:51 End Action SetupInitialize 15:19:52 Fixed install: 0 15:19:52 Begin Action: CheckRequirements 15:19:52 Platform ID: 0xf0000000 15:19:52 Version: 5.0.2195 15:19:52 Processor Architecture: x86 (Pentium) 15:19:52 File Version - C:NTSRVRSystem32shdocvw.dll: 5.0.3315.2879 15:19:52 ComputerName: SERVER-5IQ8359Z 15:19:52 User Name: Administrator 15:19:52 IsAllAccessAllowed returned: 1 15:19:52 C:NTSRVRTEMP\_ISTMP44.DIRscm.exe -Silent 1 -Action 6 -Timeout 5000 -Service MSSQLServer 15:19:57 Process Exit Code: (0) 15:19:57 OS Language: 0x409 15:19:57 End Action CheckRequirements 15:19:57 Begin Action: Detection 15:19:57 End Action Detection 15:19:57 Begin Action: ODBCLocked 15:19:57 End Action ODBCLocked 15:19:57 This combination of Package and Operating System allows a client install only. 15:19:59 The Enterprise Edition server component cannot be installed on Windows NT Server using this CD. Only client components will be available for installation.
15:19:59 Reading SoftwareMicrosoftWindowsCurrentVersionCommonFilesD ir ... 15:19:59 CommonFilesDir=C:Program FilesCommon Files 15:19:59 Windows Directory=C:NTSRVR15:19:59 Begin Action: ShowDialogs 15:19:59 Begin Action: DialogShowSdWelcome 15:20:00 End Action DialogShowSdWelcome 15:20:00 Begin Action: DialogShowSdLicense 15:20:01 End Action DialogShowSdLicense 15:20:01 Begin Action: DialogShowSdRegisterUserEx 15:20:06 End Action DialogShowSdRegisterUserEx 15:20:06 Begin Action: DialogShowCdKey 15:20:06 End Action DialogShowCdKey 15:20:06 Begin Action: DialogShowPID 15:20:06 End Action DialogShowPID 15:20:06 Begin Action: DialogShowSdSetupType 15:20:10 [SetupTypeSQL] 15:20:10 szDir=C:MSSQL7 15:20:10 Result=303 15:20:10 szDataDir=C:MSSQL7 15:20:10 End Action DialogShowSdSetupType 15:20:10 Begin Action: DialogShowSdComponentMult 15:20:10 basesys=0, baseinst=0,basedata=0 15:20:19 SQL program folder: C:MSSQL7 15:20:19 SQL data folder: C:MSSQL7 15:20:19 Windows system folder: C:NTSRVRSystem3215:20:19 Prog req: 46703, Data req: 0, Sys req: 24971 15:20:19 Prog avail: 2147483, Data avail: 2147483, Sys avail: 2147483 15:20:19 Prog req vs. avail, 71674, 2147483 15:20:19 Data req vs. avail, 0, 2147483 15:20:19 Sys req vs. avail, 24971, 2147483 15:20:19 DisplaySystemPreReq 15:20:19 [SQLComponentMult] 15:20:19 Component= 15:20:19 Result=1 15:20:19 End Action DialogShowSdComponentMult 15:20:19 Begin Action: DialogShowSdStartCopy 15:20:38 End Action DialogShowSdStartCopy 15:20:38 Begin Action: DlgCPLLicense 15:20:38 End Action DlgCPLLicense 15:20:38 End Action ShowDialogs 15:20:38 Begin Action ProcessBeforeDataMove: 15:20:38 DeinstallStart returned (C:MSSQL7): -1 15:20:38 DeinstallStart returned (C:MSSQL7): 0 15:20:38 End Action ProcessBeforeDataMove: 15:20:38 Begin Action ProcessComponentSelection: 15:20:38 End Action ProcessComponentSelection 15:20:38 Begin Action LogSelectedComponents: 15:20:38 MgtTool 15:20:38 MgtToolSEM 15:20:38 MgtToolSEMHTML 15:20:38 MgtToolSEMMSD98 15:20:38 MgtToolSEMMSD98SYS 15:20:38 MgtToolSEMMSD98Res 15:20:38 MgtToolSEMMSD98Hlp 15:20:38 MgtToolSEMHelp 15:20:38 MgtToolSEMSEMSys 15:20:38 MgtToolSEMRes1033 15:20:38 MgtToolSEMResIntl 15:20:38 MgtToolSEMMSD98RsI 15:20:38 MgtToolProfiler 15:20:38 MgtToolProfilerHelp 15:20:38 MgtToolProfilerRes1033 15:20:38 MgtToolProfilerResIntl 15:20:38 MgtToolQryanlz 15:20:38 MgtToolQryanlzHelp 15:20:38 MgtToolQryanlzRes1033 15:20:38 MgtToolQryanlzResIntl 15:20:38 MgtToolDTCCLi 15:20:38 MgtToolWzcnflct 15:20:38 MgtToolWzcnflctWzcnsys 15:20:38 MgtToolWzcnflctWzcnHlp 15:20:38 MgtToolUtilSys 15:20:38 MgtToolUtilBinn 15:20:38 Connect 15:20:38 ConnectConnSys 15:20:38 ConnectConn9x 15:20:38 ConnectConnNT 15:20:38 Books 15:20:38 BooksBookso 15:20:38 DevTools 15:20:38 DevToolsHeaders and Libraries 15:20:38 DevToolsHeaders and LibrariesInclude 15:20:38 DevToolsHeaders and LibrariesLibx86 15:20:38 DevToolsHeaders and LibrariesLibAlpha 15:20:38 DevToolsHeaders and LibrariesESQLC 15:20:38 DevToolsMDAC SDK 15:20:38 DevToolsVDI 15:20:38 DevToolsVDIInc 15:20:38 DevToolsVDISamples 15:20:38 DevToolsDbg Int 15:20:38 DevToolsDbg IntDbg Int Common 15:20:38 DevToolsDbg IntEXE 15:20:38 Samples 15:20:38 SamplesADO 15:20:38 SamplesDBLIB 15:20:38 SamplesDTS 15:20:38 SamplesESQLC 15:20:38 SamplesMSDTC 15:20:38 SamplesODBC 15:20:38 SamplesODS 15:20:38 SamplesOLEAut 15:20:38 SamplesRepl 15:20:38 SamplesSQLDMO 15:20:38 SamplesSQLNS 15:20:38 Core 15:20:38 CoreSys 15:20:38 ODBC 15:20:38 OLEDB 15:20:38 Repostry 15:20:38 RepstSys 15:20:38 CoreMisc 15:20:38 Monarch 15:20:38 Jet 15:20:38 NetCore 15:20:38 NetExt 15:20:38 SFExt 15:20:38 ReplExt 15:20:38 Core1033 15:20:38 CoreIntl 15:20:38 CrMi1033 15:20:38 CrMiIntl 15:20:38 Monr1033 15:20:38 MonrIntl 15:20:38 SFEx1033 15:20:38 SFExIntl 15:20:38 RpEx1033 15:20:38 RpExIntl 15:20:38 SysCore 15:20:38 VOLEDB 15:20:38 VODBC 15:20:38 MiscCore 15:20:38 MCHlp 15:20:38 MC1033 15:20:38 MCIntl 15:20:38 CnctBinn 15:20:38 CrRepCom 15:20:38 {E07FDDC8-5A21-11d2-9DAD-00C04F79D434} 15:20:38 {E07FDDBF-5A21-11d2-9DAD-00C04F79D434} 15:20:38 End Action LogSelectedComponents 15:20:38 Begin Action MoveFileData: 15:21:11 End Action MoveFileData 15:21:11 Begin Action ProcessAfterDataMove: 15:21:11 DeinstallSetReference (C:MSSQL7sqlservr.exe) returned: 0 15:21:11 End Action ProcessAfterDataMove 15:21:11 Begin Action InstallPkgs: 15:21:11 Setup is installing Microsoft Management Console (MMC) ... 15:21:11 D:x86Otherinstmmc.exe /Q 15:21:35 Process Exit Code: (0) 15:21:35 Setup is installing HTML Help ... 15:21:36 HTML Help installer exit code: 0 15:21:36 End Action InstallPkgs 15:21:36 Path successfully updated. 15:21:36 %SystemRoot%system32;%SystemRoot%;%SystemRoot%syst em32WBEM;C:Program FilesSymantecpcAnywhere;C:MSSQL7BINN 15:21:36 Begin Action SelfRegister 15:23:39 Return code: 0 15:23:39 End Action SelfRegister 15:23:39 Begin Action SetupRegistry: 15:23:39 End Action SetupRegistry 15:23:39 Begin Action PostSetupRegistry: 15:23:39 C:MSSQL7BINNdcomscm.exe /RegServer 15:23:39 Process Exit Code: (0) 15:23:39 C:PROGRA~1COMMON~1MICROS~1SQLDEB~1sqldbreg.exe -RegServer 15:23:39 Process Exit Code: (-2147312566) Error loading type library/DLL.
There are have 2 nodes.Both on cluster and on a test_domain.Test domain is a active directory domain.
Node_A & node_B has C and D drives.D drive will have programs.
There is one common drive E - where data will go.
Now,I have to install SQL2000 on it.Can anyone tell me in layman's way how to install it.Do I have to have D drive in shared mode?When I give remote connection what should I give here?
Win 2000 clustered was installed by a NT expert and is working fine.
I am assuming drive_D will hold the SQl programs.
I tried one article posted here from Sqlserver preformance side but nothing worked.
Does it matter as both the nodes are on a Active Directory?
