Error Connecting Database Problem After Moving Databases 2000 To 2005

Nov 9, 2007

I have moved my databases to 2000 to instance of 2005 on the same server.
Now i set databases offline in 2000 as i did upgrade use backup & recovery method.

& my connection string
Password=test;Persist Security Info=True;User ID=test;Initial Catalog=databasename;Data Source=ipaddress

i was using above connection string to connect when using 2000 databases form applications in the production machine

I get the following error when i am running my applications now after moving to 2005


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)

IS it because i have two server on one server or
What do i need to do in order to fix this....tried several thing by searching nothing worked out..

Let me know
thanks


View 9 Replies


ADVERTISEMENT

After Moving 2000 Databses To 2005 Error With Maintanance Plan

Oct 25, 2007



I have moved few databases in 2000 to a different server which run's on sql server 2005 and its not a instance ogf 2000.
I backed up databases in 2000 moved those files to other server and then restored them.
I had solved the problem of orphand users by deleting and adding again.

Now when i try to setup maintenance plan i have the following error after walking through the wizard

TITLE: Maintenance Plan Wizard Progress
------------------------------
Adding tasks to the maintenance plan failed.
------------------------------
ADDITIONAL INFORMATION:
Object reference not set to an instance of an object. (Microsoft.SqlServer.Management.MaintenancePlanWizard)
------------------------------
BUTTONS:
OK
------------------------------

what do i need to fix this????Any help is appreciated...

And what else do i need to make sure everything in 2005 are working fine apart from orphand user.

Please let me know

Thanks in advance

View 1 Replies View Related

Getting When Connecting To SQL Server 2005 Error Using MS SQL 2000?

Jun 8, 2007

I'm new to using VS2005 and this is my first project connecting to our MS SQL 2000. App worked fine on my dev PC, connection to the same MS SQL Server. Published the web site to the web server (same server running MS SQL Server) and getting the below error. Is this a permission setup problem on SQL Server or does it really think it's connecting with a MS SQL 2005 database?
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)
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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

View 16 Replies View Related

After Moving 2000 Database To 2005 Database

Oct 15, 2007



I have used backup and restore method to upgrage 2000 databases to 2005 database.
What do i need to do in order to for my application or users to use databse in 2005 and remove 2000

let me know
thanjs

View 3 Replies View Related

Connecting To SQL 2000 Server Gives SQL 2005 Error Message

Aug 11, 2007

Hi,
Here is the syntax of the connection string within the web.config file:<connectionStrings><clear />
<add name="MyConnectionString" connectionString="Data Source=000.000.000;Initial Catalog=Database Name;Persist Security Info=True;User ID=XXXXXX;Password=XXXXXX;" providerName="System.Data.SqlClient" />
</connectionStrings> 
The test page has a GridView in it which uses the connectionstring fron the web.config file.
Error Message:

View 4 Replies View Related

Moving SQL Server 2005 Databases

May 19, 2007

What is the easiest way to move SQL Server 2005 databases from one oldserver to a new server?

View 1 Replies View Related

Moving System Databases SQL 2005

Mar 16, 2007

I am in the process of moving my system databases to another volume. I have accommplished the first section pertaining to master database.

I have reached step 3 in the Resource database move section down below.

It states to change the FILENAME path to match the new location of the master database. Do not change the name of the database or the file names.

ALTER DATABASE mssqlsystemresource
MODIFY FILE (NAME=data, FILENAME= 'new_path_of_mastermssqlsystemresource.mdf');

I changed the query to point ot the new location of the master, (E:MSSQLData)

