I have a Windows 2003 Server running IIS 6.0 and SQL Server 2005. I have just (Today) deployed the first ASP.NET application (developed in Visual Studio 2003 and, as such, dependent on .NET Framework 1.1) on this server and am getting HTTP Error 403 (You are not authorized to view this page). This ASP.NET application runs fine on another server that is configured with the OS=Windows Server 2003, IIS=6.0 but without SQL Server 2005 and without the .NET Framework version 2.0. I found in the IIS Application configuration (on the troublesome site) that my app (in the Default Web Site folder) was pointing to the version 2.0 aspnet_isapi.dll. All efforts to use aspnet_regiis to "re-align" my app with version 1.1 have been fruitless to eliminate the HTTP Error 403. I granted the NETWORK SERVICE account privledges to the wwwroot folder. At this point, I don't know if I have a Framework error or a privileges problem.
I am trying to migrate from my current system, where I do merge replication from Windows Mobile devices running SQL Server CE 2.0 to a central database running SQL Server 2000 sp3a. I want eventually to move to a system running SQL Server 2005 CE replicating to a SQL Server 2005 back-end. But the transition will need to be gradual, and I may have to support both systems for a while until I can convert all clients from the old system to the new. I also need to do thorough testing.
So ... I'm trying to set up a test environment giving me the maximum possible flexibility to do my testing. Ideally, I'd like to set up SQL Server 2000 and SQL Server 2005 on a side-by-side basis, in a manner that would potentially allow mobile devices running both SQL Server CE 2.0 and SQL Server 2005 CE to sync with either back-end server.
Can someone provide me with guidance as what is possible to set up here? I know that SQL Server 2000 and 2005 can be installed side-by-side on the same server. It also appears that you can set up SQL Server 2000 so that EITHER SQL Server CE 2.0 OR SQL Server 2005 CE can sync with SQL Server 2000 (see www.microsoft.com/sql/editions/sqlmobile/connectivity-tools.mspx), but I don't know if it's possible for BOTH SQL Server CE 2.0 AND SQL Server 2005 CE to sync to the same SQL Server 2000. As for SQL Server 2005 ... it appears to be possible to set up SQL Server 2005 so that BOTH SQL Server CE 2.0 devices AND SQL Server 2005 CE devices can sync to the same SQL Server 2005 (see web page cited above). However, I don't know if it's possible to set up a SQL Server 2005 server installation in this manner while at the same time having a side-by-side SQL Server 2000 installation supporting any level of mobile merge replication.
I will soon be embarking on an upgrade of a transaction replicated database (Push) from 2005 to 2012 SP2.The publisher, distributor and subscriber are 3 separate machines.There databases will be detached, MDF and LDF will be copied across. Once attached, replication will be set up from scratch.
The name of the new servers are NOT the same as the existing ones.Should I completely remove transaction replication user the wizard and unticking the DB from being a database for transactional replication or just stop the log reader agent?How can I make sure the last of the transactions have gone across before I detach?Should I detach the subscriber first or the publication? Does it even matter?
Is there a better way of moving across the databases? I for one would have preferred to backup (.bak) then restore on the other side. I'd love to hear opinions on this as well.
I am working to create a phone list that will contain Last Name, First Name, and Phone Number sorted by last name. For printing purposes I would like to have three columns of data instead of the standard of one column.
Is it possible to create a query to present data in three columns showing the data side by side?
I have downloaded and installed VS C# Express Orcas beta 1. It appears that Express editons ov VS can only connect to SQL2005 Express and not to a high end edition which I have on my computer. In one of the Orcas forums, it was suggested that I can install SQL2005 Express side by side my high end SQL 2005. To play it safe, I wanted to get a confirmation from this forum before I do that. Is a side-by-side installation ok? thanks.
would like to know if it's possible to install SQL Server Failover cluster instance with shared storage along with standalone installation with Always on ( always on uses WSFC underneath).
Here is my case: I've a server running Windows server 2003 edition and SQL2000. I've installed SQL2005 using the side-by-side method as described by MSFT docs. I've then copied the mdf & ldf files to new locations and attached the db in SQL 2005 management studio. Every thing fine. Next, I've migrated the DTSs using the DTS migration wizard. After this step I have some bad warnings in windows:
When I restart the server I get the following message: "mmc.exe Microsoft Management Console encountered a problem and needed to close". Furthermore: I can't start the old SQL enterprise manager. It shows another error "mmc.exe - Entry point Not Found" and closes it self.
The MSFT support page on this error relates it to Windows XP but my system is running Windows server....
Any one has any idea why this is happening? Any suggested course of action?
My system is already installed with SQL server 2000 . Is it possible for me to install SQL server 2005 BETA CTP in the same machine and run both side by side.
I was trying to do something like puting two tables side-by-side inside a list, and list itself is grouped by a field. But for some reason, two tables are not organzied pararally even there is no page break inserted.
I need to migrate from sql 2000 to 2005 and in place upgrade is not possible. I can move the databases, logins but can some one help me to migrate sqlmaint plans and dts packages to 2005.
We have some developers who manage SQL2000 servers from their WinXP workstations using Enterprise Manager. We have now rolled out our first SQL Server 2005.
Can we install the SQL2005 Management Studio side-by-side with Enterprise Manager on these WinXP workstations?
If not, what are most people doing in these cases?
I've recently done a side by side upgrade of a mssql 2000 to mssql 2005 instance. I'm having problems with 1 login that I've been told had a password that was only 3 characters in length. They don't seem to be able to log in with it. I get an error with a state of 8 meaning it's the password. Is there an issue with migrating the id and password as is into the 2005 instance? None of the other ids are having the problem, they all seem to work and have longer passwords. Any help is appreciated.
I plan to upgrade my server to SQL 2005. It is a rather old machine, but still ok with the recommended hardware requirements.
It runs Windows 2000 (SBS) server, which is also a PDC, DHCP, DNS, Exchange server (I stop here but the list is long), with SQL Server 2000 Standard Edition (one single named instance). Everything localized (Italian).
I upgraded the database in a development machine and it works perfectly.
I installed SQL 2005 Standard Edition (English locale) on the server (default instance, MSSQLSERVER), and I have run in a lot of troubles.
The problem seems to reside in the TCPIP network protocols. If I enable TCPIP in the 2005 Server Configuration Manager, the new instance (MSSQLSERVER) does not start (this prevented me from upgrading to SP1 until I realized the cause, disabled TCPIP protocol and was finally able to update).
If I understand correctly, the problem is that both instances, the old 2000 one and the new one, try to listen to 1433 port. I changed manually the port to 1434 in the Server Configuration Manager. The result is that both SQL servers work, but none is working ok. I have several applications accessing the server. The asp application works. The .NET aspx one doesn't.
A tipical error I get is:
Codice evento: 3005 Messaggio evento: Eccezione non gestita. (Unhandled exception) Ora evento: 04/05/2006 13.42.26 Ora evento (UTC): 04/05/2006 11.42.26 ID evento: 7c2749235b7d4c578591871217f74046 Sequenza evento: 175 Occorrenza evento: 24 Codice dettagli evento: 0 Informazioni applicazione:
Dominio applicazione: /LM/W3SVC/1/Root/intranet-1-127912101551093750 Livello di attendibilità : Full Percorso virtuale applicazione: /intranet Percorso applicazione: F:Inetpubwwwrootintranet Nome computer: IQ Informazioni processo: ID processo: 684 Nome processo: aspnet_wp.exe Nome account: mycompanyIWAM_IQ Informazioni eccezione: Tipo di eccezione: SqlException Messaggio eccezione: Login failed for user 'mycompanystefania'. Informazioni richiesta: URL richiesta: http://intranet/intranet/articoli/venditeProd.aspx?Codice=SOL T1 Percorso richiesta: /intranet/articoli/venditeProd.aspx Indirizzo host utente: 10.0.0.127 Utente: mycompanystefania Autenticazione: True Tipo di autenticazione: NTLM Nome account thread: mycompanyIWAM_IQ Informazioni thread: ID thread: 1 Nome account thread: mycompanyIWAM_IQ Rappresentazione: True Analisi dello stack: in System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) in System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) in System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) in System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) in System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) in System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) in System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) in System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) in System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) in System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) in System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) in System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) in System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) in System.Data.SqlClient.SqlConnection.Open() in intranet.Global.Session_Start(Object sender, EventArgs e) in System.Web.SessionState.SessionStateModule.RaiseOnStart(EventArgs e) in System.Web.SessionState.SessionStateModule.CompleteAcquireState() in System.Web.SessionState.SessionStateModule.BeginAcquireState(Object source, EventArgs e, AsyncCallback cb, Object extraData) in System.Web.HttpApplication.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() in System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
I also tried to use named pipes on the 2005, but I was unable to access the SQL 2005 server instance from a network computer running the Management Studio. I need to have the new SQL server working besides the old one, for a short period, to evaluate in the production environment if the legacy hardware is actually ok to support it. Any ideas?
I'm rather new at working with SQL Server. I've installed 2005 onto my PC and I have 7.0 already. What I want to know is how do I import my packages from 7.0 into 2005?
We are testing our SQL 2000 db on a test box in which we loaded SQL 2000 first and then installed SQL Server 2005 Enterprise Trial edition side by side. I am trying to execute new functions in SQL 2005 against the Northwind db to test and these functions are not recognized. What am I missing?
I was using a single data table to contain my assortment of fields, but one of the text boxes often has to grow vertically, skewing the layout on the fields to the right of it. So, I moved those other fields to a data list right beside the table. It seemed to work perfectly, so I deployed it to our development server and tested it. When rendered from the server, the list gets bumped down to below the table.
So, after doing some research, I stuck the list into a rectangle and tried different things, like making sure the top of the rectangle was above the top of the table, etc. However, one or the other data region always gets bumped down to below the other--I can't get them to stay side-by-side when run from the SSRS server.
The final frustration is that when I print from the malformed 'preview' on the server, it comes out correctly on the printer! In other words, it looks different on the printer (correct) from how it looked when I hit print (incorrect) in the browser.
Apologies if this is a newbie question, but I'm stuck.
Hi, I work with very sensitive data and do not want to do any in-place upgrades. Does anyone know of the risks (or some documentation) involved with an in-place besides the rollback. I would prefer only to do only side by side upgrades.
I was running sql 2000 for months before the release of sql 2005. I cannot upgrade any old databases on my test server but new applications are to be designed for sql 2005 database.
I installed sql 2005 onto my server but for some reason I cannot get the enterpise manager to start (when I doubleclick C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe the splash screen displays for a fraction of a second and disappears).
Can I run 2000 and 2005 side by side? How can I get the enterprise manager to start?
Have an asp.net 2.0 application that I want to enable a "demo" version of with the required tables. The tables currently exist in SQL2000Dev on a server. I have installed SQLEXP on a clean box and restored the database to it no problem. Now I want to install SQLEXP on my dev pc side-by-side with the SQLDEV instance. I could not find any reference to this ability other than some warnings about the pre-release versions. Can it be done safely?
I have SQL Express 2005 with Advanced Services on a development box that I also want to have installed side-by-side with SQL Server 2005 Standard Edition so I can develop apps using either edition based on the features I need (or don't need). From what I understand from sifting through other posts is that side-by-side installs of these two editions is supported and I should setup a named instance for each edition (SQLEXPRESS for the express edition and MSSQLSERVER for the standard edition). Is this setup accurate or is there another/better way?
Also, does anybody know if side-by-side installations of Reporting Services is also supported? If I install SQL Server 2005 Standard Edition with Reporting Services, will there be two different report servers running in IIS? Since there are different features in Reporting Services between the two editions, I'm not sure how side-by-side installations will effect one another.