SQL Server 2000 Standard Edition - Distribution Agent Dieing When Network Connection Fails
May 21, 2007
Hi,
We have replication setup on a sql server 2000. We encountered issue that the distribution agent goes down (distrib.exe stop running) in the event of network connection broken. We would like to know:
is this the expected result that the distribution agent will go down in the event of communication failure between the distribution server and subscriber server?
if not, is there a way to programmatically control and restart the agent?
Is there any sp in SQL server which can monitor the replication communication error message?
is there any sp in SQL server which can be run to restart the agent?
For the best practice, what do you think we can do to achieve an €˜event-driven€™ kind of mechanism so when an communication breaks, the agent can be restarted by the triggered event (or at least a simple way to automatically restart)?
We are trying to install the Standard Edition of SQL Server 2005. We already have SQL Express installed. Standard won't install and Express won't uninstall.
We have tried every suggestion we can find and some we made up. When we try to install Standard, we get to the bit where you choose what you want to install and the only thing available is workstation components.
There are so many cases of this on the Internat that I can't believe MS have not solved the issue. And I am stunned that they want to charge us more money to talk to us about how to fix something we just paid them an arm and a leg for!
What do I need to tell you to get some idea of where to go next with this?
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.
I did a small package with only one ODBC connection (Merant 3.70 32-Bit Progess). This package runs well in Visual Studio and fails when runs by SQL Server Agent.
Configuration:
SQL Server Agent on a 32Bit server.
The ODBC connection configuration in available on System DSN on this server.
The user of Server Agent have full access (Admin).
Connect Manager Provider: ".Net ProvidersOdbc Data Provider"
SQL Server version: 9.0.3042
Error Message:
Executed as user: TEKCON cadmin. ...ion 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 16:50:33 Error: 2007-06-11 16:50:33.62 Code: 0xC0047062 Source: Data Flow Task DataReader Source [1] Description: System.Data.Odbc.OdbcException: ERROR [HYC00] [MERANT][ODBC PROGRESS driver]Optional feature not implemented. ERROR [HY000] [MERANT][ODBC PROGRESS driver]msgOpen: unable to open message file: PROMSGS ERROR [IM006] [MERANT][ODBC PROGRESS driver]Driver's SQLSetConnectAttr failed. ERROR [HYC00] [MERANT][ODBC PROGRESS driver]Optional feature not implemented. ERROR [HY000] [MERANT][ODBC PROGRESS driver]msgOpen: unable to open message file: PROMSGS ERROR [IM006] [MERANT][ODBC PROGRESS driver]Driver's SQLSetConnectAttr failed. at System.Data.Odbc.OdbcConnection.HandleError(OdbcHandle hrHandle, RetCode retcode) at System.Data.Odbc.OdbcConnectionHandle..ctor(OdbcConnection connection, OdbcCon... The package execution fa... The step failed.
I created a .bat file with this instruction and It's run well:
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.
I am trying to install SQL Server 2005 onto Windows Server 2003 Small Business Edition. Previously SQL Server 2000 from the SBE disk was installed, automatic updates are enabled.
I have selected the default instance and everything I try results in the error:
An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.
Log file says;
-------------------------------------------------------------------------------- Machine : ISAINTERNET Product : Microsoft SQL Server 2005 Product Version : 9.00.1399.06 Install : Failed Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0002_ISAINTERNET_SQL.log Last Action : DetectInstanceClash Error String : An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name. Error Number : 28086 --------------------------------------------------------------------------------
I am running Win2k Professional version SP2. I tried to install the SQL Server 2000 Standard Edition, I got error message said " MS Sql Server 2000 Standard Edition server component is not supported on this operating system. Only client components will be available for installation."
I am currently trying to migrate to a new computer. My old computer (Box 1) has Windows 2000 Ver 5.0 SP4 as an operating system. My new computer (Box 2) has Windows XP Professional Ver 5.1 SP2 as an operating system.
Currently, I have Microsoft SQL Server 2000 running on Box 1. When I used the CD to install the software on Box 2, it will not allow a full install. Just the Client portion. The exact message I get is "Microsoft SQL Server 2000 Standard Edition is not supported on this operating system. Only client components will be available for installation.
How in the world do I get this software to install on Box 2? I've seen and downloaded, the service packs but I don't know where to go from there.
Thanks in advance for any help that you can provide.
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.
When i install sql server 2000 i have a message " Microsoft SQL Server 2000 Standard Edition Server Component is not supported on this operating system only client components will be available for installation"
Hence I cannot install properly. I installed only the client componets. Thereafter when I went through Enterprise Manager and tried to establish a connection, I failed. It said server does not exist.
What to do now?
I found out that if one has sql server 2000 standard editon the prerequisties are Microsoft Windows NT Server 4.0 with Service Pack 5 or later, Windows NT Server 4.0 Enterprise Edition with Service Pack 5 or later, Windows 2000 Server, Windows 2000 Advanced Server, or Windows 2000 Datacenter Server.
I have windows xp professional version on which i am installing sql server standard edition. Which of the above exists in my OS. Or which should I download.
Hi, One of our main servers running on SQL Server 2000 Enterprise edition which has transactional replications on it which replicates to other servers running on the SQL Server 2000 Enterprise edition as well.
Due to Hardware problems the server is being migrated to a new machine but the client has installed SQL Server 2000 standard edition on the new machine.
We will be using a two processor cpu with 4GB RAM and we are also not planning about clustering. Is there any problem if i migrate the server in Standard Edition will the replications work properly between Standard and Enterprise editions.
What other complications can be there if i switch over to standard edition from enterprise edition
I am getting the following warning on a Live SQL 2000 system: This SQL Server has been optimized for 8 concurrent queries. This limit has been exceeded by 1 queries and performance may be adversely affected. Reading about this error I realised that, by mistake, the version installed is a personal edition instead of the standard edition. I am thinking to backup the databases, uninstall SQL 2000 Personal edition, install Standard edition and restore the databases back. OR, disconnect the databases, uninstall the current version, install the standard version and re-connect the databases. I haven't found within Microsoft any advice how to upgrade the personal version to the standard edition. Because it is a live system, I would not like to mess the system up. Can you please advice? Many thanks
When trying to install SQL 2005, I keep getting the foll. error:
Error 1706. Setup cannot find the required files. Check your connection to the network or CD-Rom drive. For other potential soltions to this problem, see C:Program ....1033setup.chm
I have tried using two different DVDs, and also downloaded SQL 2005 from msdn, but none of them work.
Hi all, I have a production website at Godaddy and an ASP.net 2.0 page that successfull connects to a SQL 2005 instance provided by Godaddy using SQL authentication(User ID/Password). The Godaddy database has become too small (200MB limit) and the plan is to use the SQL Server 2005 standard edition at my office. In other words, I want to host my own SQL server and keep the front-end at Godaddy. The ASP.net test page at Godaddy generates the basic connection errors when attempting to connect to my SQL server at the office. This error has several variations depending on how the connection string is configured: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) In this case the connection string is: Data Source=xxx.xxx.xx.xxx,1433; Network Library=DBMSSOCN; Initial Catalog=Test; User ID=xxx; Password=xxx" I've embedded this connection string directly into the ASP.net test page in order to make this page independent of the web.config file. My MS SQL server is on a Small Bussiness Server 2003 with Sharepoint and Remote Workplace running, and this machine is behind a linksys router, and Routing and Remote Access is running in place of windows firewall. I've openned ports TCP 1433 and UDP 1434 on the router and Routing and Remote Access. Telnet xxx.xxx.xxx.xxxx 1433 connects successfull, and the SQL log shows listening on 1433. I don't know if telnet is telling me that there is successful connection to the port on the router, or if it makes it all the way to the SQL server. The SQL server is running the default instance MSSQLSERVER. Locally, I am able to connect using SQL 2005 Studio, and I am able to confirm this activity in the SQL log. Since I've openned port 1433, I also see numerous dictionary attacks in the SQL Log. Based on this, remote connectivity is there. The strange observation is that the SQL log shows no sign of a connection attempt from the ASP.net page. The connection appears to be failing before it reaches the SQL server. I've openned ports in the Linksys router and the NAT/Firewall the same way I've openned them for Sharepoint and Remote Workplace. I also found that when I move the ASP.net test page to another ISP, then the SQL connection that worked from the Godaddy website, is no longer able to connect. An explanation of this would also be very helpful to me. Is there something that needs to be configured to expose the SQL server to ASP.net pages that is different from remote access? Does IIS need to somehow be involved? Is there something in Small Business Server 2003 that could be interferring with ASP.net page requests to the SQL server? Do I need to run my machine as a web server to make this work? Any help with this configuration would be greatly appreciated.
I€™ve developed a BI system using the SQL Server 2005 Developer€™s Edition.
SSAS, SSIS and SSRS have been added to a SQL Server 2005 Standard Edition Server in preparation for delivering the developed database to this live environment.
So I am able to connect directly to the Database Engine, SSAS, SSIS and SSRS successfully from the actual SQL Server 2005 Standard Edition box which is sat on a Windows 2003 Server operating system.
However when I launch SQL Server Management Studio from a desk top PC which is connected to the SQL Server Standard Edition box I can€™t connect to either SSIS or SSRS, however I can connect to the Database Engine and it also seems that I can connect to SSAS OK.
I am using Windows Authentication where the I used a SQL Server account which exists with €œsysadmin€? permissions and this SQL Server account has the same login name as the Windows Server 2003 desktop login.
We got SQL Server 2000 Standard Edition SP3 running on Windows 2003 Standard Edition server.
Now, we would like to apply windows 2003 SP2 to the Operating System.
We are concerned that whether windows 2003 SP2 is compatible with SQL server 2000 (SP3)?
I was looking at the application compatibility chart for Windows 2003 SP2.Among them Microsoft SQL Server Standard (2000) was listed but with no Service pack details. And also does Standard means standard edition there?
My Question - Is windows 2003 server SP2 compatible with SQL Server 2000 (SP3) Standard Edition? And what if I plan to apply SP4 to Sql Server ?
I have a simple SSIS package that reads a flat file and copies it into a SQL Server table.
When the flat fiel is on the C drive I have no problem runnign this package from SQL Server Agent, but as soon as I update the path to a network location the package only works when I run it manually, but fails when is executed via the SQL Server agent job.
The error says "cannot open the datafile", while the datafile location is valid.
Is this a kind of limitation of a SQL Server Agent that only local files are allowed to be processed?
SQL Agent will not successfully execute my package as a job. Bids executes the package correctly as well as when I run the package manually (right click, run package) through SQL Server Management Studio. This is a permissions issue with the flat file any help will be much appreciated.Background Information:OS: SQL 2005 on Windows Server 2003Flat File Connection: \servernamefolderfile.txt (If I change the flat file location to a local file the package will run as a job successfully)Domain: The package is running on a Windows machine that is not on any domain. The network location is a Windows machine on a domain.Security: The network location folder (\servernamefolderfile.txt) has no security, namely anyone can access any file to read/write/delete/etc. I can manually add and delete files as well as add and delete files when the package runs through BIDS or when I manually run it through management studio.Permissions: I have created a login, security credential, and proxy which I am using to run the package. The security credential is tied to the Administrator account on the local machine. Error Message: Executed as user: COMPUTER-NAMEAdministrator. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 12:05:37 PM Error: 2007-06-19 12:05:39.25 Code: 0xC001401E Source: DataTransfer Connection manager "FILECONNECTION.FileConnection" Description: The file name "\servernamefolderflatfile.txt" specified in the connection was not valid. End Error Error: 2007-06-19 12:05:39.25 Code: 0xC001401D Source: DataTransfer Description: Connection "FILECONNECTION.FileConnection" failed validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 12:05:37 PM Finished: 12:05:40 PM Elapsed: 2.297 seconds. The package execution failed. The step failed. (note: I replaced the fileconnection strings with FILECONNECTION and the serverpath with "servernamefolder" for privacy reasons. Any help would be greatly appreciated. This is some sort of security issue with SQL Agent. But, the error claims that the user is running as localmachineAdministrator. Isn't this how the package would run if I manually execute it?
Hello!I would like to change the SQL server 2000 from Standard version toDevelopment edition. I have two database running on this server, bothreplicated, with few jobs, etc ... Can you recommend the easiest way to dothis? I heard, it would be as easy as, detaching the databases, deletingcurrent SQL software, installing different one, and attaching the olddatabases back. I doubt that is true, so that's why I'm asking here for anyreal-life instructions.Thanks for your input!Kind regards,Dejan--
I will be installing a new, SBS2003 R2 server that comes with SQL 2005 Workgroup Edition. We currently have a SQL 2000 Standard server. Can I installed SQL2000 Standard on SBS2003 R2? The reason for this is that we're not ready to migrate to SQL2005 and we need to continue running SQL2000.
I am experiencing an issue with SQL Server 2000 Maintenance Plan. DB Backup job fails to delete old backup files from the file server (I am backing up to the network share - actually, a DFS). Backup part of the maintenance plan/job succeeds, but then cleanup part fails.
I made sure that service account under which SQL Server Agent is running, has sufficient privileges over the network share by logging in and successfully deleting files in question.
I was not able to locate any log entries either on the SQL Server machine or on the file server machine that would indicate the root of the problem. Even though I turned on auditing for Delete operations for the destination folder, its subfolders and files, I could not find anything in the Security event log.
I would appreciate any ideas on how to troubleshoot and correct this problem.
I have been tasked with upgrading around 150 SQL Server 2000 DTS packages to SSIS in SQL Server 2005 standard edition. I made a backup of the 2000 database upon which the DTS packages operate and restored it to the SQL 2005 server. So far, so good. I have the database in place. Now I need to get the DTS packages themselves into the SLQ 2005 server. I think I need to check my install and make sure that I have the SQL Server 2000 DTS services installed on the SQL 2005 server. I can do that.
However, I wonder what would be the most effective way to physically get the packages from the SQL 2000 server to the SQL 2005 server. Should I use structured storage files? If so, how do I go about opening them in SQL 2005 in order to save them to SQL server 2005?
I should mention that these packages make heavy use of ActiveX scripting so I am looking at rewriting them from scratch to be SSIS packages. I just need the packages on the SQL Server 2005 box so I can make sure I am creating exactly the same functionality in 2005 as existed in SQL server 2000. Each DTS 2000 individual package tends to be fairly simple and I think I can greatly improve the process by consolidating them.
Hi -I have istalled sql server 2005 standard edition , I want to install sql server 2005 enterprise edition on the same machine. Is it possible? I have Microsoft windows server 2003 SP2 and 1GB RAM. I want to use partition function with the enterprise edition, will the trial version of sql server work for me? -If I have already created a database and tables using the standard edition, will I be able to access and use the database using the installed trial version or will I have to start a fresh creating a new database? - Is it possible to access the same database with any of the installed versions?
BTW, I am prety new to sql server and databases , I am trying to learn by myself
Hello!M a newbie.. I just want to know, that wots the difference b/w SQL Server Standard Edition and Express Edition.?And can I use Visual Studio 2005 (Professional Edition) with SQL Server Express Edition.?
Dear All,We have a database which contains many tables which have millions ofrecords. When We attach the database with MS SQL Server 2005 StandardEdition Server and run some queries (having joins, filters etc.) thenthey take very long time to execute while when We execute same querieson Enterprise Edition then they run 10 times faster than on standardedition.Our database does not use any features which are present in EnterpriseEdition and not present in Standard Edition. We want to know what arethe differences between Standard Edition and Enterprise Edition forperformance. Why should we go for Enterprise Edition when StandardEdition has all the features required.We are presently using evaluation versions of SQL Server 2005 Standardand Enterprise Editions.Thanks and regards,Nishant Sainihttp://www.simplyjava.com
I am attempting to upgrade a 2005 Standard Edtion to Enterprise Edition. This is a default instance. All components are upgraded successfully except the Database Engine. I receive the following error:
SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]The certificate cannot be dropped because one or more entities are either signed or encrypted using it.. To continue, correct the problem, and then run SQL Server Setup again.
This installation does not have encryption enabled, so I do not undersand the error or how to correct it.
After rebooting the SQL instance appears to be upgraded to Enterprise, but it cannot be upgraded to SP2.
I'd like to upgrade from my current SQL Server version: 09.00.3042 (Workgroup edition that comes with SBS upgrade) to the standard edition that I've just purchased. I've attempted to run setup.exe SKUUPGRADE=1 from the command prompt and it just tells me that there's nothing new to install.
I don't really want to uninstall the current installation just to do something that shouldn't be complicated to do, upgrading software versions should not be a difficult process.
As an ISV, I want to certify my product on Standard Edition. I am using Developer Edition everywhere. Is there a way I can do the certification using the Developer Edition, or do I need to obtain/purchase a copy of the Standard Edition?