ALTER DATABASE mssqlsystemresource
MODIFY FILE (NAME=data, FILENAME= E:MSSQLDatamssqlsystemresource.mdf');


I get the following error when I run the query:

Could not locate entry in sysdatabases for database mssqlsystemresource. No entry found with that name. Make sure that the name is entered correctly.

What am I doing wrong? My syntax must be incorrect. But I can't figure it. Anybody done this before.

These are the steps per msdn.
****************************************************************************************************************
To move the master database, follow these steps.
1. From the Start menu, point to All Programs, point to Microsoft SQL Server 2005, point to Configuration Tools, and then click SQL Server Configuration Manager.
2. In the SQL Server 2005 Services node, right-click the SQL Server (MSSQLSERVER) service and choose Properties.
3. In the SQL Server (MSSQLSERVER) Properties dialog box, click the Advanced tab.
4. Edit the startup parameters values to point to the planned location for the master database data and log files and click Apply. Moving the error log file is optional.
The parameter value for the data file must follow the -d parameter and the value for the log file must follow the -l parameter. The following example shows the parameter values for the default location of the master data and log files.
-dC:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmaster.mdf;-eC:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG;-lC:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDATAmastlog.ldf
If the planned relocation for the master data file is E:SQLData and the planned relocation for the log file is F:SQLLog, the parameter values would be changed as follows:
-dE:SQLDatamaster.mdf;-eC:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG;-lF:SQLLogmastlog.ldf
5. Stop the MSSQLSERVER service.
6. Physically move the files to the new location.
7. Restart the MSSQLSERVER service.
8. Verify the file change.
SELECT name, physical_name, state_desc
FROM sys.master_files
WHERE database_id = DB_ID('master');
********************************************************************************************

To move the Resource database, follow these steps.

1. Stop the MSSQLSERVER service if it is started.
2. Start the service in minimal mode. To do this, at the command prompt, enter <SQLPath>innsqlservr -c -f -T3608 where <SQLPath> is the path for the instance of ssNoVersion. For example, C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL. This will start the instance of ssNoVersion for master-only recovery.
3. Run these queries. Change the FILENAME path to match the new location of the master database. Do not change the name of the database or the file names.

ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME=data, FILENAME= 'new_path_of_mastermssqlsystemresource.mdf');

ALTER DATABASE mssqlsystemresource MODIFY FILE (NAME=log, FILENAME= 'new_path_of_mastermssqlsystemresource.ldf');
4. Make sure the Resource database is set to read-only by running this query:
ALTER DATABASE mssqlsystemresource SET READ_ONLY;
5. Physically move the files to the new location.
6. Restart the MSSQLSERVER service.

View 6 Replies View Related

Moving Sql Server 2005 DataBases From C: To D:

Dec 7, 2007



How do you move databases from C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
to d:MSSQL.1MSSQL?

I want to copy them, then detach/retach at the new location

Thanks

View 6 Replies View Related

Moving ReportServer Databases Example In Error?

May 21, 2007

The following link shows an example of backing-up and restoring the databases supporting Repor Server. My question is not so much Report Server-related but I question the restore syntax for restoring the logs.

http://msdn2.microsoft.com/en-us/library/ms156421.aspx



I honestly do not see how the following code would work. At least, I was not able to until I deleted everything after the "NORECOVERY". Then it seemed to work fine but maybe I missed something!



-- Restore the report server log file to new instance folder
RESTORE LOG ReportServer
FROM DISK='C:ReportServerData.bak'
WITH NORECOVERY, FILE=2
MOVE 'ReportServer' TO
'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDataReportServer.mdf',
MOVE 'ReportServer_log' TO
'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLDataReportServer_Log.ldf';
GO


Thanks a lot!

View 4 Replies View Related

Moving And Restoring Connections W/ SQL 2005 Databases

Dec 27, 2007



I have a question regarding moving databases within the same server but to a different drive. Using the 'Alter Database' query transaction procedures within the SQL Server Management Studio, I'm able to take a user database offline and move it. However, when using the Alter transaction to bring the database back online, I get errors. There was also an attempt that seemed to work, but the app that uses the database through ODBC can't see the database that was moved and errors out.
How can databases be moved and connections re-established within the same server?
Thanks...

View 1 Replies View Related

SQL Server 2005 Instance Is Dead After Moving System Databases!

May 20, 2008

Followed this article to move my model and msdb databes but I think I messed up. http://msdn.microsoft.com/en-us/library/ms345408.aspx
The instance will not start because it says one of the files does not match it's primary file (not sure if it's model or msdb)

I can bring the instance up in single user mode (NET START mssqlserver /f /t3608) but when I try to do a query to re-do my alter statements, it says i can't attach because only one seesion is allowed. in 2000 i used to be able to start query analyzer without starting enterprise manager..

