Could someone please tell me what I have to set at the Server side so that I will be able to STOP and START the SQL Server using Enterprise Manager and `sa` login remotely, say from the workstation.
Thank you in advance for your help
Asfen
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".
At least it worked for me!
I have the following connection string in my Windows app that works fine on the Server:
workstation id=SCSXP;packet size=4096;integrated security=SSPI;data source=scsxp;persist security info=False;initial catalog=nala
But when I use that string on a workstation, it times out. I do have a Network connection to the Server.
How should I modify the connection string to work on the workstation?
Thanks,
Bill
I am running SQL 7 (SP3) on a 2000 Server. When I configure the server as part of the Workgroup I have no problems connecting from the workstation. However, if I join the server to our 2000 domain, I cannot connect and/or register the server from the workstation through EM.
Is this a security issue? If so, what are the minimum requirements or what else am I missing. Any suggestions would be appreciated.
Thank you,
Eugene Jenkins
This might not be a SQL Server question, might be something else. Ihave a workstation on a LAN that can't connect to the SQL Server. WhenI try to configure a User DSN to connect to it, the server name I wantappears TWICE in the list of possible servers. No matter which one Iselect, it can't get the connection.The workstation also can't connect through EM or QA.We've checked the user's permissions, we've re-installed some serverpacks, re-installed the Client Tools, we've even hunted through theregistry, everything looks OK, but we still can't connect. This is theonly machine on the LAN that can't connect. Everybody else connectsfine.I'm stumped. Any ideas? Anybody ever seen the server name appeartwice like that?-Emily
View 2 Replies View RelatedDear folks,
I€™ve moved my server folder which contains about 10 dtsx and its ADO .net connection as well as OLEDB into my folder workstation. Then, when I€™m gonna to open them appears this error:
Error 1 Error loading M_HAC_Modelo198_CECA.dtsx: Failed to decrypt protected XML node "DTS:Password" with error 0x8009000B "Clave no válida para utilizar en el estado especificado.". You may not be authorized to access this information. This error occurs when there is a cryptographic error. Verify that the correct key is available. c:ssishacienda_anualM_HAC_Modelo198_CECA.dtsx 1 1
Translate into english: "Clave no válida para utilizar en el estado especificado" = Invalid key for to use in the specified state (more or less)
What really happen? Well, I wrote these packages using a domain user (belong to Administrators group in Active Directory) via Terminal Server and now I want to modify them by mean my domain user (I already have got installed sql25k client tools and the stuff required)
I thouht that these connections were saved in the same folder where dtsx, dtsproj, etc..
Solution? Create them again? I hope that it will be a piece of cake otherwise...
Thanks in advance for any though or advice,
I set up the collector, and specify the Run As as my AD account in the Collector Set - Properties - General screen. My AD account is the local admin of the remote server.
However, the collector does not seem to work. Although the collecting set is shown as running, the The blg file stays at 64K. If I open it, there is nothing inside (no counter at the bottom). What did I miss?
Greetings,
I thought I had applied sp2 successfully but I discovered when I tried to apply the hotfix ( sqlserver2005-kb933097-x86-enu.exe), that the SQL Server Tools and Workstation Components wasn't at the 3042 level.
The recommendation in the log file is to:
"Update 3152 is dependent on prerequisite update 3042. Exit setup and refer to the Knowledge Base article to find the prerequisite patch."
Does anyone know where I find the prerequisite patch?
Any help would be appreciated.
Regards Noel
Time: 03/13/2007 18:05:39.045
KB Number: KB933097
Machine: NOEL_EVO
OS Version: Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 2
Package Version: 3152
Command-line parameters specified:
Cluster Installation: No
**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed
**********************************************************************************
Products Detected Language Level Patch Level Platform Edition
SQL Server Database Services 2005 (SQL2005) ENU SP1 2005.090.3042.00 x86 DEVELOPER
SQL Server Analysis Services 2005 (SQL2005) ENU SP1 2005.090.3042.00 x86 DEVELOPER
SQL Server Reporting Services 2005 (SQL2005) ENU SP1 9.00.3042.00 x86 DEVELOPER
SQL Server Notification Services 2005 ENU SP1 9.00.3042.00 x86 DEVELOPER
SQL Server Integration Services 2005 ENU SP1 9.00.3042.00 x86 DEVELOPER
SQL Server Tools and Workstation Components 2005 ENU SP1 9.1.2153 x86 DEVELOPER
**********************************************************************************
Products Disqualified & Reason
Product Reason
SQL Server Tools and Workstation Components 2005 The product instance SQL Tools does not have prerequisite update 3042 installed. Update 3152 is dependent on prerequisite update 3042. Exit setup and refer to the Knowledge Base article to find the prerequisite patch. Install the prerequisite and rerun the installation.
I have need to configure Microsoft SQL Server 2014 express on my development machine. I have never worked with Microsoft SQL Server and could use some direction. I have done MYSQL work before but the seems much different.
View 3 Replies View RelatedHi,
I created a CLR UDF that returns a large number of rows, when I run it from my VPC (XP, SQL Server Developer Edition and 1GB Memory) it takes approx 2 min and 30 secs to start displaying the rows (Using Management Studio), when I run the same query in our development server (Win 2003, SQL Server Enterprise Edition, 8 GB Memory and 8 Processors) it takes more than 15 min to start displaying the results, does anybody have an idea why is this happening?
Thanks in advance
Everytime I do an install of SQL Server 2005 and I don't select to install all components (even if I make sure Workstation components and all sub components are selected) SQL Management Studio never loads. The setup completes without error however there is no SQL Management Studio anywhere on the system. I know I have searched hard for it. Has anyone else had this problem? Am I missing something?
Thanks.
We currently built a new SQL2005 server and have serveral sentitive Payroll database hosted in it. I managed to seperate some roles to various users to prohibit them to direct access the data but can access it via front-end application.
The problem is I setup a backup operator with the following rights
Server Roles -- Public
User Mapping
User Mapped to this login / Database membership for
PayrollDataBase_1 BackupOperatorName
db_backupoperator / db_denydatareader / db_denydatawriter / public
However, I try to login using the 'BackupOperatorName' in my workstation and Backup the PayllrollDataBase_1 to a server shared path says E:SqlDataBacupPayrollDataBase_1.BAK. Afterward, I copy it over the network back to my workstation and RESTORE in back to my local SQL2005 instant using the local SQL2005 SA user. All data CAN BE browse
Anyone please help to post how to restrict the Backup operator can only Backup the database but cannot restore to its local SQL2005 instant
Many Thanks in advance
Hello,
I have installed successfully Microsoft SQL server 2005 in MSCS.
However the set up did not install Workstation components (client tools - SSMS etc).
I have successfully installed workstation components in one node of cluster.
However setup is giving following error while installing workstation components on other node. (From this node MS SQL server 2005 was installed).
Product: Microsoft SQL Server 2005 Tools -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A, location: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, command: /setup
There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.
I did "C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, /setup".
It executed but no error, no output.
Any gues, help in isolating issue?
Any more information required.(Media is ok. Setup has been tried after reboot. There is enough disk space.)
Regards.
Mahesh
===========
Setup
1) Microsoft Cluster of two nodes.
2) Hardare - HP Blade servers
3) OS - Windows 2003 EE with SP2
4) SQL Server 2005 Standard Edition with SP2.
=============================
MSI (s) (B0:7C) [17:40:20:390]: Note: 1: 1722 2: SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A 3: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe 4: /setup
MSI (s) (B0:7C) [17:47:23:609]: Product: Microsoft SQL Server 2005 Tools -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A, location: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, command: /setup
MSI (s) (B0:7C) [17:47:35:921]: Note: 1: 1729
MSI (s) (B0:7C) [17:47:35:921]: Product: Microsoft SQL Server 2005 Tools -- Configuration failed.
MSI (s) (B0:7C) [17:47:35:953]: Cleaning up uninstalled install packages, if any exist
MSI (s) (B0:7C) [17:47:35:953]: MainEngineThread is returning 1603
MSI (s) (B0:A0) [17:47:36:062]: Destroying RemoteAPI object.
MSI (s) (B0:80) [17:47:36:062]: Custom Action Manager thread ending.
Hi all,
Have just tried my sql server 2005 connected asp classic website on II7 for the first time and have gotten some errors.
First off I have unchecked show friendly errors in IE and have enabled ASP to send error messages to the browser.
My error I get is when I execute a basic .asp page:
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "mydatabasename" requested by the login. The login failed.
/index.asp, line 10 which is dbConnect.Open cstring
from this peice of code:
sub dbOpen()
set dbConnect = Server.CreateObject("ADODB.Connection")
cstring = "DSN=mysqldsn; Trusted Connection=yes"
dbConnect.Open cstring
end sub
I have gone into ODBC and have setup both a user dsn and file dsn that equals mysqldsn and points to my database (I know you only need to set up one DSN but I'm not sure which)
I also notice under mywebsite home panel there is a connection string option. Do I do anything with that?
Definatley a lot more to it than XP's II6!
Any help or advice would be greatly appreciated.
Oracle and Teradata are able to capture the windows/client login that connects to their database with a functionnal ID.I've searched around and I don't think MS SQL can do this...I administer SQL 2014 server and also SAS Enterprise guide product. I've created sql server logins for several teams so everyone shares the same sql server login which is used to bind the SAS library to my SQL server database.
However, when looking at activity monitor, I can't drill down to which user is executing a particular query. I only see the SQL login which is share amongs 200 other folks.On the other hand, when they connect from SAS to Oracle or Teradata, I can see the shared login + additionally their windows NT login used to connect to SAS which is awesome....they can't fool me by using a shared/funcionnal ID....i still see who's using that ID...
I use EM to handle 2 SQL servers. One I can `stop`; the other I can`t. (except I think I used to be able to do so).
When I select the `stop` I get the following message from EM:
"An error 1051 - (A stop control has bee sent to a service which other running services are dependent on) occurred while performing the service operation on the MSSQLServer service."
How do I track down what this other running service is? How do I stop SQL?
All help greatly appreciated.
Judith
Hi,
I have a script component. What it does, it queries the a table using a connectionstring assigned to it in the Connection Managers Editor (which is an ado.net adapter). this works fine when i'm using a windows login in the ado.net connection manager. But when i changed my connection to use SQL server login, I encounter this error:
OnError,,,Add new records to Dim_T_Status (Case),,,10/14/2007 5:54:47 PM,10/14/2007 5:54:47 PM,-1073450910,0x,System.Data.SqlClient.SqlException: Login failed for user 'CS_REPORT'.
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.HandleUserException(Exception e)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ProcessInput(Int32 inputID, PipelineBuffer buffer)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper90 wrapper, Int32 inputID, IDTSBuffer90 pDTSBuffer, IntPtr bufferWirePacket)
OnError,,,LOAD AND UPDATE OCEAN Dimension Tables,,,10/14/2007 5:54:47 PM,10/14/2007 5:54:47 PM,-1073450910,0x,System.Data.SqlClient.SqlException: Login failed for user 'CS_REPORT'.
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.HandleUserException(Exception e)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ProcessInput(Int32 inputID, PipelineBuffer buffer)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper90 wrapper, Int32 inputID, IDTSBuffer90 pDTSBuffer, IntPtr bufferWirePacket)
OnError,,,LoadOCEANDimensions,,,10/14/2007 5:54:47 PM,10/14/2007 5:54:47 PM,-1073450910,0x,System.Data.SqlClient.SqlException: Login failed for user 'CS_REPORT'.
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.HandleUserException(Exception e)
at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.ProcessInput(Int32 inputID, PipelineBuffer buffer)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostProcessInput(IDTSManagedComponentWrapper90 wrapper, Int32 inputID, IDTSBuffer90 pDTSBuffer, IntPtr bufferWirePacket)
How to go about this?
cherriesh
All the logins with sysadmin role are locked out in one of the SQL server. Also in that instance Logon trigger is implemented which allows only certain users with Windows Authentication to logon.
This server is converted into single user mode by using command prompt. Now we are attempting to connect to SQLServer using command sqlcmd -S FTCPU3239 (since we do not have any other login) and create a new login with sysadmin role but are refused due to logon trigger. it says Login failed for login 'DomainNameUserName' due to trigger execution.
I have a server that has 20 databases . I have tested with few users with different level of access and all of them were able to connect to the server and also see, select, update , delete from a particular database which is kind of weird because they do not have a user login associated or mapped to that database. I checked and no user is part of any group in AD that would give them permission to connect . I need a query that would find the permission path of a user. I already queried with xp_logininfo but I am not getting any thing.
View 9 Replies View Related I'm having some problems debugging SQL Server stored procedures on a SQL Server 2005 server. I have installed Visual Studio 2005 on a workstation running Windows XP, now I'm trying to debug a ASP.Net web application that has some code that executes the stored procedures on a Windows 2003 Server running SQL Server 2005.
I opened VS2005 ... created a connection to the SQL Server 2005 instance ... open the Stored procedure ... right click the stored procedure name and selected Step into Stored Procedure and the following message is displayed:
Unable to start T-SQL debugging.Could not attach to SQL Server process on 'ServerName'.
Any ideas.
Thanks,
I have a weird problem. I started my laptop this morning and was unable to start my SQL Server. Every time I try to start it I get the below error:
A connection could not be established to (local)
Reason: SQL Server does not exist or access denied.
ConnectionOpen (Connect())..
Please verify SQL Server is running and check your SQL Server registeration properties.
Any ideas?
Thanks
Hi,
I am not an sql server person, but have been asked to stop replication on sql server. Can someone please let me know how to do this.
Thanks,
Jo
We have a web applicaiton backend database uses sql server. Now we stop using this web application. I would like to stop this sql server database. What do you usually do? I can backup this database and delete this database. Or if i want to keep this database. What should i do?
Thanks for you help.
Hi out there!My publisher database holds an table with an column that is to small.The related subscriber-table I already have expanded (column fromvarchar50 -> varchar60).But I can't expand the table in the distributer-base, i get the error thatit can't be done because of replication.How can I expand my column? Have I to delete replication? If yes, how?Greetings Bjørn
View 2 Replies View RelatedI program a batch file for SQL server2000 disarstrer recovery. It just stops sqlserver service and copy data file to a flash drive, then restart service.
sc \S-HKRGCTTMA stop sqlagent$trips
timeout /t 50
sc \S-HKRGCTTMA stop mssql$trips
timeout /t 20
REM del dbyestoday*.* /q
REM move yestoday*.* dbyestoday
REM move oday*.* yestoday
REM cd oday
REM copy d: masql_data
REM sc start mssql$trips
REM sc start sqlagent$trips
When it run first line, shown: sc openScmanager Failed 1722.
The RPCservice is unavalible."
Does batch file can stop service?
Any help is welcome.
Peter
create login dave with password='abc', default_database=tempdb
View 6 Replies View Related
Hi,
I am using SQL Server 2005 at home.
My problem is I forgot my password to log in to my server.
I only remember user name is 'sa'.
I haven't used it for two to three months. So I forgot password.
Previously, When I used sql server 2000, my login is as windows login. so no problem.
But this time, I set seperate log in and I got this problem.
Any help will be appreciated.
Thanks
George
Hello everyone,
Since last so many days i am seeing that someone is trying to login to sql server through login name sa.but that login is failed.and this is occuring constantly.
Earlier i had same login failed message for another ip address.i have blocked that ip address through access-list in firewall.but now i am seeing the same message for another ip address.
(1).how can i permenently remove this message from Event log.
(2).What is the impact of this on sql server performance.is sql server performance degraded by this kind of contineous attack?
here i am attaching that report from event viewer log file.
2/26/2007 1:48:18 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:17 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:17 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:17 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:16 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:16 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:16 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:15 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:15 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:15 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:14 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:14 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:14 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:13 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:13 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:12 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:12 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:12 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:11 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:11 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:11 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:10 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:10 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:10 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:09 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:09 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:09 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:08 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:08 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:08 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:07 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:07 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:07 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:06 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:06 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:06 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:05 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:05 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:05 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:04 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:04 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:04 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:03 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:02 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:02 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:02 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:01 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:01 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:01 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:00 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:00 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:48:00 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:59 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:59 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:59 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:58 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:58 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:57 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:57 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:57 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:56 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:56 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:55 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:55 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:54 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:54 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:54 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:53 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:53 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:53 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:52 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:52 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:52 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:51 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:51 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:50 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:50 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:50 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:49 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:49 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:49 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:48 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:48 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:48 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:48 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:47 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:47 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:47 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:46 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:46 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:45 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:45 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:45 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:44 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:44 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:44 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:43 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:43 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
2/26/2007 1:47:43 AM MSSQL$CASHMAX Failure Audit (4) 18456 N/A CASHMAX Login failed for user 'sa'. [CLIENT: 192.192.81.126]
Needs your help to resolve this issue.
Thanks,
Bharat
Hiya
Since yesterday the sqlserver service has been falling over, my error logs says the below?
006-04-26 11:28:41.64 spid51 Using 'xpstar.dll' version '2000.80.2039' to execute extended stored procedure 'sp_MSgetversion'.
2006-04-26 11:28:41.92 spid51 Error: 15457, Severity: 0, State: 1
2006-04-26 11:28:41.92 spid51 Configuration option 'show advanced options' changed from 1 to 1. Run the RECONFIGURE statement to install..
2006-04-26 11:28:42.04 spid51 Using 'xplog70.dll' version '2000.80.2039' to execute extended stored procedure 'xp_msver'.
2006-04-26 14:44:08.92 spid2 SQL Server is terminating due to 'stop' request from Service Control Manager.
What do I need to do? Is is just a matter of running the reconfigure script? Yesterday night we had some monitoring installed on the server. Can anyone help?
Thanks
Hello buddies ,
I hope you hade good day , I didn't have ... but anyway.... I installed Active Directory on my dedicated server and after that uninstall that from my server and I delete NETWORK SERVICE from my Program Files completely and again I gave full permission to it and I chaked that Microsoft SQL Server and all folder has this account permission.
As i meantioned it's my dedicated server and It's damn problem for me can anybody tell me what I have to do exactly please
But when I tried to start my SQL Server , I got this error , (my VIA Portocol is disable) :
2007-10-11 02:52:38.46 Server Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)
Oct 14 2005 00:33:37
Copyright (c) 1988-2005 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
2007-10-11 02:52:38.46 Server (c) 2005 Microsoft Corporation.
2007-10-11 02:52:38.46 Server All rights reserved.
2007-10-11 02:52:38.46 Server Server process ID is 3388.
2007-10-11 02:52:38.46 Server Logging SQL Server messages in file 'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'.
2007-10-11 02:52:38.46 Server This instance of SQL Server last reported using a process ID of 216 at 10/9/2007 5:48:01 AM (local) 10/9/2007 2:18:01 AM (UTC). This is an informational message only; no user action is required.
2007-10-11 02:52:38.46 Server Error: 17053, Severity: 16, State: 1.
2007-10-11 02:52:38.46 Server UpdateUptimeRegKey: Operating system error 5(Access is denied.) encountered.
2007-10-11 02:52:38.46 Server Registry startup parameters:
2007-10-11 02:52:38.46 Server -d C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmaster.mdf
2007-10-11 02:52:38.46 Server -e C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG
2007-10-11 02:52:38.46 Server -l C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmastlog.ldf
2007-10-11 02:52:38.48 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2007-10-11 02:52:38.48 Server Detected 1 CPUs. This is an informational message; no user action is required.
2007-10-11 02:52:38.64 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2007-10-11 02:52:38.67 Server Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2007-10-11 02:52:39.71 Server Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2007-10-11 02:52:39.71 Server Database Mirroring Transport is disabled in the endpoint configuration.
2007-10-11 02:52:39.73 spid5s Starting up database 'master'.
2007-10-11 02:52:39.90 spid5s CHECKDB for database 'master' finished without errors on 2007-10-09 05:27:12.937 (local time). This is an informational message only; no user action is required.
2007-10-11 02:52:39.95 spid5s SQL Trace ID 1 was started by login "sa".
2007-10-11 02:52:39.98 spid5s Starting up database 'mssqlsystemresource'.
2007-10-11 02:52:40.10 spid5s Error: 15466, Severity: 16, State: 1.
2007-10-11 02:52:40.10 spid5s An error occurred during decryption.
2007-10-11 02:52:40.15 spid5s Failed to check for new installation or a renamed server at startup. The logic for this check has failed unexpectedly. Run setup again, or fix the problematic registry key.
2007-10-11 02:52:40.17 Server Error: 17182, Severity: 16, State: 1.
2007-10-11 02:52:40.17 Server TDSSNIClient initialization failed with error 0x5, status code 0x90.
2007-10-11 02:52:40.17 Server Error: 17182, Severity: 16, State: 1.
2007-10-11 02:52:40.17 Server TDSSNIClient initialization failed with error 0x5, status code 0x1.
2007-10-11 02:52:40.17 Server Error: 17826, Severity: 18, State: 3.
2007-10-11 02:52:40.17 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2007-10-11 02:52:40.17 Server Error: 17120, Severity: 16, State: 1.
2007-10-11 02:52:40.17 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
Bets regards,
Pooria
Hi, This is my firs time in this forum, we are getting this error and my sql server stop responding to users,
we have upgraded our server from sql 2000 to sql 2005 in jan 2008 and since jan it waz working f9 but from last month we are facing this problem,
we have Windows 2003 32bit and sql 2005 on HP Proliant server with RAID.
Is this a hardware problem or something wrong with sql server 2005.
followin the msg from sql log
SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [F: empdbdata empdb.mdf] in database [tempdb] (2). The OS file handle is 0x00000A20. The offset of the latest long I/O is: 0x000000097a0000
-masroor
I'm trying to setup a new server but need to stop people accessing the database via Access, Excel etc
Is there any way to set SQL server up to stop connections from such applications?
Is there any way to allow only certain users to connect via a DSN
We are not using windows authentication on the server
Cheers