Hi,
I am trying to install multiple application services on 1 sql server database. Is this possible? I do not know how to install anything but the default application services settings for the membership, roles, etc.
Please help if you can.
Thanks,
Ezeibe
My client has a server running MS 2003 Server for Smal Business Server, and it has SQL Server Express 2005 installed (I believe it is installed 3 times, as part of SharePoint, Veritas Backup Exec and ACT! applications).
I am trying to implement an application that uses SQL Server 2000, but the Server 2003 SBS does not support that version. So I need to launch an additional instance of SQL Server Exp 2005.
To do so, do I need to download and install SQL Server Express 2005 software again? Or can I just run SQLSVR.exe from an existing instance, but with a different instance name (sqlservr.exe -s<InstanceName>?
The reason I need another instance is that these existing instances limit DDL statements.
I am new to this and compare it to launching MS Word multiple times - you don't need to reinstall Word to run it multiple times.
Is launching from the command line a bad idea - and if it is, what is the better way to ensure that it launches under the local system context a service?
Thanks in advance for any help and insights. It is much appreciated.
I know that by default asp.net 2.0
creates the aspnetdb sql express database for storing membership, role
management, profiling etc. And I saw we have the aspnet_regsql tool to
have this installed in a standard sql server. But what should I do to
have these stored procedures, tables etc installed in an existing sql
express database? Aspnet_regsql doesn't seem suited for that.
I've noticed some sql scripts in the framework folder like
InstallCommon.sql, InstallMembership.sql, etc. They seem to be used to
create the regular aspnetdb.mdf database, should I just modify those
and run them against my own sql express database or is there a tool or
an easier way?
Cheers,
Frank.
I am running multiple instance of the same application. This application is connecting to the database and running stored procedures using ADODB (all code examples are taken from msado15).
The problem is that somehow these two applications are sharing something either with the connection or commands.
For instance if the two instances are in the following function at the same time then they both thow an SEH exception:
Code Snippet
inline _RecordsetPtr Command15::Execute ( VARIANT * RecordsAffected, VARIANT * Parameters, long Options ) {
struct _Recordset * _result = 0;
HRESULT _hr = raw_Execute(RecordsAffected, Parameters, Options, &_result);
if (FAILED(_hr)) _com_issue_errorex(_hr, this, __uuidof(this));
return _RecordsetPtr(_result, false);
}
The exception that occurs is: "First-chance exception ...: 0xC0000005: Access violation reading location 0x00000068."
And afterwords when they go to release the command an error occurs on
First-chance exception at 0x4de4120c in IpsEngine.exe: 0xC0000005: Access violation reading location 0xcccccccc.
Code Snippet
inline void _bstr_t::Data_t::_Free() throw()
{
if (m_wstr != NULL) {
::SysFreeString(m_wstr);
}
if (m_str != NULL) {
delete [] m_str;
}
}
This is being called from.
Code Snippet
inline void Command15::PutRefActiveConnection ( struct _Connection * ppvObject ) {
HRESULT _hr = putref_ActiveConnection(ppvObject);
if (FAILED(_hr)) _com_issue_errorex(_hr, this, __uuidof(this));
}
The exception that occurs: First-chance exception at ...: 0xC0000005: Access violation reading location 0xcccccccc.
Similarly when one instance releases a command using
Code Snippet
inline void Command15::PutRefActiveConnection ( struct _Connection * ppvObject ) {
HRESULT _hr = putref_ActiveConnection(ppvObject);
if (FAILED(_hr)) _com_issue_errorex(_hr, this, __uuidof(this));
}
The second instance of the application fails when running the command at the exact same time.
Code Snippet
inline _RecordsetPtr Command15::Execute ( VARIANT * RecordsAffected, VARIANT * Parameters, long Options ) {
struct _Recordset * _result = 0;
HRESULT _hr = raw_Execute(RecordsAffected, Parameters, Options, &_result);
if (FAILED(_hr)) _com_issue_errorex(_hr, this, __uuidof(this));
return _RecordsetPtr(_result, false);
}
The command and connections are not static and there should be completely seperate instances of these for each instance of the application. Does anybody know why this may be happening. Any help would be appreciated. Thanks in advance.
Can we install two instances of report server on the same machine?. We want to use the same hardware for two different methods of custom authentication. Both the server applications would then talk to the same database.
View 1 Replies View RelatedHello,
Trying to install SQL Server Express Edition from downloaded file SQLEXPR_DUT.EXE. MSXML6, SQL Setup support files, SQL Native Client and SQL VSS Writer are all installed ok, but SQL Server Database Services fails with a message that the SQL Server-service cannot be started and to look at Book Online for error files and starting manually. The end of the relevant error file would seem to be:
2006-07-26 18:45:47.33 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2006-07-26 18:45:47.33 Server Detected 1 CPUs. This is an informational message; no user action is required.
2006-07-26 18:45:47.48 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.
2006-07-26 18:45:47.49 Server Database Mirroring Transport is disabled in the endpoint configuration.
2006-07-26 18:45:47.49 spid5s Warning ******************
2006-07-26 18:45:47.50 spid5s SQL Server started in single-user mode. This an informational message only. No user action is required.
2006-07-26 18:45:47.50 spid5s Starting up database 'master'.
2006-07-26 18:45:47.60 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2006-07-26 18:45:47.71 spid5s SQL Trace ID 1 was started by login "sa".
2006-07-26 18:45:47.75 spid5s Starting up database 'mssqlsystemresource'.
2006-07-26 18:45:47.78 spid5s The resource database build version is 9.00.2047. This is an informational message only. No user action is required.
2006-07-26 18:45:48.20 spid5s Error: 15209, Severity: 16, State: 1.
2006-07-26 18:45:48.20 spid5s An error occurred during encryption.
2006-07-26 18:45:48.20 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
I need some opinion about coping data tables from auto-generated ASP.NET database into SQL 2000 database.
View 2 Replies View RelatedI can't seem to get all of the SQL9_Hotfix_KB913090_sqlrun_sql.msp.log to post (too big), but I can post the SQL9_Hotfix_KB913090.log file...hope that helps and which seems to me might contain the clue as to what's going. Any ideas would be appreciated. This is happening on a fresh install of Win Server 2003 and SQL Server standard 2005.
Thanks,
Steve
04/09/2007 16:14:30.562 ================================================================================
04/09/2007 16:14:30.578 Hotfix package launched
04/09/2007 16:14:33.312 Product discovery successfully completed during the install process for MSSQLSERVER
04/09/2007 16:14:33.328 SP Level check successfully completed during the install process for MSSQLSERVER
04/09/2007 16:14:33.359 Product language check successfully completed during the install process for MSSQLSERVER
04/09/2007 16:14:33.390 Product version check successfully completed during the install process for MSSQLSERVER
04/09/2007 16:14:33.421 Command-line instance name check completed during the install process
04/09/2007 16:14:33.437 Baseline build check completed during the install process
04/09/2007 16:16:52.828 Attempting to install instance: MSSQLSERVER
04/09/2007 16:16:52.875 Attempting to install target: TURBULENT2
04/09/2007 16:16:53.015 Attempting to stop service: SQLSERVERAGENT
04/09/2007 16:16:58.171 Successfully stopped service: SQLSERVERAGENT
04/09/2007 16:16:58.203 Attempting to stop service: MSSQLServer
04/09/2007 16:17:00.250 Successfully stopped service: MSSQLServer
04/09/2007 16:17:00.281 Attempting to check for locked files: sqlrun_sql.msp
04/09/2007 16:17:00.468 Attempting to check for locked files: \TURBULENT2f$9104ddf6956f8b22663aHotFixSQLFilessqlrun_sql.msp
04/09/2007 16:17:00.500 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.out
04/09/2007 16:17:38.125 MSP returned 1602: The user cancels installation.
04/09/2007 16:17:38.328 Successfully checked file: \TURBULENT2f$9104ddf6956f8b22663aHotFixSQLFilessqlrun_sql.msp
04/09/2007 16:17:38.359 Successfully opened registry key: SystemCurrentControlSetControlSession Manager
04/09/2007 16:17:38.421 Failed to read registry key: PendingFileRenameOperations
04/09/2007 16:17:38.468 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlfilt.dll
04/09/2007 16:17:38.515 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnThaWBrkr.dll
04/09/2007 16:17:38.562 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnquery.dll
04/09/2007 16:17:38.609 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnls400.dll
04/09/2007 16:17:38.687 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnlhtml.dll
04/09/2007 16:17:38.734 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsir5jp.dll
04/09/2007 16:17:38.765 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftesql.exe
04/09/2007 16:17:38.812 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftepxy.dll
04/09/2007 16:17:38.843 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftefd.exe
04/09/2007 16:17:38.875 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsfte.dll
04/09/2007 16:17:38.890 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnLangWrbk.dll
04/09/2007 16:17:38.921 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnkorwbrkr.dll
04/09/2007 16:17:38.937 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinninfosoft.dll
04/09/2007 16:17:38.968 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERefFTERef.dll
04/09/2007 16:17:39.000 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnCHTBRKR.DLL
04/09/2007 16:17:39.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnChsBrkr.dll
04/09/2007 16:17:39.046 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COMResources1033REPLRES.rll
04/09/2007 16:17:39.062 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COM
eplrec.dll
04/09/2007 16:17:39.093 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COM
plisapi.dll
04/09/2007 16:17:39.156 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:WINDOWSassemblyGAC_32Microsoft.SqlServer.Replication9.0.242.0__89845dcd8080cc91Repl.dll
04/09/2007 16:17:39.171 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.DataStorage9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.DataStorage.dll
04/09/2007 16:17:39.203 Failed to read version information for the following file: C:Program FilesCommon FilesMicrosoft SharedDatabase ReplicationResources10332005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
plhtfin.sql
04/09/2007 16:17:39.218 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
C:Program FilesMicrosoft SQL Server90COMqrdrsvc.exe
04/09/2007 16:17:39.250 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COMsnapshot.exe
04/09/2007 16:17:39.281 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COM
eplmerg.exe
04/09/2007 16:17:39.296 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90COM ablediff.exe
04/09/2007 16:17:39.328 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COMDISTRIB.exe
04/09/2007 16:17:39.359 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnDatabaseMail90.exe
04/09/2007 16:17:39.390 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources30822005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources2052sqlevn70.rll
04/09/2007 16:17:39.406 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10422005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1041sqlevn70.rll
04/09/2007 16:17:39.437 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10402005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1036sqlevn70.rll
04/09/2007 16:17:39.453 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10332005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1031sqlevn70.rll
04/09/2007 16:17:39.484 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10282005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033XPStar90.RLL
04/09/2007 16:17:39.515 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll
04/09/2007 16:17:39.531 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll
04/09/2007 16:17:39.562 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll
04/09/2007 16:17:39.578 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn6.6.3.5
C:Program FilesMicrosoft SQL Server90Sharedmsxmlsql.dll
04/09/2007 16:17:39.609 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2.0.3609.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlrw.dll
04/09/2007 16:17:39.640 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll
04/09/2007 16:17:39.656 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll
04/09/2007 16:17:39.687 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll
04/09/2007 16:17:39.703 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLBOOT.dll
04/09/2007 16:17:39.734 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxplog70.dll
04/09/2007 16:17:39.765 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnatchp~1.dll
04/09/2007 16:17:39.796 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll
04/09/2007 16:17:39.812 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll
04/09/2007 16:17:39.843 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll
04/09/2007 16:17:39.875 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL
04/09/2007 16:17:39.906 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL
04/09/2007 16:17:39.921 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL
04/09/2007 16:17:39.953 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll
04/09/2007 16:17:39.984 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll
04/09/2007 16:17:40.000 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll
04/09/2007 16:17:40.031 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE
04/09/2007 16:17:40.062 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE
04/09/2007 16:17:40.078 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE
04/09/2007 16:17:40.140 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90SharedResources10339.0.2047.0
C:Program FilesMicrosoft SQL Server90Sharedmsmdrdir.dll
04/09/2007 16:17:40.156 Failed to read version information for the following file: C:Program FilesCommon FilesSystemole db2.0.3609.0
C:Program FilesCommon FilesSystemole dbxmlrw.dll
04/09/2007 16:17:40.171 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll
04/09/2007 16:17:40.203 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll
04/09/2007 16:17:40.218 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll
04/09/2007 16:17:40.265 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe
04/09/2007 16:17:40.281 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe
04/09/2007 16:17:40.296 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe
04/09/2007 16:17:40.312 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll
04/09/2007 16:17:40.328 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll
04/09/2007 16:17:40.359 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll
04/09/2007 16:17:40.375 Failed to read version information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90enMicrosoft.AnalysisServices.AdomdClient.xml
04/09/2007 16:17:40.390 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90Microsoft.AnalysisServices.AdomdClient.dll
04/09/2007 16:17:40.421 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices.AdomdClient9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.AdomdClient.dll
04/09/2007 16:17:40.437 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033
C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033sqlcm.xml
04/09/2007 16:17:40.453 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll
04/09/2007 16:17:40.484 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll
04/09/2007 16:17:40.500 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll
04/09/2007 16:17:40.515 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll
04/09/2007 16:17:40.531 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll
04/09/2007 16:17:40.546 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll
04/09/2007 16:17:40.578 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll
04/09/2007 16:17:40.593 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll
04/09/2007 16:17:40.609 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll
04/09/2007 16:17:40.625 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources10332005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstallsysdbupg.sql
04/09/2007 16:17:40.656 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL
04/09/2007 16:17:40.671 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL
04/09/2007 16:17:40.687 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL
04/09/2007 16:17:40.703 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinn2.0.3609.0
C:Program FilesMicrosoft SQL Server90ToolsBinnSQLdiag.exe
04/09/2007 16:17:40.718 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinn2005.90.2047.0
C:Program FilesMicrosoft SQL Server90Sharedsqlsvc~1.dll
04/09/2007 16:17:40.765 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll
04/09/2007 16:17:40.781 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll
04/09/2007 16:17:40.796 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll
04/09/2007 16:17:40.812 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll
04/09/2007 16:17:40.843 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll
04/09/2007 16:17:40.875 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll
04/09/2007 16:17:40.890 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll
04/09/2007 16:17:40.906 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll
04/09/2007 16:17:40.937 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll
04/09/2007 16:17:40.968 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll
04/09/2007 16:17:40.984 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll
04/09/2007 16:17:41.000 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll
04/09/2007 16:17:41.015 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared2005.90.2047.0
C:Program FilesMicrosoft SQL Server90Sharedsqlsqm.exe
04/09/2007 16:17:41.046 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared9.0.2047.0
C:Program FilesMicrosoft SQL Server90Shareddbghelp.dll
04/09/2007 16:17:41.062 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe
04/09/2007 16:17:41.125 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe
04/09/2007 16:17:41.171 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe
04/09/2007 16:17:41.203 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Rmo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Rmo.dll
04/09/2007 16:17:41.234 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.DLL
04/09/2007 16:17:41.250 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.DataWarehouse.Interfaces9.0.242.0__89845dcd8080cc91Microsoft.DataWarehouse.Interfaces.DLL
04/09/2007 16:17:41.265 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.RegSvrEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.RegSvrEnum.dll
04/09/2007 16:17:41.281 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
04/09/2007 16:17:41.312 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
04/09/2007 16:17:41.328 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
04/09/2007 16:17:41.359 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.ServiceBrokerEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ServiceBrokerEnum.dll
04/09/2007 16:17:41.375 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.WmiEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.WmiEnum.dll
04/09/2007 16:17:41.406 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SqlEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SqlEnum.dll
04/09/2007 16:17:41.421 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SmoEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SmoEnum.dll
04/09/2007 16:17:41.453 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Smo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Smo.dll
04/09/2007 16:17:41.484 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlSAC.exe
04/09/2007 16:17:41.515 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedMicrosoft.SqlSac.Public.dll
04/09/2007 16:17:41.687 Attempting to install file: sqlrun_sql.msp
04/09/2007 16:17:41.750 Attempting to install file: \TURBULENT2f$9104ddf6956f8b22663aHotFixSQLFilessqlrun_sql.msp
04/09/2007 16:17:41.765 Creating MSP install log file at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.log
04/09/2007 16:17:41.796 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
04/09/2007 16:17:41.812 Failed to read registry key: Debug
04/09/2007 16:19:50.187 MSP returned 1603: A fatal error occurred during installation.
04/09/2007 16:19:50.250 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
04/09/2007 16:19:50.265 Failed to read registry key: Debug
04/09/2007 16:19:50.296 Unable to install MSP file: \TURBULENT2f$9104ddf6956f8b22663aHotFixSQLFilessqlrun_sql.msp
04/09/2007 16:19:50.312 The following exception occurred: Unable to install Windows Installer MSP file Date: 04/09/2007 16:19:50.312 File: depotsqlvaultsetupmainsetupsqlsesqlsedllcopyengine.cpp Line: 856
04/09/2007 16:19:50.437
04/09/2007 16:19:50.468 Product Status Summary:
04/09/2007 16:19:50.500 Product: SQL Server Native Client
04/09/2007 16:19:50.546 SQL Server Native Client (RTM ) - Success
04/09/2007 16:19:50.578
04/09/2007 16:19:50.609 Product: Setup Support Files
04/09/2007 16:19:50.640 Setup Support Files (RTM ) - Success
04/09/2007 16:19:50.656
04/09/2007 16:19:50.687 Product: Database Services
04/09/2007 16:19:50.734 Database Services (SP1 2047 ENU) - Failure
04/09/2007 16:19:50.750 Details: Unable to install Windows Installer MSP file
04/09/2007 16:19:50.781 Reporting Services (SP1 2047 ENU) - Not Applied
04/09/2007 16:19:50.812
04/09/2007 16:19:50.843 Product: Client Components
04/09/2007 16:19:50.890 Client Components (SP1 2047 ENU) - Not Selected
04/09/2007 16:19:50.921
04/09/2007 16:19:50.953 Product: MSXML 6.0 Parser
04/09/2007 16:19:50.968 MSXML 6.0 Parser (RTM ) - Not Selected
04/09/2007 16:19:51.015
04/09/2007 16:19:51.046 Product: SQLXML4
04/09/2007 16:19:51.078 SQLXML4 (RTM ) - Not Selected
04/09/2007 16:19:51.109
04/09/2007 16:19:51.125 Product: Backward Compatibility
04/09/2007 16:19:51.140 Backward Compatibility (RTM ) - Not Selected
04/09/2007 16:19:51.171
04/09/2007 16:19:51.203 Product: Microsoft SQL Server VSS Writer
04/09/2007 16:19:51.265 Microsoft SQL Server VSS Writer (RTM ) - Not Selected
04/09/2007 16:19:51.296
04/09/2007 16:29:32.812 Hotfix package closed
I would like to know if it is possible to have different applications on separate report servers sharing one report server database. If so are there possible issues or ptfalls to this type of architecture?
Thanks,
thecoleman
Hi,
I think this is a question for the specialists among us.
Can I use one general reporting server (installed on instance MAINREPORTING)
for multiple customers who all have their own sql instance (CUST1, CUST2, CUST3, ..)
I would use UserAuthenciation on the reportserver url to display the specific reports customers can use.
Is this possible, and what do i have to take care off concerning installation and/or configuration (especially on
the reporting side) ?
Greetings
Vinnie
I am running SQL 7.0 as the default instance and SQL 2K as a named instance. Each is using a different port....7.0 is using port 1433 and 2K is using 1024. Everything appears to be up and running fine on the server. However, I am not able to access the 2K instance from a client. I have tried to use both TCP IP and named pipes setting them up using the server network utility and the client network utility. No luck anywhere. I continue to get connection errors...check network documentation...
ANY IDEAS??????
Is there any limit on SQL server Multiple Instances? if we require to run 60+ Instances on single machine what will be the minimum hardware requirements.
View 3 Replies View RelatedDear Listers,
1.) Is it possible to install Analysis Services on multiple SQL Server 2000 instances? If it is, then can you instruct me as to how to perform the install. If it is not possible, then does one restrict access to cube data via the Database Role Manager?
ie. The host box is - DOILAB30 with Analysis Services & SP2
Instance - DOILAB30/DOILAB30_FIN (Can AS be installed here?)
Do I severely restrict the membership of OLAP Admins?
2). Re. AS maintenance. - How do I backup and restore OLAP dbs/cubes etc. Following a restore, what issues, such as cube users/permissions should I be aware of? (if any).
TIA
John
Hello,
There are several instances in SQL Server. I use RDA method to access SQL Server from mobile devices. But RDA method only gets the server IP,not the instance name. So, how can I define RDA to access to the instance that I need?
Hello all,
I am trying to built a general demo machine for our multiple resellers.
Is it possible to have multiple database instances (one per reseller) with each of them their own reporting instance, running on the same server (also same IIS). In our DNS and in the IIS settings i will reroute the specific reseller to his specific reporting url (eg: http://www.demosite.reseller1.com/reports (this is not a real url), will be rerouted via dns to the
specific reporting url for reseller one ... and so on.)
Each reseller must be able to has it own reports, subscriptions, models and access to reportbuilder.
Can this be accomplished ?
I have tried already a few times but get stuck when i want to upload reports/datasources to the specific websites. Also i have encountered the fact that if i succeed in uploading data to one reporting site and i want to upload different data to
another site, the initial site is also changed with the data of the second upload.
Can anyone point me into the right direction how to solve this problem .
Greetings
Vinnie
I have found a lot of info on MS site regarding installing SQL Server 2005 Express as part of an application. I have found these articles to be extremely inaccurate or at best incomplete.
1. The documentation says all I need is the setup.exe from SQLEXP but this is not true.
2. When I do launch setup.exe during my app's install, it fails because setup.exe trys to run the support.msi. Of course this causes failure because my install is also an msi.
So, does anyone know how to install SQLEXPRESS as part of my app's install?
Thanks.
Hi all,
Can a MIRROR server have mirrored databases on many instances or must all of the mirrored databases on a server reside on one instance?
This initial implementation worked fine:
PRINCIPAL ServerPROD1instance01 endpoint1430
MIRROR ServerDRinstance01 endpoint1440
WITNESS ServerZ endpoint1450
This second implementation (different PRINCIPAL server to same MIRROR but to a different instance)
PRINCIPAL ServerPROD2instance5 endpoint1430
MIRROR ServerDRinstance02 endpoint1440 <<same mirror server but different instance
WITNESS ServerZ endpoint1450
I know that you can only install one endpoint on each server. Does that mean that the endpoint can only resolve to one instance though?
The second implementation looks fine until the final step (start mirroring). I get the following error:
An error occured while starting mirroring
Alter failed for database 'test'
An exception occurred while executing transaction-sql statement or batch
The remote copy of database 'test' does not exist. Check the database name and resissue the command
I have created the test database in instance02 and rolled a log onto it. It is currently in recovery mode - waiting patiently for another log.....
I have read books online and 2k5 unleashed but can't see anything that relates to an implementation across mutliple instances on the DRmirrored servers.
Has anyone tried to do this? Can you confirm its possible?
Many thanks in advance...
Is it possible to have more than one instance of SQL Server on a failover Active/Passive cluster? What are the concerns/ramifications if that indeed is possible?
View 4 Replies View RelatedGreetings... I'm working at consolidating several Reporting Services installations into one so we can decommission some old servers. We have two Report Servers that are in SQL Server 2000 and three that are in SQL Server 2005 (none are in a web farm configuration). I can upgrade the 2000 databases to 2005 format just fine, but now how do I merge these five ReportServer/ReportServerTempDB databases into one? I'm reluctant to redeploy reports to the "official" Report Server because we lose security, subscription, and scheduling information by doing that. So redeploy would cost us time and data loss over hundreds of reports, thus my hope to merge the databases at a data level. Is there a tool to automate this process, or has anyone tried this before? Thanks in advance.
Austin
Good Day,
I have an application that is being developed on Visual Studio 2005 (VB) and SQL Express. The application is set up to use the SQL Express on the development computer, and if an Internet or CD install is built, it installs SQL Express as expected. The question is, when it is time to deploy and put the SQL Express database on the 2003 server, how should the install on the server be done and how should we set the database path to the server?
Thanks,
Dave
I was told that if I wanted to setup mirroring between multiple instance on the same server that each endpoint had to be different number. Is that true? Or can I use the default 5022 for each instance?
Ex.
Server1Instance1
Use endpoint 5022
Server1Instance2
Use endpoint 5022
VS
Server1Instance1
Use endpoint 5022
Server1Instance2
Use endpoint 5023
i want to run a transaction across mulitpule instences of sqlserver with out linked server.
distributed trnasaction can do it with link server , can it do it with out linked server.
Hi,I'm having a problem running a distributed transaction between twolinked servers that both have multiple instances of SQL Serverinstalled on them. This is the error message that I receive:"The operation could not be performed because the OLE DB provider'SQLOLEDB' was unable to begin a distributed transaction.[OLE/DB provider returned message: New transaction cannot enlist in thespecified transaction coordinator. ]OLE DB error trace [OLE/DB Provider 'SQLOLEDB'ITransactionJoin::JoinTransaction returned 0x8004d00a]."The query follows the format:"BEGIN DISTRIBUTED TRANUPDATE [LINKEDSERVER1INSTANCE_NAME].DB.OWNER.TABLENAMESET fieldname = alias2.fieldnameFROM tablename alias2JOIN [LINKEDSERVER1INSTANCE_NAME].DB.OWNER.TABLENAME alias1on alias2.urn=alias1,urn"[color=blue]>From what I can gather from various sources the SQL Server must be[/color]named the same as the computer which it is installed on. However, if Ihave two instances of SQL Server, they cannot both be named the same asthe computer. Does anyone know of a way around this or whether I'mbarking up the wrong tree completely?Many thanks.
View 2 Replies View RelatedI have a website running under Windows Server 2003 which I am trying to deploy Reportin Services to using a custom security extension using Forms authentication. There is also another website which is just a Report Server running on this IIS 6.
On my development machine, XP with IIS 5.1, the Website with Reporting Services using forms authentication works fine, shares cookies for authentication and all that jazz. but trying to configure a second instance of Reporting Services on Server 2003 is not behaving.
Is there some trickery or details involved with running two instances of Reporting Services?
Also in the Configure Report Server tool it is failing and so not initializing on the last step of the Database Setup
Setting Connection Info for Reporting Server
ReportServicesConfigUI.WMIProvider.WMIProviderException: An error occurred when attempting to connect to the report server remote procedure call (RPC) end point. Verify that the Report Server Windows service is running, and then retry the operation.
---> System.Runtime.InteropServices.COMException (0x800706B3): The RPC server is not listening. (Exception from HRESULT: 0x800706B3)
--- End of inner exception stack trace ---
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ThrowOnError(ManagementBaseObject mo)
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.ListReportServersInDatabase(RSReportServerInfo[]& serverInfos)
Hi
We are trying to setup a number of SQL Server 2005 database instances on a single server. The server has multiple IP addresses bound to its network interface (card). Each instance is configured to listen on a specific (unique) port on 127.0.0.1 and port 1433 on a specific (unique) IP address configured on the network interface. Finally, there is another instance of SQL Server (which also has the Reporting Services, Analysis Services and Integration Services installed) that does not allow remote connections and has TCP/IP disabled.
SSL is configured for all instances, apart from the non-remote connections instance, as follows: The same self-signed certificate is specified for every instance. This certificate has been configured for all 127.0.0.1 ports and port 1433 on all IPs in use for any of the instances using httpcfg as documented. The Force Encryption option is enabled and the Hide Instance option is disabled.
All appears to work correctly, and the "The certificate was successfully loaded for encryption" message appears when sp_readerrorlog is run, for the instances it is supposed to. However, at some point a problem occurs. The Force Encryption and Hide Instance labels _disappear_ (leaving blank spaces in the grid) from the interface, with the drop-down settings still visible. This seems to happen after installing an additional instance, although on one occasion it was after the 3rd was installed and on another occasion the 4th. Uninstalling the instances (even all of them) does not seem to help - only removing SQL Server 2005 completely and re-installing allowed the labels to re-appear.
Another concern is that after problem occurs, it appears that the settings are not being interpreted correctly. Even if the certificate is disabled for an instance, the message "The certificate was successfully loaded for encryption" appears, instead of the instance using a self-signed certificate. Additionally, on some occasions, the values for the Force Encryption and Hide Instance are swapped (or at least the values in the positions that used to be inline with the labels for these options).
As an additional note, various IIS Web Sites are configured on each of the IPs on the network interface. These are also using the same self-signed certification for SSL and are all using port 443, which none of the SQL server instances are configured to use.
Any feedback or suggestions on this would be appreciated. Thanks.
I am currently having publisher(database A), subscriber (database B) and distributor on the same instance for a test environment that is using a uni directional transactional replication. Now I need to setup another unidirectional transactional replication in the same test instance but for a different database. Publisher database is D and subcsirber database is E.
View 4 Replies View Related
I have a situation where I would like to set up one DB server instance for US and anther one for AUStralia. The Instance should share the same data base/hardsisk. One of the instances will be running in using US time zone and anothe one in Australia time zone.
There will be 2 Application instaces one poinint to each SQL Server instance. This applications does write into the database
So the underlying requirment is to have 2 database server running in differnet time zones but accessing the same disk/set of data
What is the best way to do this? Is it linked servers?Girish
I'm looking at installing 2008R2 and 2014 side by side, then using Mirroring to provide HA for the 2008R2 instance and AoHA for the 2014 instance. I'd be using the same two physical servers for both the Mirroring pair and the AoHA pair.
View 2 Replies View RelatedI am playing around in a test environment with SQL Server 2014. I have a question about the default location of the report server databases when you have multiple report server instances installed on one server.
I did a very simple install of SQL Server 2014 with the database and Reporting Services in Native Mode (install only) features selected. Accepting the default locations, I ended up with the following locations as you would expect:
C:Program FilesMicrosoft SQL ServerMSSQL12.MSSQLSERVER
C:Program FilesMicrosoft SQL ServerMSRS12.MSSQLSERVER
Running the Reporting Services Configuration Manager, I created the Report Server database. After creating the Report Server database, the related files will be located below in the SQL folder as I would expect.
C:Program FilesMicrosoft SQL ServerMSSQL12.MSSQLSERVERMSSQLDATA
Next I installed another instance, which I called Test, of SQL Server 2014 like I did above. I now have the following folder structure the Test instance as I expect.
C:Program FilesMicrosoft SQL ServerMSSQL12.TEST
C:Program FilesMicrosoft SQL ServerMSRS12.TEST
Running the Reporting Services Configuration Manager, I select the Test instance and create the Report Server Test instance database.
My first thought would be that the Test instance Report Server database would be in the following location:
C:Program FilesMicrosoft SQL ServerMSSQL12.TESTMSSQLDATA
Instead this database is located with the default instance Report Server database:
C:Program FilesMicrosoft SQL ServerMSSQL12.MSSQLSERVERMSSQLDATA
One of my varchar columns in a table has multiple key words enclosed in a pattern of special characters.
Eg: William Shakespeare was an English [##poet##], [##playwright##], and [##actor##], widely regarded as the greatest [##writer##] in the English language and the world's pre-eminent [##dramatist##]. He is often called England's national [##poet##] and the "Bard of Avon". His extant works, including some collaborations, consist of about 38 plays, 154 [##sonnets##], two long narrative [##poems##], and a few other [##verses##], of which the authorship of some is uncertain. His plays have been translated into every major living language and are performed more often than those of any other [##playwright##].
I need to write to query to find all distinct key words that are enclosed within [## and ##]. My query should yield the following results from the string in the example above
[##actor##]
[##dramatist##]
[##playwright##] -- 2 occurrances, but I need it only once in my result set
[##poems##]
[##poet##] -- 2 occurrances, but I need it only once in my result set
[##sonnets##]
[##verses##]
[##writer##]
I need to run this on a large table, so I am looking for the best possible way to minimize any performance issues.
Just give you sample code, I have provided below 2 separate snippets, one with table variable and another with temp table.
DECLARE @MyTable TABLE (MyString VARCHAR (8000))
INSERT @MyTable VALUES ('William Shakespeare was an English [##poet##], [##playwright##], and [##actor##], widely regarded as the greatest [##writer##] in the English language and the world''s pre-eminent [##dramatist##]. He is often called England''s national [##poet##] and the "Bard of Avon". His extant works, including some collaborations, consist of about 38 plays, 154 [##sonnets##], two long narrative [##poems##], and a few other [##verses##], of which the authorship of some is uncertain.
[code].....
We have a Silverlight based application which currently supports only one production version. Idea is to support three concurrent versions of the same application and user will switch to the newer versions based on their interest or they can still continue with the older version.
We still have to use the existing database for all these three versions.
What is the best way to architect this so that we can differentiate the code between the versions and still keep the data in sync and run all the versions in parallel.
Hi,
I've read the readme for the Service Pack 1 for Microsoft SQL Server 2005.
http://download.microsoft.com/download/b/d/1/bd1e0745-0e65-43a5-ac6a-f6173f58d80e/ReadmeSQL2005SP1.htm
But I'm not quite clear on what will happen if you currently have SQL Server Express 2005 installed with User Instances, and then you launch the installer for SP1.
Will it also update the User Instance? If so, how could I tell? When I go to the registry for the User Instance it has the older version value ie.
HKLMSOFTWAREMicrosoftMicrosoft SQL Server[instance name]MSSQLServerCurrentVersion = 9.00.1399.06
Shouldn't it be saying 9.00.2047.00?
Does this mean that I have to uninstall the User Instance before installing SP1?
Any help will be appreciated.
Thanks
Sam
I have noticed that analysis services has stopped on two instance on my server.For the first instance, I go to configuration manager and try to start the service I get the standard service did not respond in a timely fashion error, if I change the account that runs it from the domain user account to local system it starts up fine, but try changing it back I get the following WMI error: The server threw an exception. [0x80010105], I see this error in google but it always refers to the agent and not analysis services. In the application log, I see the following error...The service cannot be started: Message-Handling subsystem: The message manager for the defaul locale cannot be found. The locale will be changed to US English. File system error: The following error occurred during a file operation: Access is denied. But access denited to what? The services had been up and running for a while and nothing on the server has changed.
As on the second instance gives me the following error in the application log...The file <path>CryptKey.bin' could nor be opened. Please check the file for permissions or see if other applications locked it.
Then further up...The service cannot be started: Message-Handling subsystem: The message manager for the defaul locale cannot be found. The locale will be changed to US English. File system error: The following error occurred while opening the file <path>CryptKey.bin.
I should say the <path> part is me, saving typing not part of the error. And again, if I change the account running the service to local system if all changes and starts fine, but if I try to change it back I get WMI Error: The process terminated unexpectedly [0x8007042b]. If I hit 'apply' a second time I get another WMI Error, except this time it says 'The server threw an exception. [0x80010105].