When i try and start with a minimal config (sqlservr -c -m) it won't start. I get an error saying that one of my files does not match it's primary file (either model or msbd don't know which) any ideas????????

View 10 Replies View Related

Moving An Sql Server 2005 Database To A Sql Server 2000 Database

Dec 12, 2006

I am trying to move a database which I wrote in SQL Server 2005 to a SQL Server 2000 database.
I'm not sure the best way to do this.......
Can anyone enlighten me?.....
 

View 4 Replies View Related

Problem In Connecting 2 Databases With Sql Server 2005 Express

Aug 23, 2006

I am programming in VB6 using ADO 2.8. This connection and query works in MS access, SQL server 2000 and Sql Server 2005. does not work in Sql server 2005 express. Any Suggestions?

Connection String #1 Provider=SQLNCLI.1;Integrated Security=SSPI;Persist Security Info=False;AttachDBFileName=C:Program FilesMaterial_Management_SystemDATAMain.mdf;Data Source=Steve_Laptopsqlexpress

Connection String #2 Provider=SQLNCLI.1;Integrated Security=SSPI;Persist Security Info=False;AttachDBFileName=C:Program FilesMaterial_Management_SystemDATAItems.mdf;Data Source=Steve_Laptopsqlexpress


Sql Query: Select POLINE.ID as POLine_ID, PFMS.ID as Items_ID FROM POLINE LEFT JOIN Items.PFMS as PFMS ON POLINE.lItem_ID = PFMS.ID

Error: Msg 208, Level 16, State 1, Line 1
Invalid object name 'Items.PFMS'

Sql Query#2: Select POLINE.ID as POLine_ID, PFMS.ID as Items_ID FROM POLINE LEFT JOIN Items.dbo.PFMS as PFMS ON POLINE.lItem_ID = PFMS.ID

Error: Msg 208, Level 16, State 1, Line 1
Invalid object name 'Items.dbo.PFMS'.

I am running the queries directly from the 2005 Mgt window to take as many variables out of the equasion. I get the same error in Visual basic

How am I supposed to reference a join of 2 databases? Any suggestions

View 1 Replies View Related

Moving 2000 To 2005 Box

Mar 7, 2008

Hey guys I need to move a 2000DB to a 2005 just the database and the logins
Any suggestions of the best way to do this....
DTS backup attach database
Use the Upgrade Advisor....

View 1 Replies View Related

Moving Users From 2000 To 2005

Oct 23, 2006

What is the best way to move users from a 2000 sql server to a 2005 server? I have a bunch of issues with the passwords etc...

thanks for your time.

View 5 Replies View Related

Moving DB From Sql Server 2000 To 2005

May 21, 2008

Hello, what is the easiest way to move a DB (tables and data) from SQL server 2000 to 2005.

Ive been trying to export the DB tables from 2000 using Excel, yet i get "cannot expand named range" errors on several of the tables.

Is excel the way to go? another way? Can i use backup/restore?

Note: also moving from one machine to another.


Thanks for any help.

View 2 Replies View Related

HELLLP !!! Moving From Sql 2000 To 2005

Mar 30, 2008

Hi ,

I am working on a DWH project, and we decided few days ago to move from 2000 to 2005.
we installed the 2005 on the same server with two different instances for testing the 2005.
I migrate everything with the indexes but the issue is that queries at the 2005 take much more time than the same query on the 2000.
for example i have a nasty qry which join 14 tables. at the 2000 its take around 2.5 - 3 mins and at the 2005 its infinity , they both have the same indexes.

PLS ANYONE HAVE ANY IDEA WHATS THE PROBLEM ?

View 14 Replies View Related

Merging 2000 And 2005 Databases, Save As 2000

Apr 30, 2008

I have to merge the data from two databases, one is in SQL Server 2005 format, one is in 2000. The merged data will then reside on a SQL Server 2000 platform. Is there an easy way to do this through Management Studio or Enterprise Manager? Or will we have to export the data from the 2005 database to a flat file and import it into a new 2000 database. And then do the merge?

TIA

View 4 Replies View Related

Moving A 2000 Database To 7.0

Aug 9, 2001

We have developed our database in 2000. We want to run this DB on 7.0 But we get a bunch of errors. (we are not using any 2000 specific features).

Can anyone tell me way to export a database on 2000 to 7.0 ?

View 1 Replies View Related

Moving Data From SQL 2005 To SQL 2000 Daily

Feb 21, 2007

We need to upgrade our HR system from SQL 2000 to SQL 2005. Support for SQL 2000 ends 12/31/2007.

We have a third party vender that do not currently support SQL 2005. Employee's data is transfered from our HR database to the third party database for the purpose of yearly performance evaluation on a daily basis.

Both databases are currenlty on a SQL 2000 server.

Can data be transferred from a SQL 2005 database to a SQL 2000 database?

View 4 Replies View Related

Moving CRM, SPS, Project Web Server, SQL 2000 To SQL 2005

May 17, 2007

I am reciving a new powerful database server



My old database server runs SQL 2000 and has the CRM 3.0 app and database, our corporate web site (SharePoint Services 3.0) database, and Project Server 2007 database. The corporate site and project apps and web sites reside on our file server.



I want to move, upgrade or migrate the databases, corporate site and Project site to this new SQL 2005 server. I am a little unsure the best way to do this.



Should I move all the database first, then move the apps?



Should I do a restore of everything on the new server, and after I know it works just turn off the other server?



Am I missing a better way?



Anyone have any insight, let me know.



Thanks,



Ken

View 1 Replies View Related

Service Broker Not Working For Restored Databases (SQL 2000 Databases Restored On 2005)

Jan 24, 2006

I just restored my SQL server 2000 database on the SQL server 2005. after this i ran the Service broker sample ("Hello World") on this database by changing the AdventureWorks name to the new database name. The "setup.sql" runs fine. When i run the "SendMessage.sql" i was not getting any rows in the output (The message was not getting inserted into the queue). I checked the Service broker is enabled on this databased using the query "select is_broker_enabled from sys.databases where name = 'newdbname' " It was 1. I even tried the ALTER DATABASE SET ENABLE_BROKER. but it didnt work.

When i tried the sample on a newly created database it worked fine.

Is there any solution to make the restored database to work for service broker.

Thanks

Prashanth

View 3 Replies View Related

Moving Database To MSDE 2000

Dec 20, 2003

I have detached my database from the server and copied the mdf and ldf files to the new PC do I need to do anything but attach it to the MSDE? What about logins, roles, etc... does all this remain the same or do I need to delete the old and reenter them?

Please provide any help, thank you.

View 1 Replies View Related

Moving Sql 2000 DTS Packages To Sql 2005 Standard Edition

Feb 23, 2006

I have been tasked with upgrading around 150 SQL Server 2000 DTS packages to SSIS in SQL Server 2005 standard edition. I made a backup of the 2000 database upon which the DTS packages operate and restored it to the SQL 2005 server. So far, so good. I have the database in place. Now I need to get the DTS packages themselves into the SLQ 2005 server. I think I need to check my install and make sure that I have the SQL Server 2000 DTS services installed on the SQL 2005 server. I can do that.

However, I wonder what would be the most effective way to physically get the packages from the SQL 2000 server to the SQL 2005 server. Should I use structured storage files? If so, how do I go about opening them in SQL 2005 in order to save them to SQL server 2005?

I should mention that these packages make heavy use of ActiveX scripting so I am looking at rewriting them from scratch to be SSIS packages. I just need the packages on the SQL Server 2005 box so I can make sure I am creating exactly the same functionality in 2005 as existed in SQL server 2000. Each DTS 2000 individual package tends to be fairly simple and I think I can greatly improve the process by consolidating them.

Thanks in advance for any advice.

S. Wells

View 3 Replies View Related

2005 Connecting 2000 ?

Oct 28, 2006

if I install SServer Express EditionCan I connect to SServer 2000 DB ?thanks

View 1 Replies View Related

Connecting SQL 2000 Using SQL 2005

Feb 7, 2007

Hi,I have installed SQL 2005 in my PC and am trying to connect to SQLServer 2000 installed in a different machine. Both the server areinstalled in mixed mode.I can connect to the 2000 server from 2005's SSMS using windowsauthentication mode but fail to connect using SQL authentication.The follwoing message is displayed.Cannot connect to <servername>.Additional information:Login failed for user 'username'. (Microsoft SQL Server, Error: 18456)TIA,Taw.

View 4 Replies View Related

Error Connecting To SQL 2000

Aug 12, 2007

I am using Visual Studio 2005 with SQL Server 2000. I'm having an issue where I can build my website just fine for long periods of time, and then for what appears to be no reason, my site errors out when trying to connect to the database with the message below -- the thing is I don't want to use a SQL Server 2005 database, nor do I have Server 2005 or Server Express loaded. How can I unhook this and make it use SQL 2000?"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 - No connection could be made because the target machine actively refused it.) "

View 5 Replies View Related

Error When Connecting To Sql 2000

Sep 11, 2007

I am trying to connect to a sql 2k database using a Microsoft Application block. I get the following error. It is saying about 2005, I verified that SQL 2K is running on the server.
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
 
Any help will be appreciated.

View 5 Replies View Related

Error Connecting To SQL 2000

Aug 12, 2007

I am using Visual Studio 2005 with SQL Server 2000. I'm having an issue where I can build my website just fine for long periods of time, and then for what appears to be no reason, my site errors out when trying to connect to the database with the message below -- the thing is I don't want to use a SQL Server 2005 database, nor do I have Server 2005 or Server Express loaded. How can I unhook this and make it use SQL 2000?

"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 - No connection could be made because the target machine actively refused it.) "

View 1 Replies View Related

Newbie Question, Moving Data Between Sql Server 2000 And 2005

Jun 7, 2006

Hi,

I'm a newbie on SSIS and am trying to grasp my way through this.



I am trying to copy data from a Sql Server 2000 database to a simplified table in Sql Server 2005 database.



What I want is to move the data to a staging table, then drop the main
table and rename the staging table to the main table, to minimize the
down-time of the data. I can't get the workflow to work, because the
staging table has to exist when I run the package. I thought I could
use an "Execute SQL" task to generate the table before I would run the
task, but that doesn't work. Am I going about this the wrong way? Is
there an optimal solution to this problem so my data can be accessible
as much as possible.



Regards,

Atli

View 5 Replies View Related

Moving From 2000 To 2005: Issue Accessing Cursor Returned By Sp

Apr 28, 2006

I have a number of triggers that call a stored procedure that returns a cursor. The triggers then use the results of this cursor to do other actions.

My problem is that this works fine in SQL2000 but just won't work in SQL2005. When I try to access the results of the returned cursor, I get an error -2147217900 could not complete cursor operation because the set options have changed since the cursor was declared.

If I port the code contained in the sp into the trigger, it runs fine. But having to port over the sp's code defeats the whole concept of being able to re-use the sp.

Does anybody have any ideas of what could be going on?

I look forward to a quick response.

Dennis

View 8 Replies View Related

Moving A SQL Server 2000 Database That Is In Standby Mode

Jul 20, 2005

SQL Users/DBAs,I'm trying to move data files around for a database that is in standbymode. I can detach/attach the database fine usingSP_DETACH_DB/SP_ATTACH_DB , but when I re-attach the database the logsequence is broken and I can't restore any more logs. Does anyoneknow if there is a way to move around data files and keep the databasein standby mode?Thanks,JB

View 4 Replies View Related

SQL 2000 To SQL 2005 Upgrade Error - Database Down - Updated - Help Appreciated

Jan 3, 2007

SQL 2000 to SQL 2005 Upgrade Error - Database Down - Help Appreciated

I am upgrading a SQL 2000 standard database server to SQL 2005 standard on a windows 2003 server

I am logged in as domain admin and started the upgrade as 'sa'

The upgrade stops with the error:

Service MSSQLSERVICE can not be started. Verify you have sufficient privilages to start system services. The error code is (17185)

The error log shows:

2007-01-04 15:59:38.77 Server      Authentication mode is MIXED.

2007-01-04 15:59:38.79 Server      Microsoft SQL Server 2005 - 9.00.1399.06 (Intel X86)

 Oct 14 2005 00:33:37

 Copyright (c) 1988-2005 Microsoft Corporation

 Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

 

2007-01-04 15:59:38.79 Server      (c) 2005 Microsoft Corporation.

2007-01-04 15:59:38.79 Server      All rights reserved.

2007-01-04 15:59:38.79 Server      Server process ID is 4188.

2007-01-04 15:59:38.79 Server      Logging SQL Server messages in file 'F:SQLDataMSSQLlogERRORLOG'.

2007-01-04 15:59:38.79 Server      This instance of SQL Server last reported using a process ID of 2980 at 1/4/2007 3:56:58 PM (local) 1/4/2007 2:56:58 AM (UTC). This is an informational message only; no user action is required.

2007-01-04 15:59:38.79 Server      Registry startup parameters:

2007-01-04 15:59:38.79 Server        -d F:SQLDataMSSQLdatamaster.mdf

2007-01-04 15:59:38.79 Server        -e F:SQLDataMSSQLlogERRORLOG

2007-01-04 15:59:38.79 Server        -l F:SQLDataMSSQLdatamastlog.ldf

2007-01-04 15:59:38.79 Server      Command Line Startup Parameters:

2007-01-04 15:59:38.79 Server        -s MSSQLSERVER

2007-01-04 15:59:38.79 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2007-01-04 15:59:38.79 Server      Detected 4 CPUs. This is an informational message; no user action is required.

2007-01-04 15:59:38.83 Server      Set AWE Enabled to 1 in the configuration parameters to allow use of more memory.

2007-01-04 15:59:39.02 Server      Using the static lock allocation specified in the locks configuration option.  Allocated 20000 Lock blocks and 20000 Lock Owner blocks per node.  This is an informational message only. No user action is required.

2007-01-04 15:59:39.02 Server      Multinode configuration: node 0: CPU mask: 0x0000000a Active CPU mask: 0x0000000a. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

2007-01-04 15:59:39.04 Server      Multinode configuration: node 1: CPU mask: 0x00000005 Active CPU mask: 0x00000005. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.

2007-01-04 15:59:39.04 Server      Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.

2007-01-04 15:59:41.04 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-01-04 15:59:41.04 Server      Database Mirroring Transport is disabled in the endpoint configuration.

2007-01-04 15:59:41.04 spid7s      Starting up database 'master'.

2007-01-04 15:59:41.05 spid7s      1 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.

2007-01-04 15:59:41.07 spid7s      0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.

2007-01-04 15:59:41.07 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.

2007-01-04 15:59:41.08 spid7s      SQL Trace ID 1 was started by login "sa".

2007-01-04 15:59:41.08 spid7s      Starting up database 'mssqlsystemresource'.

2007-01-04 15:59:41.11 spid7s      Using 'dbghelp.dll' version '4.0.5'

2007-01-04 15:59:41.11 spid7s      ***Stack Dump being sent to F:SQLDataMSSQLLOGSQLDump0035.txt

2007-01-04 15:59:41.11 spid7s      SqlDumpExceptionHandler: Process 7 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

2007-01-04 15:59:41.11 spid7s      * *******************************************************************************

2007-01-04 15:59:41.11 spid7s      *

2007-01-04 15:59:41.11 spid7s      * BEGIN STACK DUMP:

2007-01-04 15:59:41.11 spid7s      *   01/04/07 15:59:41 spid 7

2007-01-04 15:59:41.11 spid7s      *

2007-01-04 15:59:41.11 spid7s      *

2007-01-04 15:59:41.11 spid7s      *   Exception Address = 78144D3A Module(MSVCR80+00014D3A)

2007-01-04 15:59:41.11 spid7s      *   Exception Code    = c0000005 EXCEPTION_ACCESS_VIOLATION

2007-01-04 15:59:41.11 spid7s      *   Access Violation occurred reading address 0000001E

2007-01-04 15:59:41.11 spid7s      * 

2007-01-04 15:59:41.11 spid7s      *

2007-01-04 15:59:41.11 spid7s      *  MODULE                          BASE      END       SIZE

2007-01-04 15:59:41.11 spid7s      * sqlservr                       01000000  02BA7FFF  01ba8000

2007-01-04 15:59:41.11 spid7s      * ntdll                          7C800000  7C8BFFFF  000c0000

2007-01-04 15:59:41.11 spid7s      * kernel32                       77E40000  77F41FFF  00102000

2007-01-04 15:59:41.11 spid7s      * MSVCR80                        78130000  781CAFFF  0009b000

2007-01-04 15:59:41.11 spid7s      * msvcrt                         77BA0000  77BF9FFF  0005a000

2007-01-04 15:59:41.11 spid7s      * MSVCP80                        7C420000  7C4A6FFF  00087000

2007-01-04 15:59:41.11 spid7s      * ADVAPI32                       77F50000  77FEBFFF  0009c000

2007-01-04 15:59:41.11 spid7s      * RPCRT4                         77C50000  77CEEFFF  0009f000

2007-01-04 15:59:41.11 spid7s      * USER32                         77380000  77411FFF  00092000

2007-01-04 15:59:41.11 spid7s      * GDI32                          77C00000  77C47FFF  00048000

2007-01-04 15:59:41.11 spid7s      * CRYPT32                        761B0000  76242FFF  00093000

2007-01-04 15:59:41.11 spid7s      * MSASN1                         76190000  761A1FFF  00012000

2007-01-04 15:59:41.11 spid7s      * Secur32                        76F50000  76F62FFF  00013000

2007-01-04 15:59:41.11 spid7s      * MSWSOCK                        71B20000  71B60FFF  00041000

2007-01-04 15:59:41.11 spid7s      * WS2_32                         71C00000  71C16FFF  00017000

2007-01-04 15:59:41.11 spid7s      * WS2HELP                        71BF0000  71BF7FFF  00008000

2007-01-04 15:59:41.11 spid7s      * USERENV                        76920000  769E3FFF  000c4000

2007-01-04 15:59:41.11 spid7s      * opends60                       333E0000  333E6FFF  00007000

2007-01-04 15:59:41.11 spid7s      * NETAPI32                       71C40000  71C97FFF  00058000

2007-01-04 15:59:41.11 spid7s      * SHELL32                        7C8D0000  7D0D2FFF  00803000

2007-01-04 15:59:41.11 spid7s      * SHLWAPI                        77DA0000  77DF1FFF  00052000

2007-01-04 15:59:41.11 spid7s      * comctl32                       77420000  77522FFF  00103000

2007-01-04 15:59:41.11 spid7s      * psapi                          76B70000  76B7AFFF  0000b000

2007-01-04 15:59:41.11 spid7s      * instapi                        48060000  48069FFF  0000a000

2007-01-04 15:59:41.11 spid7s      * sqlevn70                       4F610000  4F7A0FFF  00191000

2007-01-04 15:59:41.11 spid7s      * SQLOS                          344D0000  344D4FFF  00005000

2007-01-04 15:59:41.11 spid7s      * rsaenh                         68000000  6802EFFF  0002f000

2007-01-04 15:59:41.11 spid7s      * AUTHZ                          76C40000  76C53FFF  00014000

2007-01-04 15:59:41.11 spid7s      * MSCOREE                        61FB0000  61FF4FFF  00045000

2007-01-04 15:59:41.11 spid7s      * ole32                          77670000  777A3FFF  00134000

2007-01-04 15:59:41.11 spid7s      * msv1_0                         76C90000  76CB6FFF  00027000

2007-01-04 15:59:41.11 spid7s      * iphlpapi                       76CF0000  76D09FFF  0001a000

2007-01-04 15:59:41.11 spid7s      * kerberos                       62220000  62277FFF  00058000

2007-01-04 15:59:41.11 spid7s      * cryptdll                       766E0000  766EBFFF  0000c000

2007-01-04 15:59:41.11 spid7s      * schannel                       76750000  76776FFF  00027000

2007-01-04 15:59:41.11 spid7s      * COMRES                         77010000  770D5FFF  000c6000

2007-01-04 15:59:41.11 spid7s      * XOLEHLP                        622E0000  622E5FFF  00006000

2007-01-04 15:59:41.11 spid7s      * MSDTCPRX                       622F0000  62367FFF  00078000

2007-01-04 15:59:41.11 spid7s      * msvcp60                        780C0000  78120FFF  00061000

2007-01-04 15:59:41.11 spid7s      * MTXCLU                         62370000  62388FFF  00019000

2007-01-04 15:59:41.11 spid7s      * VERSION                        77B90000  77B97FFF  00008000

2007-01-04 15:59:41.11 spid7s      * WSOCK32                        71BB0000  71BB8FFF  00009000

2007-01-04 15:59:41.11 spid7s      * OLEAUT32                       77D00000  77D8BFFF  0008c000

2007-01-04 15:59:41.11 spid7s      * CLUSAPI                        62390000  623A1FFF  00012000

2007-01-04 15:59:41.11 spid7s      * RESUTILS                       623B0000  623C2FFF  00013000

2007-01-04 15:59:41.11 spid7s      * DNSAPI                         76ED0000  76EF8FFF  00029000

2007-01-04 15:59:41.11 spid7s      * winrnr                         76F70000  76F76FFF  00007000

2007-01-04 15:59:41.11 spid7s      * WLDAP32                        76F10000  76F3DFFF  0002e000

2007-01-04 15:59:41.11 spid7s      * rasadhlp                       76F80000  76F84FFF  00005000

2007-01-04 15:59:41.11 spid7s      * security                       62800000  62803FFF  00004000

2007-01-04 15:59:41.11 spid7s      * dbghelp                        671B0000  672C7FFF  00118000

2007-01-04 15:59:41.11 spid7s      *

2007-01-04 15:59:41.11 spid7s      *        Edi: 62FA0040:  62FA0028  671AFFF0  00000000  00000000  00000000  00000000 

2007-01-04 15:59:41.11 spid7s      *        Esi: 0000001E: 

2007-01-04 15:59:41.11 spid7s      *        Eax: 0416C05E:  C0400096  C0400416  00000416  000062FA  00000000  00000000 

2007-01-04 15:59:41.11 spid7s      *        Ebx: 0416C040:  0105F270  00002000  00000005  00000000  3368C1E0  00000000 

2007-01-04 15:59:41.11 spid7s      *        Ecx: 0105B010:  458B0046  01F88348  00D3850F  458B0000  89C23B50  0F342444 

2007-01-04 15:59:41.11 spid7s      *        Edx: 00000000: 

2007-01-04 15:59:41.11 spid7s      *        Eip: 78144D3A:  24FFA5F3  144E5495  C78B9078  000003BA  04E98300  E0830C72 

2007-01-04 15:59:41.11 spid7s      *        Ebp: 33D6E770:  33D6E790  01C65B97  62FA0040  0000001E  0416C040  0416C6DC 

2007-01-04 15:59:41.11 spid7s      *      SegCs: 0000001B: 

2007-01-04 15:59:41.11 spid7s      *     EFlags: 00010212:  0020006D  00690046  0065006C  005C0073  006F0043  006D006D 

2007-01-04 15:59:41.11 spid7s      *        Esp: 33D6E768:  62FA0040  33D6E7A4  33D6E790  01C65B97  62FA0040  0000001E 

2007-01-04 15:59:41.11 spid7s      *      SegSs: 00000023: 

2007-01-04 15:59:41.11 spid7s      * *******************************************************************************

2007-01-04 15:59:41.11 spid7s      * -------------------------------------------------------------------------------

2007-01-04 15:59:41.11 spid7s      * Short Stack Dump

2007-01-04 15:59:41.13 spid7s      78144D3A Module(MSVCR80+00014D3A)

2007-01-04 15:59:41.13 spid7s      01C65B97 Module(sqlservr+00C65B97)

2007-01-04 15:59:41.13 spid7s      01CA43B5 Module(sqlservr+00CA43B5)

2007-01-04 15:59:41.13 spid7s      01CA452E Module(sqlservr+00CA452E)

2007-01-04 15:59:41.13 spid7s      0217D3BD Module(sqlservr+0117D3BD)

2007-01-04 15:59:41.13 spid7s      0217B896 Module(sqlservr+0117B896)

2007-01-04 15:59:41.13 spid7s      0100889F Module(sqlservr+0000889F)

2007-01-04 15:59:41.13 spid7s      010089C5 Module(sqlservr+000089C5)

2007-01-04 15:59:41.13 spid7s      010086E7 Module(sqlservr+000086E7)

2007-01-04 15:59:41.13 spid7s      010D764A Module(sqlservr+000D764A)

2007-01-04 15:59:41.13 spid7s      010D7B71 Module(sqlservr+000D7B71)

2007-01-04 15:59:41.13 spid7s      010D746E Module(sqlservr+000D746E)

2007-01-04 15:59:41.13 spid7s      010D83F0 Module(sqlservr+000D83F0)

2007-01-04 15:59:41.13 spid7s      781329AA Module(MSVCR80+000029AA)

2007-01-04 15:59:41.13 spid7s      78132A36 Module(MSVCR80+00002A36)

2007-01-04 15:59:41.13 spid7s      Stack Signature for the dump is 0x2BEDE9E0

2007-01-04 15:59:41.27 spid7s      External dump process return code 0x20000001.

External dump process returned no errors.


2007-01-04 15:59:41.27 spid7s      Error: 17185, Severity: 16, State: 1.

2007-01-04 15:59:41.27 spid7s      Unable to update password policy.

2007-01-04 15:59:41.27 spid7s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Any clues?

Cheers

Paul

View 3 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved