Difference Between Windows Locale In Remote Settings And SQL Server
Jul 20, 2005
Hello,
I just installed a SQL server and playing with it. I was reading up on
Collation and tried rebuilding the master database after changing to
Latin 1. After the master database was built, I looked at the regional
settings and realized that it was still English. When I tried to
change the settings again using rebuild database, I saw that my
selection was gone and replaced by the default setting. Iam a newbie
and any help is appreciated
Thanks!
Sunder
View 1 Replies
ADVERTISEMENT
Jun 15, 2007
Hi There
We currently have the following scenario:
4 app servers with regional date and time settings of locale A.
1 database server with locale settings B.
What is happening is that timestamps are being generated on the app servers, these are then in a sql command which fails on the database server since the timestamp format is invalid.
It was suggested that we change the regional locale settings of the database server, but will this not have serious implications , for example every current timestamp format in the datbase will become invalid?
In a nutshell is it safe to change a database servers regional date time locale settings ? Or are there serious implications?
Thanx
View 1 Replies
View Related
Dec 25, 2007
Hi all,
We have SQL Server 2005 Entp 32-bit on Windows Server 2003 Entp.Edtion 64-bit. ( Total memory = 16 Gb)
1) So, in this case , do i need to enable AWE Configuration from SQL Server Side ( 32-bit).
And what settings( AWE, /PAE) i should enable on OS (i.e.) on Windows Server 2003 (64-bit) in boot.ini file.
Because right now, i dont see any switches in boot.ini file.
2) And with 16 GB of RAM, what should be the ideal setting for memory ( Min & Max).
Please give some ideas on this.
Thanks.
View 5 Replies
View Related
Apr 16, 2008
Please help a teacher at wit's end.
I have created a site using Microsoft Expression Web. The site includes a create user page on which I placed the create user control (wizard), and a login page (which houses a login control) . When the site sits on my local host all works well and I render the pages on my browser locally: the first time a user is created the aspnetdb.mdf file is automatically created into my app_data folder, the new user information is saved and can be accessed on the login page etc. However, when I upload to my hosting server. (godaddy) I can navigate to each of these pages seamlessly but when I try to use the controls on either page I get similar errors:
Exception Details: 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
I am not a programmer, and am just beginning to learn asp.net. However, I need to solve this problem. GoDaddy cannot help me, they say, because this is inside of EW and that is a MS problem. They have on the several ocassions I have contacted them, suggested compatibility issues (since they use SQL server 2003 and 2008 not 2005, or suggest that I need to script something to ensure that the .mdf file is recognized by their server, or that it was a database problem and that I may need a database programmer. They did tell me that it is important to note that the databases are hosted outside their server. I have not found anything in the EW side of this equation since most forums and support etc, deal more with the design part, than the online publishing part. I have tried to find a programmer locally that could help me, and have yet to find one. I am so close to being able to publish a site that meets our small school's needs, but cannot jump this one hurdle. Can anyone tell me what I can do?
Any help will be appreciated.
View 6 Replies
View Related
Jan 22, 2008
When my default.aspx page loads I get this error for the connection to my SQL 2005 DB. 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 already gone to Surface Area Configuration to ensure that Remoting with both Named Pipes or TCP/IP is enabled and it's set to both for remoting.I verified that my local account has access to the DB.Not sure what else to check.
View 8 Replies
View Related
Jan 22, 2008
My site works fine in VWD2008 express, but I get this error when I try to use it on my live website.
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.
According to this article: http://support.microsoft.com/kb/914277 I am supposed to:
1.
Click Start, point to Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Surface Area Configuration.
Ok, there is no such program in this folder. The only thing in there is "SQL Server Error and Usage Reporting"...
The other thing I am greatly concerned with is this: All is want is for my webpages to be able to access my database for user authentication. I DO NOT want to grant the internet rights to remote connect to my database.
View 4 Replies
View Related
Dec 10, 2007
I get the following error and have been trying to figure out why I keep getting it. Initially, I had placed my project under wwwroot folder and ran it under IIS and it gave this error. Then I moved it to my local C drive and same thing. I am sharing this project with two other co-workers and all our config files and code files are same...they don't get this error but I do. I checked that SQL Server Client Network Utility has TCP/IP and the 'Named Pipes' enabled. I thought maybe I have setting in the Visual Studio 2005 that I'm not aware of that's causing this problem...it can't be the server since my co-workers aren't having this error and can't be anything in the code since all of us are sharing this project through vss. I dont' think using different version of .net framework can create this error. I changed the version from 2.0 to use 1.1x and it gave same error... Any help would be greatly appreciated. Thanks in advance.
Server Error in '/RBOdev' Application.
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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace:
[SqlException (0x80131904): 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)]
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +739123
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188
System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) +685966
System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) +109
System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +383
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +181
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +130
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28
System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424
System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate) +84
System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +197
System.Web.UI.WebControls.WebParts.SqlPersonalizationProvider.GetConnectionHolder() +16
System.Web.UI.WebControls.WebParts.SqlPersonalizationProvider.LoadPersonalizationBlobs(WebPartManager webPartManager, String path, String userName, Byte[]& sharedDataBlob, Byte[]& userDataBlob) +195
System.Web.UI.WebControls.WebParts.PersonalizationProvider.LoadPersonalizationState(WebPartManager webPartManager, Boolean ignoreCurrentUser) +95
System.Web.UI.WebControls.WebParts.WebPartPersonalization.Load() +105
System.Web.UI.WebControls.WebParts.WebPartManager.OnInit(EventArgs e) +497
System.Web.UI.Control.InitRecursive(Control namingContainer) +321
System.Web.UI.Control.InitRecursive(Control namingContainer) +198
System.Web.UI.Control.InitRecursive(Control namingContainer) +198
System.Web.UI.Control.InitRecursive(Control namingContainer) +198
System.Web.UI.Control.InitRecursive(Control namingContainer) +198
System.Web.UI.Control.InitRecursive(Control namingContainer) +198
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +692
Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832
View 3 Replies
View Related
Jan 24, 2008
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,
View 2 Replies
View Related
Apr 10, 2008
Hi,I have SQL Server Express Edition. I tried working out some ASP.NET Labs in my local system. Here is the link of the Virtual Lab which I tried. http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032286906&EventCategory=3&culture=en-US&CountryCode=USI recieve this error in my local system. 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 tried working out solutions from various websites. But the no solution is effective. Could anyone help me in solving this issue.
View 1 Replies
View Related
Oct 25, 2000
Hi Everybody,
Can anyone tell me what is the difference between Remote Server and Linked Servers.
thks in advance,
Srinivasan.
View 1 Replies
View Related
Jan 28, 2008
Hi I always get good reply from u all, thank you,
I have copied my asp.net website from one server to another. they administrator made necessary modification on IIS manager . and able to see the website on browser. but now i can't loging to system using old password.
I tryed to create new password then also it gives error
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)
Here I have used asp.net login control and membership class. Do I need to make nay changes in code.
I have already modified server name in connection string in web config file.
any one can say what is the problem and how to solve this.
thanks
Pat
View 1 Replies
View Related
Apr 18, 2008
Hi ,
I am struck with one issue.Plz help me out if you have any solution for this one.
Details
Front End - Visual Studio 2005
Back End -SQL Server 2000 (Remote database)
Error i am getting is
{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)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at dbcAccess.clsSQL.GetConnect() in C:Documents and SettingskerlsgMy DocumentsVisual Studio 2005ProjectsdbcAccessdbcAccessclsSQL.cs:line 296}
{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)
View 6 Replies
View Related
Jan 16, 2008
Is there a way to control some of the windows application log settings from within the logging process of a package. Specifically the 'source' parameter which comes out as 'SQLISPackage' which i'd like to be the actual name of the package which wrote to the log, and similarly 'Category' which comes out as 'none' and I'd prefer to assign something more meaniful ?
THX
View 1 Replies
View Related
Apr 10, 2008
Hi,I have SQL Server Express Edition. I tried working out some ASP.NET Labs in my local system. Here is the link of the Virtual Lab which I tried. http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032286906&EventCategory=3&culture=en-US&CountryCode=USI recieve this error in my local system. 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 tried working out solutions from various websites. But the no solution is effective. Could anyone help me in solving this issue.
View 3 Replies
View Related
Dec 6, 2007
Hi,
I am developing a windows application that needs to communicate with a remote SQL server 2005 database. Server allows remote connections and MSDTC service also running. Do I need to run MSDTC service on the client machine where I use desktop application ? any ideas ? It's throwing some error like
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.
But my SQL Server allows remote connection, and I am able to do a select statement.
But when I insert/update anything, it's throwing this error. I guess some problem with MSDCT. Anybody have any idea ?
View 1 Replies
View Related
Dec 25, 2007
Hi!!
I'moving my asp application to a new hosting server.
So when i tried the setup locally with the live DB & application in my test machine...
The DB access is denied when application tries to hit the DB.
DB is in seperate machine with SQL Server 2000 & application(ASP) is in Windows server 2003.....
Kindly help me with your suggestions....on what went wrong?
View 1 Replies
View Related
Jan 14, 2008
Hello Everyone,
I have a Report Server setup on my laptop (XP Pro SP2). I have developed a report which I would like to view from a Windows Forms Application (VB.NET) using a ReportViewer. When I try it from the local machine it works correctly, but if I try to connect and preview the same report from my other PC (Vista Home Premium) I am getting the "Unable to connect to the remote server. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because the connected host failed to respond." error.
I have setup the Processing mode to Remote and correctly setup the ReportPath and ReportServerUrl using:
With rptRetEmp
.ProcessingMode = Microsoft.Reporting.WinForms.ProcessingMode.Remote
.ServerReport.ReportServerUrl = New Uri("http://192.168.1.2/CPMReports")
.ServerReport.ReportPath = "/CPM_Reports/Test"
.ServerReport.Refresh()
.RefreshReport()
End With
Where CPMReports is the Report Server virtual directory and CPM_Reports is the folder where the report Test resides.
I do not know if this has anything to do with the fact that Vista Home does not have Report Services enabled or it is just a permissions problem. I have red several posts that describe similiar problems, but I could not find a solution.
Thank you for your help.
Daniel D.
View 1 Replies
View Related
Mar 28, 2008
I just want to find out what the difference between a remote login and a remote query is. I'd have thought that a remote query inherently requires a remote login.
View 6 Replies
View Related
Jan 5, 2001
I acciently change the locale id of my sql server using sp_configure. After i stop the server it now can not be re-started. Any help is appreciated.
View 1 Replies
View Related
Oct 8, 2007
Hi,
Just upgraded some development desktops to Vista Business. However we need
to still connect to some older remote windows 2000/SQL 2000 servers.
Trying to setup an ODBC system DSN on our Vista Business local desktop we get the
following errors -
-START ERROR WINDOW-
Connection Failed:
SQLState: '01000'
SQL Server Error: 772
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(SECDoClientHandshake()0.
Connection failed:
SQLState: '08001'
SQL Server Error: 18
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SSL Security Error
-END ERROR WINDOW-
Any help greatly appreciated as this is stopping us from making
database/table connections etc. We've checked the firewall setup and all is well there.
PS - we can still connect fine using XP or windows 2000 desktops and their
local DSNs.
View 8 Replies
View Related
Aug 18, 2007
I have SQL Server 2005 Developer Edition. And my operating system is Windows Vista.
I have written a procedure in C# and deployed it on SQL Server. However when i try to run it i get the following error.
System.Data.SqlClient.SqlException: The locale identifier (LCID) 16393 is not supported by SQL Server
Also I tried using same procedure in Windows XP machine and it workd fine. Can anyone help me what could be the problem?
View 12 Replies
View Related
Sep 20, 2006
Hi all,
I have a Windows Server 2003 with SQL Server 2005.
I´ve configured the following itens to allow remote connecitions:
[code]
WORKAROUND
Warning If you use Registry Editor incorrectly, you may cause
serious problems that may require
you to reinstall your operating system. Microsoft cannot
guarantee that you can solve problems that result from using
Registry Editor incorrectly. Use Registry Editor at your own
risk.To work around this problem, follow these steps on the
computer that Windows XP SP2 is installed on:
1. Make sure that the Log On As account for the MSDTC service
is the Network Service account. To do this, follow these steps:
a. Click Start, and then click Run.
b. In the Run dialog box, type Services.msc, and then click OK.
c. In the Services window, locate the Distributed Transaction
Coordinator service under Name in the right pane.
d. Under the Log On As column, see whether the Log On As
account is Network Service or Local System.
If the Log On As account is Network Service, go to step 2.
If the Log On As account is Local System, continue with these steps.
e. Click Start, and then click Run.
f. In the Run dialog box, type cmd, and then click OK.
g. At the command prompt, type Net stop msdtc to stop the MSDTC service.
h. At the command prompt, type Msdtc €“uninstall to remove MSDTC.
i. At the command prompt, type regedit to open Registry Editor.
j. In Registry Editor, locate, and then delete the following subkey:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSDTC
k. Close Registry Editor.
l. At the command prompt, type Msdtc €“install to install MSDTC.
m. At the command prompt, type Net start msdtc to start
the MSDTC service.
Note The Log On As account for the MSDTC service is set
to the Network Service account.
2. To allow the network transaction, you must enable
MSDTC. To do this, follow these steps:
a. Click Start, and then click Run.
b. In the Run dialog box, type dcomcnfg.exe, and then click OK.
c. In the Component Services window, expand Component
Services, expand Computers, and then expand My Computer.
d. Right-click My Computer, and then click Properties.
e. In the My Computer Properties dialog box, click
Security Configuration on the MSDTC tab.
f. In the Security Configuration dialog box, click to
select the Network DTC Access check box.
g. To allow the distributed transaction to run on this
computer from a remote computer, click to select the Allow Inbound check box.
h. To allow the distributed transaction to run on a
remote computer from this computer, click to select the Allow
Outbound check box.
i. Under the Transaction Manager Communication
group, click to select the No Authentication Required option.
j. In the Security Configuration dialog box, click OK.
k. In the My Computer Properties dialog box, click OK.
3. Configure Windows Firewall to include the MSDTC
program and to include port 135 as an exception. To do this,
follow these steps:
a. Click Start, and then click Run.
b. In the Run dialog box, type Firewall.cpl, and then click OK.
c. In Control Panel, double-click Windows Firewall.
d. In the Windows Firewall dialog box, click Add
Program on the Exceptions tab.
e. In the Add a Program dialog box, click Browse,
and then locate the Msdtc.exe file. By default, the
file is stored in the Installation drive:WindowsSystem32 folder.
f. In the Add a Program dialog box, click OK.
g. In the Windows Firewall dialog box, click to select
the msdtc option in the Programs and Services list.
h. Click Add Port on the Exceptions tab.
i. In the Add a Port dialog box, type 135 in the Port
number text box, and then click to select the TCP option.
j. In the Add a Port dialog box, type a name for the
exception in the Name text box, and then click OK.
k. In the Windows Firewall dialog box, select the name
that you used for the exception in step j in the
Programs and Services list, and then click OK.
[/code]
But, when the Windows firewal on the server is "On", remote connections
are not allowed, despite I´ve configured the Exceptions on the firewall.
Is there another task to solve this problem?
thanx!!!!
View 1 Replies
View Related
May 22, 2015
After 2 days of reading everything on the net about setting up Remote Access of my SQL 2012 Express using Windows Authentication I'm still not able to connect from a remote client onto my SQL Server Database Engine. I can get connected if using SQL Server Authentication. I have set all the parameters to allow access (read and tried everything from this site: URL.... but when I try using SSMS from the remote client to login I get Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. (Microsoft SQL Server, Error: 18452).I've disable the firewall (Even though I have put in rules to allow port 1433 and UDP port 1434). Nothing is allowing me to connect. I've have tried every solution listed and got nowhere. My network is very simple with only three computers connected via a Linksys router (Two running Windows 7 the test client is running Windows 8.1). I can shared files and folders between all. Each computer only has one user defined (default admin user).
I need to make this work as I have to document it for other end users who will be using an application I created that requires an SQL Database and it needs to be accessible by other users on their network.
View 2 Replies
View Related
Jun 17, 2007
I was able to do this on a Windows XP machine but I am not able to get this to work on a Windows 2003 Server machine.
I am connecting to the Windows 2003 Server and MS SQL Express via remote desktop on the lan.
This is what worked for me before:
EXEC sp_grantlogin '4800X2ASPNET'
USE MyDB
EXEC sp_grantdbaccess '4800X2ASPNET'
EXEC sp_addrolemember 'db_owner', '4800X2ASPNET'
But for some reason now I am getting this error:
Msg 15401, Level 11, State 1, Procedure sp_grantlogin, Line 49
Windows NT user or group '4800X2ASPNET' not found. Check the name again.
Msg 15401, Level 16, State 1, Line 1
Windows NT user or group '4800X2ASPNET' not found. Check the name again.
Msg 15410, Level 11, State 1, Procedure sp_addrolemember, Line 75
User or role '4800X2ASPNET' does not exist in this database.
I thought what I needed to add was the name of this pc that will connect remotely, but that doesn't seem to be working.
What weird is the old copy of this query I used had the local pc as the computer name. If I exchange the computer name from the remote pc name to the local 2003 Server machine name, the query works fine. Although that still doesn't let me add connections via Web Developer Express without error. It doesn't make sense to me anyhows, how could I have used the local machine's name and not the remote machine's name to get this to work previously. So confused.
Thank you in advance for help.
View 1 Replies
View Related
Jan 10, 2007
I have a windows based software application that connects remotely to a sql server 2005 and calls stored procedures. There is someone that I work with that is cautioning the company strongly that this is a bad thing to do in terms of security. Isn't this a very common thing to do? Assuming that the SQL Server installation is setup appropriately. Is this a bad practice?
View 4 Replies
View Related
Jun 17, 2007
I was able to do this on a Windows XP machine but I am not able to get this to work on a Windows 2003 Server machine.I am connecting to the Windows 2003 Server and MS SQL Express via remote desktop on the lan.This is what worked for me before:EXEC sp_grantlogin '4800X2ASPNET'USE MyDBEXEC sp_grantdbaccess '4800X2ASPNET'EXEC sp_addrolemember 'db_owner', '4800X2ASPNET'But for some reason now I am getting this error:Msg 15401, Level 11, State 1, Procedure sp_grantlogin, Line 49Windows NT user or group '4800X2ASPNET' not found. Check the name again.Msg 15401, Level 16, State 1, Line 1Windows NT user or group '4800X2ASPNET' not found. Check the name again.Msg 15410, Level 11, State 1, Procedure sp_addrolemember, Line 75User or role '4800X2ASPNET' does not exist in this database.I thought what I needed to add was the name of this pc that will connect remotely, but that doesn't seem to be working.What
weird is the old copy of this query I used had the local pc as the
computer name. If I exchange the computer name from the remote pc name
to the local 2003 Server machine name, the query works fine. Although
that still doesn't let me add connections via Web Developer Express
without error. It doesn't make sense to me anyhows, how could I have
used the local machine's name and not the remote machine's name to get
this to work previously. So confused.Thank you in advance for help.
View 1 Replies
View Related
Jun 17, 2007
I was able to do this on a Windows XP machine but I am not able to get this to work on a Windows 2003 Server machine.
I am connecting to the Windows 2003 Server and MS SQL Express via remote desktop on the lan.
This is what worked for me before:
EXEC sp_grantlogin '4800X2ASPNET'
USE MyDB
EXEC sp_grantdbaccess '4800X2ASPNET'
EXEC sp_addrolemember 'db_owner', '4800X2ASPNET'
But for some reason now I am getting this error:
Msg 15401, Level 11, State 1, Procedure sp_grantlogin, Line 49
Windows NT user or group '4800X2ASPNET' not found. Check the name again.
Msg 15401, Level 16, State 1, Line 1
Windows NT user or group '4800X2ASPNET' not found. Check the name again.
Msg 15410, Level 11, State 1, Procedure sp_addrolemember, Line 75
User or role '4800X2ASPNET' does not exist in this database.
I thought what I needed to add was the name of this pc that will connect remotely, but that doesn't seem to be working.
What weird is the old copy of this query I used had the local pc as the computer name. If I exchange the computer name from the remote pc name to the local 2003 Server machine name, the query works fine. Although that still doesn't let me add connections via Web Developer Express without error. It doesn't make sense to me anyhows, how could I have used the local machine's name and not the remote machine's name to get this to work previously. So confused.
Thank you in advance for help.
View 1 Replies
View Related
Mar 27, 2007
Hi,
I have the following scenario in my lab:
1. Windows Vista Ultimate with an fresh SQL 2005 Express SP2;
2. Developer machine with Windows XP and SQL Manag. Studio.
Problem:
Windows Vista isn't allowing a SQL connection from XP >> Vista.
I've tried:
1. Configured surface area (the same configurations works on XP);
2. Configured all services and windows firewall base on online docs from MS.
After 6 hours arround i didn't find any solution. Any ideas?
View 3 Replies
View Related
Dec 18, 2007
Hey all!
I've tried all I know in an effort to get SQL 2005 Express to allow remote connections on my customer's 2K3 server and I'm not having any luck. I've followed MSKB 914277, including adding the exceptions to their Windows firewall...even disabled the firewall altogether (for testing purposes), and I still can't get remote clients to connect. As suggested by various other posts, I used netstat -an to confirm that SQL is listening on port 1433 for the desired IP on the server.....and saw that it is listening. Here's a snippet:
TCP 192.168.0.2:1433 0.0.0.0:0 LISTENING
TCP 192.168.0.2:1433 192.168.0.2:1738 ESTABLISHED
TCP 192.168.0.2:1738 192.168.0.2:1433 ESTABLISHED
TCP 127.0.0.1:1433 0.0.0.0:0 LISTENING
I can connect to the database locally (i.e. on the 2K3 server itself) using just the IP address .... tried with a DSN, UDL, ODBC, and SSMSE...all of which have no problems (as shown by the two, "ESTABLISHED" entries in the netstat results above which were from running SSMSE locally on the server at the time of the netstat). But if a remote computer on the network tries to connect, they cannot connect. Sorry, I don't have a copy of the error message the clients are getting yet.
I asked The customer's IT to confirm that the clients CAN can "see" the server (i.e. that there wasn't some kind of router or firewall blocking their path) and they sent me a copy of the server's pfirewall.log file. Here is an entry from the file that seems to show that client requests ARE getting to the server:
2007-12-17 19:12:13 OPEN-INBOUND TCP 192.168.0.4 192.168.0.2 1213 1433 - - - - - - - - -
2007-12-17 19:12:13 CLOSE TCP 192.168.0.2 192.168.0.4 1433 1213 - - - - - - - - -
I'm starting to get in over my head here (I'm a programmer, not a DBA or Net Admin), but doesn't the above suggest that an incoming request came in from .4 on port 1213 and attempted to connect to .2 on port 1433, but the connection was denied or dropped by the server? If so, why? Is this related to another MS KB I read about connection pooling? I'm way over my head here and could use some help. Did I miss something subtle during configuration of SQL Express?
Thanks in advance.
View 2 Replies
View Related
Jun 10, 2007
Using Bulk Insert Task extensively in our solution. Everything was working great till we deployed it in stage columns. The database server is different from application servers. We have ASP.NET web services driving SSIS packages on application server. After struggling thru several security issues to get this working (ended up creating an application pool with a domain account) we are now stuck with this problem. On a different note still don't understand what specific security permission is available to domain account that makes it work.
Read in some blog that SQL Server 2005 SP2 Beta had this (Bulk Insert) fixed but not in final production version. Is there a specific reason why this is so?
SSIS and the API is quite easy to work with but associated security and deployment issues are not always clear. A lot of answers seem to be coming from end users - thanks a lot to all for sharing your experiences - sadly not presented clearly in SSIS documentation.
View 2 Replies
View Related
Dec 13, 2007
SQL Database in my application with windows authentication rejects accessing after deploying and remote access
1- My web applications databese access is windows authentication
2- In developing area there is no problem for accessing database
3- After deploying to another server there is problem accessing database:
Cannot open user default database. Login failed.Login failed for user 'BRCK231ASPNET'.
How can I solve this problem?
Thanks.
View 1 Replies
View Related
Mar 23, 2015
We log ship our production database tansaction logs to a secondary database on a separate remote domain.
Incidentally, this was not set up via the "Ship Transaction Logs" wizard, but instead we had to use the various system stored procedures after restoring a copy of the database on the remote domain in standby mode.
We now have an issue where users are unable to access the remote secondary database without having sysadmin privileges. Clearly we want to avoid this!
We want to be able to use Windows Authentication mode on the server of the secondary database. But since the two domains differ, is it possible to even achieve this?
How can we set up read-only access for users on the secondary database without giving them sysadmin privileges?
View 3 Replies
View Related
Jan 25, 2005
Hi,
You might just be able to save me downloading and installing SQL Server French...
I'm having localization problems with some .NET code - and I might be able to solve the problem if I know how SQL is parsed in different locales. Say my table MyTable contains a float column FloatColumn. In English, I would say
SELECT * FROM MyTable WHERE FloatColumn = 2.3
If my locale was, say for argument's sake, French, would I have to write
SELECT * FROM MyTable WHERE FloatColumn = 2,3
???
Thanks for your help,
T
View 1 Replies
View Related
