Install Of SQL Server 2000 Dev Edition Over MSDE. Any Advice Appreciated.
Jul 20, 2005
It's arriving from ebuyer tomorrow for 32 quid. I already have an
instance of MSDE running on the laptop and ideally i would like SQL
server to be installed and use the current instance and not install
any other additional services. [hope i got my terminology correct
here.] Basically all i would like is to use the Enterprise Manager
with my existing MSDE database. I was wondering if there is anything i
should be doing before I install. Should i shut down the service or
leave it running for instance.
Thanks for any tips,
AndyB
View 2 Replies
ADVERTISEMENT
May 21, 2005
Can you install Sql Server 2000 Developer Edition with MSDE 2000 release A already installed?
View 2 Replies
View Related
Feb 25, 2004
I have been using MSDE and I recently got Microsoft SQL ServerTM 2000 Developer Edition as part of my MAPS pack. Can and should I replace MSDE with Microsoft SQL Server 2000 Developer Edition on my development pc? Thanks in advance for any advice on pros and cons or known issues?
View 4 Replies
View Related
Aug 9, 2004
Hello,
I recently upgraded my MSDE server to SQL Server 2000 database. After the upgrade, I see, every minute,in the logfile that the database is starting whilst in Enterprise manager the database is up and running. I would be grateful if you could bail me out of this anomaly.
Hope to hear from you soon.
Regards,
Albert.
View 2 Replies
View Related
Jul 3, 2006
According to this http://msdn2.microsoft.com/en-us/library/ms143393(d=robot).aspx, it seems that it cannot. But is this a complete chart?
Thanks for any help,
Peter
View 5 Replies
View Related
Sep 6, 2006
Hi All,
I am facing a familiar issue, with a slight variance in the situation. I have already spent hours googling for a solution, so along with the problem I'll highlight what I have already tried to remedy it.
Problem
--------
I am trying to install SQL Server 2000 Dev. Edition on my Win XP SP1 platform. I did a default instance installation. I am able to start up the server and keep it up.
Issue
-----
On opening the Enterprise Manager I get the error, "SQLDMO.DLL not registered, re-run SQL Server setup etc."
Next I navigated to <install dir>Microsoft SQL Server80ToolsBinn and executed regsvr32 sqldmo.dll and I get the following error, "LoadLibrary("sqldmo.dll") failed - Invalid Access to Memory Location"
Comments
----------
I have verified that all the relevant dlls are present in the above and <...>system32 folders. I have also created an alias for the server using the client network utility.
There was a time when I had installed SQL Server 2000 previously and I did manage to get it to work, even the sqldmo.dll registeration bit. But uninstalled it subsequently as I was having space issues.
Since then I have installed various XP hotfixes and security fixes, except for Win XP SP2
Any thoughts, anyone?????
View 1 Replies
View Related
Jul 18, 2007
Hi,
We have a suite of applications which go through the full product life cycle and I was wondering which SQL Server edition should be installed in every each environment from Proof of Concept -> Dev -> -> UAT -> Systest...
Production is straight forward but I am just not sure about all the other environments.
thanks
Lyn
View 3 Replies
View Related
Aug 18, 2004
I know people have put up this question before but I wanted some updated feedback.
I just bought Visual Studio Tools for MS Office and it comes with SQL Developer Edition. I am currently using VS.net 2003 and using MSDE with MS SQL Web Data Administrator to build my dbs then export the sql script.
I was wondering if I should uninstall the MSDE and install the DEv Ed so I can develop all the triggers, constraints etc through Enterprise Manager, therefore having a better setup DB. I know you can do all that through code but why reinvent the wheel.
One last question, with the Dev Ed you just export the schema and scripts to a machine with SQL Server installed once the DB is ready for deployment ? Is this correct?
I lied one more question, does the uninstall of MSDE leave much of a mess, what is the best way to get rid of it.
Thanks in advance
Pete
View 1 Replies
View Related
Feb 13, 2006
In the past I've used MSDE with Visual Studio.NET 2003. I'm going to start studying for an MCP in SQL Server 2000 so I'll probably get SQL Server 2000 Developer Edition. Will I be able to install this on my PC if it already has MSDE installed, or will I need to remove MSDE, etc? If there are any other things I need to be aware of please let me know.
Also should I stick with SQL Server 2000 while studying for the exam, or would I probably be able to use SQL Server 2005 with a book that uses SQL Server 2000? I don't know how different they are.
View 1 Replies
View Related
Jan 29, 2004
I'm trying to upgrade my SQL Server 2000 Developer's Edition to sp3a, I'm following the instructions.
I receive the following message:
Invalid product code was found. Check if product is installed.
I have installed this from CD I have with me. I followed instruction on http://support.microsoft.com/?kbid=311762
but I don't see product ID/code !!!!!
I have installed default instance (MSSQLSERVER) on my machine. How do I do Update to Service Pack 3a.
I can Install "Database Components "
Downloadable file name: SQL2KSP3.exe SP3a
but I can't install "SQL Server 2000 Desktop Engine(MSDE) "
Downloadable file name: SQL2kdesksp3.exe SP3a.
Any help?
Thank you.
View 1 Replies
View Related
Mar 14, 2007
Hi everyone...
I'm facing a problem while installing the SQL Server 2005 Express on Windows 2000 Pro with SP4.
After finishing the downloading from Microsoft I start the installation and things seems to go ok but during Extracting Files step a message appears "SQL Server Setup unexpectedly failed. For more information, review the setup summary log file in %Program Files%Microsoft SQL Server90Setup BootstrapLOGSummary.txt" and it terminates the installation.
I located the log file and open it but can't understand the problem..I copy the text and paste it here for anyone who can understand it.Please, it is very importand for me to work with SQL Server for my project. Any advice or information or anything else???
Thank you all,
HERE IS THE LOG FILE:
"Microsoft SQL Server 2005 Setup beginning at Wed Mar 14 07:45:33 2007
Process ID : 2684
c:c7720b32114815db82783dd06c2d54b9setup.exe Version: 2005.90.3042.0
Running: LoadResourcesAction at: 2007/2/14 7:45:33
Complete: LoadResourcesAction at: 2007/2/14 7:45:33, returned true
Running: ParseBootstrapOptionsAction at: 2007/2/14 7:45:33
Loaded DLL:c:c7720b32114815db82783dd06c2d54b9xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2007/2/14 7:45:33, returned false
Error: Action "ParseBootstrapOptionsAction" failed during execution. Error information reported during run:
Could not parse command line due to datastore exception.
Source File Name: utillibpersisthelpers.cpp
Compiler Timestamp: Wed Jun 14 16:30:14 2006
Function Name: writeEncryptedString
Source Line Number: 124
----------------------------------------------------------
writeEncryptedString() failed
Source File Name: utillibpersisthelpers.cpp
Compiler Timestamp: Wed Jun 14 16:30:14 2006
Function Name: writeEncryptedString
Source Line Number: 123
----------------------------------------------------------
Error Code: 0x80070002 (2)
Windows Error Text: Error: Action "ActivateLoggingAction" threw an exception during execution. Error information reported during run:
Datastore exception while trying to write logging properties.
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupStateScope.primaryLogFiles
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupStateScope"
02B1CFC0Unable to proceed with setup, there was a command line parsing error. : 2
Error Code: 0x80070002 (2)
Windows Error Text:
Class not registered.
Failed to create CAB file due to datastore exception
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "HostSetup" {"SetupBootstrapOptionsScope", "", "2684"} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupBootstrapOptionsScope.HostSetup
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupBootstrapOptionsScope"
Message pump returning: 2"
View 4 Replies
View Related
Nov 4, 2004
I downloaded and attempted to install MSDE 2000 on a win2k SP4 system. the command line was:
LOG>setup /settings "setup.ini" SAPWD="mypassword"
The process proceeds then a pop-up says the installation failed. The log reports:
---------------
2004-11-04 15:07:21.30 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
2004-11-04 15:07:21.35 server Copyright (C) 1988-2002 Microsoft Corporation.
2004-11-04 15:07:21.35 server All rights reserved.
2004-11-04 15:07:21.35 server Server Process ID is 1904.
2004-11-04 15:07:21.35 server Logging SQL Server messages in file 'C:librarydataMSSQLLOGERRORLOG'.
2004-11-04 15:07:21.41 server SQL Server is starting at priority class 'normal'(1 CPU detected).
2004-11-04 15:07:21.64 server SQL Server configured for thread mode processing.
2004-11-04 15:07:21.65 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2004-11-04 15:07:21.94 spid3 Warning ******************
2004-11-04 15:07:21.94 spid3 SQL Server started in single user mode. Updates allowed to system catalogs.
2004-11-04 15:07:22.03 spid3 Starting up database 'master'.
2004-11-04 15:07:22.83 server Using 'SSNETLIB.DLL' version '8.0.766'.
2004-11-04 15:07:22.83 spid5 Starting up database 'model'.
2004-11-04 15:07:22.96 spid3 Server name is 'MJWLAP2'.
2004-11-04 15:07:22.96 spid3 Skipping startup of clean database id 5
2004-11-04 15:07:23.00 spid3 Skipping startup of clean database id 6
2004-11-04 15:07:23.00 spid3 Starting up database 'msdb'.
2004-11-04 15:07:23.51 spid5 Clearing tempdb database.
2004-11-04 15:07:24.34 spid5 Starting up database 'tempdb'.
2004-11-04 15:07:24.53 spid3 Recovery complete.
2004-11-04 15:07:24.53 spid3 SQL global counter collection task is created.
2004-11-04 15:07:24.60 spid3 Warning: override, autoexec procedures skipped.
2004-11-04 15:07:25.56 server SQL server listening on .
2004-11-04 15:07:25.58 server Error: 17826, Severity: 18, State: 1
2004-11-04 15:07:25.58 server Could not set up Net-Library 'SSNETLIB'..
2004-11-04 15:07:25.58 server Unable to load any netlibs.
2004-11-04 15:07:25.59 server SQL Server could not spawn FRunCM thread.
-------------------------
Any help will be appreciated!
Mike
View 4 Replies
View Related
Mar 16, 2004
I am developing a project in Vb.net
using MSDE 2000 as backend.
I want to deployment my project in win98 OS PCs.
is it possible to install msde 2000 in win98
bye
S.Muhilan
View 2 Replies
View Related
Feb 3, 2004
I am getting an error when installing SP3a of MSDE. I get the error message "The instance name specified is invalid." This is the first SQL database installed, so there is no instance name. I have tried "default" and "MSSQLSERVER" as instance names without success.
your help is appreciated.
View 1 Replies
View Related
Nov 8, 2007
Hi All,
I was trying to restore MSDE 2000 database to SQL 20005 EE and I got stuck with the following error:
System.Data.SqlClient.SqlError: RESTORE detected an error on page (xxxx:xxxxxx) in database 'testdb' as read from the backup set.
Do you think some pages are corrupt from the db or the backup set?
Has anybody come across this? Any ideas to resolve this error?
Thanks,
Siva.
View 4 Replies
View Related
Aug 1, 2006
I have clients that have the MSDE version installed and we need to upgrade there program to the MSSQL 2005. Is there an easy way to convert the data? Should or Could I uninstall MSDE and than install MSSQL2005 WorkGrp? Will there data be affected? Any tips would be appreciated.Thanks!
View 1 Replies
View Related
Dec 29, 2004
** Error in msgbox : “Setup failed to configure the server. Refer to the server error logs and C:WINDOWSsqlstp.log for more information. �
** Cut From: C:WINDOWSsqlstp.log – ( previous exit codes look OK) ---
(previous text removed) …
21:54:29 C:Program FilesMicrosoft SQL Server80ToolsBinncnfgsvr.exe -F "C:WINDOWSsqlstp.log" -I MSSQLSERVER -V 1 -M 0 -Q "SQL_Latin1_General_CP1_CI_AS" -H 66364 -U sa -P
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
Connecting to Server ...
driver={sql server};server=cn91909-a;UID=sa;PWD=;database=master
[Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).
driver={sql server};server=cn91909-a;UID=sa;PWD=;database=master
[Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).
driver={sql server};server=cn91909-a;UID=sa;PWD=;database=master
[Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionRead (recv()).
SQL Server configuration failed.
###############################################################################
21:54:55 Process Exit Code: (-1)
21:57:07 Setup failed to configure the server. Refer to the server error logs and C:WINDOWSsqlstp.log for more information.
21:57:07 Action CleanUpInstall:
21:57:07 C:WINDOWSTEMPSqlSetupBinscm.exe -Silent 1 -Action 4 -Service SQLSERVERAGENT
21:57:07 Process Exit Code: (1060) The specified service does not exist as an installed service.
21:57:07 C:WINDOWSTEMPSqlSetupBinscm.exe -Silent 1 -Action 4 -Service MSSQLSERVER
21:57:07 Process Exit Code: (0)
21:57:07 StatsGenerate returned: 2
21:57:07 StatsGenerate (0x0,0x1,0xf000000,0x200,1033,303,0x0,0x1,0,0,0
21:57:07 StatsGenerate -1,debbie)
21:57:07 Installation Failed.
View 1 Replies
View Related
Jul 28, 2006
I have to creat virtual server. Then I Can't install sql server 2000 enterprise edition on winXP. What should i do? What do you think
View 1 Replies
View Related
Mar 16, 2007
When come to Create Instances screen and click next it prompt error message
although i had restart my computer.
A previous program Installation created pending file operations on the installation machine. You must restart the computer before running setup.
View 2 Replies
View Related
Jan 15, 2007
Hi there
Our ISP hosts our data on SQL Server Enterprise, but I also going to host the databases on my local machine.
As it's just local would Standard edition do? If I migrate the databases over, will it work?
Thanks in advance.
View 2 Replies
View Related
Apr 24, 2006
I've been using SQL Server 2005 Std. for my development work on a laptop w/ 2 GHz Celeron and 768 Mb RAM. Now that Express Edition has Reporting Services and Full-Text Search, would I be wise to just use it instead? I actually have both on my machine since Express Edition installed with VS 2005 Standard. Also, if I uninstall SQL Server 2005 Std. what will I lose? Thanks in advance.
-Mike
View 3 Replies
View Related
Jul 24, 2007
Hi,
Can we degrade from SQL Server 2000 Enterprise Edition to SQL Server 2000 Standand Edition without doing Uninstall and reinstall?
Thanks in advance,
View 1 Replies
View Related
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
Nov 9, 2007
Hi,
I would like to find out if there is any way to upgrade SQL Server 2000 (Ent) to 2005 (STD)
The Instance has many logins and jobs etc and I dont want to loose those
A document or some advice on how to go about it would help
Thanks
View 10 Replies
View Related
Feb 26, 2008
Hello all,
Here I need some help or suggestions for the following topic...
I am using SQL server 2000 enterprise edition installed on the machine. Now I wanted to change the edition from enterprise to standard.
There are around 4 user databases exists on the server.
What are the areas I have to take care while doing this? Could I do as normal installation?
No log shipping implemented on the server.
Your suggestions would be very helpful to me.
Thanks in advance.
View 4 Replies
View Related
Dec 15, 2005
I have heard that machines running applications with embedded MSDEfrequently experience conflicts between the MSDE apps and otherapplications such as BackupExec. What can anyone tell me about this?And if this is true, does/will the new SQL Server Express Editionbehave better?
View 1 Replies
View Related
Jan 29, 2008
Hello All,
I am migrating from MSDE to Sql Server Comapct Edition.I want to how will it affect the code and how large the changes will be. For example will i need to change only the connection string or if some of the methods used by MSDE or not available in the CE version. Any information and ideas reagrding this will be useful.
Thanks & Regards
Keerti Somasundaram
View 4 Replies
View Related
Jun 27, 2004
I can't connect to any instance of MSDE on my laptop using my web app. I duplicate the whole process on another local machine and have no problems. I'm using DNN, but it's not a problem with a connection string.
Over the last week I've had to rebuild this laptop - reformating and all. I'm running win xp pro, vs'03. I've tried this on msde2000sp3a & msde2000rela. Everthing is fully patched, updated, and current.
I'm working on two pcs at the same time with identical environments, doing one step on one keyboard and then the other:
I take one set of fresh DNN files and install them on each pc.
create a new db, user with dbo rights.
create a new virtual directory in iis.
alter the dotnetnuke.sln, dotnetnuke.vbproj.webinfo to reflect the path to the local site.
alter the web.config file with the connection string.
browse to the website (this is how dnn launches, creating the db from scripts, etc.)
At this point my desktop pc works great and I've got a new instance of DNN.
My laptop does launch dnn, but it can't connect to the db and says there's a problem with the connection string - but the only difference in the strings is the instance name - which isn't spelled wrong!!!!
So I'm led to believe that there is something wrong with the setup on the laptop which was just rebuilt.
It's got .net 1.1, msde2000sp3a, winxppro sp1. I've uninstalled and reinstalled all the components I can think of.
What would you do??? I'm completely out of ideas on this.
Do I format the hd and start again? That would hurt, but I've tried everthing else I can think of.
Oh, here's the other rub. I can create a system dsn, test the connection - and it works! I know that point's toward dnn, but like I've said I believe I've ruled that out.
Thanks for any advice...
View 3 Replies
View Related
May 1, 2005
its sql server 7.0 and im looking for the service network utility and service manager that it didnt come with.. where can i download it?
View 1 Replies
View Related
Nov 7, 2005
has anybody tried to do that yet? any experiences? how-tos?
View 3 Replies
View Related
Sep 26, 2007
Hi,
I am trying to upgrade MSDE 2000 to MS SQL Server 2005 Express Edition SP2 (Build 9.00.3042.0) using a silent install.
MSDE on our systems is installed as a standalone product. There is only a single default instance (MSSQLSERVER) running on the system. SQL Authentication mode is being used.
When I try and upgrade MSDE 2000 directly to MS SQL Server 2005 Express Edition SP2, the install fails with an error:
"SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade"
When I try to upgrade the default instance of MSDE to SQL Server 2005 Express Edition SP2 selecting Windows authentication (logging in as a domain/local administrator to the server), the install fails with an error:
"Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user <mydomain><AdminID>"
However, MSDE 2000 upgrade to an earlier version of MS SQL Server 2005 Express Edition (Build 9.00.1399.6) using SA Authentication works successfully without any errors.
So I tried to upgrade our MSDE installation to SQL Server 2005 Express Edition SP2 (Build 9.00.3042.0) as a 2 step process. First by upgrading MSDE to SQL Server 2005 (Build 9.00.1399.6) using SA Authentication which works successfully as mentioned earlier.
However, when I try and upgrade SQL Server 2005 (Build 9.00.1399.6) to SQL Server 2005 SP2 (Build 9.00.3042.0) using SA Authentication, I receive the same error as before:
"SQL Server Setup Cannot Upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade"
When I upgrade using Windows Authentication, the setup displays the following error:
"[Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again"
The log file content for the error is:
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------SQL_ERROR (-1) in OdbcStatement::execute_batch
sqlstate=01000, level=0, state=1, native_error=0, msg=[Microsoft][SQL Native Client][SQL Server]Signing sps ...
sqlstate=42000, level=16, state=1, native_error=15119, msg=[Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.
sqlstate=HY000, level=0, state=0, native_error=0, msg=[Microsoft][SQL Native Client]Unspecified error occurred on SQL Server. Connection may have been terminated by the server.
sqlstate=42000, level=16, state=2, native_error=2745, msg=[Microsoft][SQL Native Client][SQL Server]Process ID 51 has raised user error 50000, severity 20. SQL Server is terminating this process.
sqlstate=HY000, level=20, state=127, native_error=50000, msg=[Microsoft][SQL Native Client][SQL Server]Cannot create ##MS_AgentSigningCertificate## in msdb. INSTMSDB.SQL terminating.
Error Code: 15119
MSI (s) (08!80) [10:56:13:133]: PROPERTY CHANGE: Adding SqlUpgradeMessage property. Its value is 'SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again.'.
SQL Server Setup has encountered the following problem:
Failed to execute the Transact-SQL statement:
/**************************************************************/
/* Sign agent sps and ...
Script file: sqlagent90_msdb_upgrade.sql
The error was: [Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again.
SQL_ERROR (-1) in OdbcHandle::release
sqlstate=HY010, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Function sequence error
SQL_ERROR (-1) in OdbcHandle::release
sqlstate=HY010, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Function sequence error
SQL_ERROR (-1) in OdbcHandle::release
sqlstate=HY010, level=-1, state=-1, native_error=0, msg=[Microsoft][ODBC Driver Manager] Function sequence error
Error Code: 0x80073b0f (15119)
Windows Error Text: Source File Name: libodbc_statement.h
Compiler Timestamp: Wed Jun 14 16:28:15 2006
Function Name: OdbcStatement::execute_batch@sqlagent90_msdb_upgrade.sql@967
Source Line Number: 91
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The registry entries suggest that the version now is 9.00.3042.0. However, I am not sure if the upgrade was successful. I can connect to the database using the old SA user ID and password.
If anyone else has faced similar issues, please let me know the workaround for the same.
Thanks and Regards,
Sahil Girotra
View 3 Replies
View Related
Sep 28, 2007
Hi,
I am planning an upgrade from MSDE to SQL Server 2005 Express Edition SP2 (Build 9.00.3042.0) for our 2000/2K3 Servers. The MSDE installation on our servers is a standalone installation (default instance) and uses Mixed Mode Authentication. When I execute the setup program for upgrade and choose SQL Server Authentication (and enter the corresponding SA user Id password), the setup program displays an error "SQL Server Setup cannot upgrade the specified instance by using SQL Server Credential. You must use Windows Authentication credential for the upgrade". However, when I select Windows Authentication for the upgrade, the setup program displays an error €œ[Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet the requirements of the password filter DLL.. To continue, correct the problem, and then run SQL Server Setup again€? (Error Code 15119).
I even tried changing the Authentication mode from Mixed Mode to Windows Authentication (by changing the LoginMode registry key value to 1) and running the upgrade using Windows Authentication, but I receive the same error.
1) Is the password policy for SQL Server 2005 Express Edition SP2 different from MSDE or SQL Server 2005 Express Edition (Initial Version), since upgrade from MSDE to SQL Server 2005 Express Edition (Initial Version) worked successfully without any issues.
2) When I am using Windows Authentication for the upgrade, the installer does not prompt me for any password. What password is the installer validating against the password filter DLL? Is there a way to find it out? Also, is it possible to find out what was the reason for the password validation to fail?
I would really appreciate if I could get some answers to all the problems I am facing.
Thanks in Advance.
Regards,
Sahil Girotra
View 1 Replies
View Related
