Can I install either MSDE 2000 or SQL Server 2005 Express on a small business server 2003 to create a small web app ?Hmm - looks like SQL Server 2005 Express is supported on SBS2003 http://download.microsoft.com/download/f/1/0/f10c4f60-630e-4153-bd53-c3010e4c513b/RequirementsSQLEXP2005.htm Has anyone done this ? Are there any pitfuls?
Server 2000 installation inherit this instance name? Remember that We'll be using the SQL Server for several economy and warehouse application databases, so the "SHAREPOINT" instance name doesn't sit quite well with me Have anybody tried? Can I choose a new instance name or revert to "(default)" during the upgrade from MSDE to SQL 2000? Trond Hindenes NorwayI have full SQL, and two msde instances I memory throttled the msde's but other than that .. the server is running just fine. Allocated Memory Alert Revisited: http://msmvps.com/bradley/archive/2005/02/04/34984.aspx Allocated memory alert one more time: http://msmvps.com/bradley/archive/2005/05/22/48500.aspx Throttle them.. you'll be fine I would not rename instances because the
I have a Server running SBS2003 SP1 and the SQL.exe process grabs memory but does not seem to release it. It reminds me of the memory leak in SQL 7. I didn't install SQL 2k with the SBS install we aren't using it but MSDE is used by Exch, Sharepoint ect is there a fix Ihave installed SP4 for MSDE and it hasn't made a differance. Any help would be great.Hi Geoff. See this link for help with this. http://msmvps.com/bradley/archive/2005/02/04/34984.aspx It appears the MSDE/Monitoring and MSDE/MFW can run away with memory. HTH Wayne
$SHAREPOINT, MSSQL$WSUS, MSSQLServerADHelper, SQLAgent$SBSMONITORING, SQLAgent$SHAREPOINT, SQLAgent$WSUS are present, but I miss the SQL Server service itself. Thus it is not possible to use applications which need the SQL Server of MSDE. In fact, the icon which has normally a green arrow on the below right corner of the taskbar shows only an empty, white circle. How can I solve this problem? If I try to install MSDE, i receive a message that the installation was aborted . . . Your help will be highly appreciated! Thanks in advance! JacquesWhat is the error you get? As I don't have the MSDE.. I just have those instances as well.The problem is that I need the instance "MSSQLServer", which is NOT installed for whatever reason, and when I try to install it
user account is a valid login with the "System Administrator" role an has dbo access to all databases. The Windows Firewall allows port 1433 at the client and no firewall on the server. What else to check?The default for MSDE is to not listen to the network, only the local machine. This was in the Server Network Utility, yes? Has the MSDE instance been restarted since you enabled a network protocol? The Windows Firewall on a client is irrelevant, since it has no impact on outgoing connections. It would only be of interest if MSDE (or SQL) was installed on the workstation itself. Out of interest, where did you get the SQL client utilities from? They're not included with SBS2003 Standard, nor are you licenced to use them in an SBS2003 Standard environment.OK
to SQL and so on, but they all seem to result in having multiple instances of the SQL server process running. Is there a way to cleanly, organise all the databases in such a way that there is only ONE SQL server process running that serves all the tables required? i.e. A default install on SBS2003 premium with LiveCommunicationsServer would result in the following separate instances: 1. MSDE SHAREPOINT 2. MSDE SBSMONITORING 3. MSDE LIVECOMMUNICATIONS 4. SQL DEFAULT Assuming there is no live data that needs to be backed up or moved over, how could one merge all these into a single SQL instance, or set this up fresh in this way? The purpose of this is to use memory more efficiently, and make applying SQL patches easier as there's only 1 instance, not 4.You'd have
fail, and last night's backup failed because the vss could not create a shadow copy because of not having enough storage on the C: drive. The only software issue I have had recently is that auto accept agent has stopped processing items, and I can't figure out why. I don't know if this is related to the issue above, as it has existed for a few weeks and the perfromance issues just started a few days ago. Any and all suggestion are appreciated. TravisHi Travis: Two things stand out in your post. 1. "not enough storage on the C drive" I would be looking to see what is using 70 GB +/- of space, and what I could move off or delete. Windows really does not like under 10% free space, and is much happier with 25% plus. One of our more prolific
't give it an instance name. Now both of the standard SBS database engines are happy and everything works great. So my question is this, how do I uninstall that plain version of MSDE without killing the SBS ones that are already there? I'm considering just leaving it there because everything is happy but I really don't want something installed and running like a MSDE especially if it isn't being used. Thanks for any insight anyone might have on this. -AllistahLet me be clear that I only removed the registry entries for the new installed instance of MSDE. I left all of the MSSQL$SHAREPOINT and the SBSMONITORING ones alone. -AllistahAllistah, Is the mssql$sharepoint service running? If you look in the \program files\microsoft sql server\mssql$sharepoint\log\errorlog
are resolved in a timely manner. For urgent issues, you may want to contact Microsoft CSS directly. Please check http://support.microsoft.com for regional support phone numbers. Any input or comments in this thread are highly appreciated. ====================================================== This posting is provided "AS IS" with no warranties, and confers no rights.Nathan, I appreciate your response but I am a bit confussed. What is the difference between MSDE and WMSDE? I has been announced that MSDE is being replaced by SQL Server 2005 Express and MSDE will not longer be supported after 2007. Also I found a document that talks about Migrating from WMSDE to SQL Server but in reality what you are using with SharePoint is SQL Server 2000 Desktop Engine. It
it for monitoring. Usually an option to install to SQL Server is offered. If I have SBS 2003 Premium anyway, does it make sense for me to install SQL Server right from the start for all these applications even if I don't have a line-of-business application that requires SQL or should I just stay with separate MSDE instances for any application that needs a database?If you use any SharePoint (companyweb) document control features Please install SQL and Implement Full Text Search on your SharePoint site(companyweb) You will love it :)MSDE is only becoming popular because it's FREE (take note of the word).It does not come with administration tools like Query Analyzer and Enterprise Manager so you have to be very comfortable running administrative scripts in command line
log on the server is: The user SCR\vaguilar connected to port VPN6-4 has been disconnected because no network protocols were successfully negotiated. Also, a new development - Outlook via HTTP stopped working at the same time . I just found this out The other day.As you've found out Changing NICs can be Tricky Have you tried running the "Change Server IP Address " wizard? It sometimes fixes issues However There are some things I'd have to look at to troubleshoot everything Are you a MCP and can call for Critical Down Support? RussOkay .I'm at whits end now. I've tried everything relating to the Event Log Error, and nothing works. I have to get the remote e-mail up, but I'm not sure how that's going to come
for sbs monitoring thinking that I could use sql server for that purpose. It appears that sbs monitoring requires msde and has therefore stopped working. Is there a way to reinstall msde for sbs monitoring and get the sbs monitoring without reinstalling the whole sbs2003? The system is sbs2003 premium with both ISA & SQL Server installed.Hi John, Go to Add/remove Programs, SBS setup and reinstall the Monitoring part. Make sure you choose the 'maintenance mode.To be safe, I would remove Monitoring from SBS integrated setup. Then remove Program Files\Microsoft SQL Server\SBSMonitoring (assuming the SBSMonitoring MSDE is removed). Finally, run the setup to put Monitoring back. Ray Fong Microsoft SBS Product Support This posting is provided "AS IS" with no
do not want to install SQL Server 2000 on it. Im not all that familiar with Small Business Server 2003 but was told it contains a scaled down version of SQL Server to support the SharePoint services. Maybe MSDE, Im not sure. What Im trying to accomplish it to create a new database instance to track employee work hours. But I am not permitted to install any new software on the Small Business Server. Can I that will connect to this new SQL database. Not sure if you need to know that or not. Thanks for any help you can provide. -markIts called WMSDE and its like MSDE, but without the 2GB limit (plus it doesn't allow external connections). I have to point out that this is not an "SBS thing", but it comes with Sharepoint even in plain vanilla Windows server (as long as you
Another admin uninstalled MSDE from our SBS 2003 server. Ouch! In order to get it back should I re-install MSDE be downloading it and re-installing or would it be better to run the SBS 2003 setup to re-install the component? I had created another STS website for their Intranet data and converted it to SQL 2000 but after MSDE was uninstalled, the site was no longer available. Why would the site not be available when it was converted to SQL from MSDE? Any help would be greatly appreciated. TIA, Kevin.Hi Kevin, Rerun the SBS setup as the Monitoring part is using MSDE too.
I agree with Dave that you can either use a script to stop the service or temporary skip backing up the database folder when configuring the backup. As an example, the ISA 2004 logging MSDE database is stored at C:\Program Files\Microsoft SQL Server\MSSQL$MSFW\Data If you have further questions, please feel free to post back. Bill Peng MCSE 2000, MCDBA, CCNP, CCDA Microsoft CSS Online Newsgroup Support Get Secure! - www.microsoft.com/security ===================================================== The public newsgroup only focuses on SBS related technical issues, for other Microsoft products, we recommend you to post to appropriate newsgroup to get most qualified responses. http://www.microsoft.com/communities/newsgroups/en-us/default.aspx When
2003 network using http://server/conncetcomputer. I am going to use a restore point prior to connecting to SBS 2003 and see if I am able to connect using connectcomputer. If anyone has any other thoughts or know of a KB about this issue, please post them. Thank you, Ed Podowskijust as a bit of further when I was trying this with 64 bit Vista, I was getting RPC issues, so it had to be driver issues for the 64 bit. 32bit Vista connected just fine.Hello Cris, I want to post this, so others could benefit. You were right it was the drivers. I used a restore point which was before I joined the domain and then uninstalled any programs which were unnecessary. I also found several 32 and 64 bit version of the same program. Although I never really isolated the driver causing the
patches on instance SHAREPOINT, the error code returned was: 10 Any Ideas? ChipI have two SBS 2003 Premium production servers with the same problem. And have been asking off and on for a solution, but haven't got one. I built a SBS 2003 test server and was able to apply the SQL/MSDE hot fix. So it is definetely a Sharepoint issue. DB (Baseline SBS instances) and Instance did not different major build of not match. This was higher than the return error code log file for instance SHAREPOINT,Hi Michael and Chip, This is an expected message and is nothing to worry about - the hotfix is still applying correctly. The message is saying that the sqlservr.exe file is a newer version
was already installed (for monitoring purposes) by default, but I cannot work out which services to start that would allow me to connect to the server. Do I have to install MSDE from a MS download? Will I be able to run MSDE on the SBS so that clients can access the DB? Or should I be doing something different. Thanks for your help Stuart PS I seem to recall SQL express being the replacement for MSDE, have I got that wrong as well?Yes SQL 2005 Express replaces MSDE, Look for the SQL Express services. MarkMark, thanks for that confirmation. Looking at the services I cannot see anything that looks appropriate. Do I have to download and install it? Will there be any conflict with the existing setup (which is a standard sbs 2003 fully patched). I'd hate to "break"
I was told, and I'm verifing first, that the version of MSDE within SBS 2003 Standard Edition has issues where a backup of MSDE will work but you can't restore it?Absolutely wrong. Here's a link to a Technet Chat on SBS Backup/Restore: http://www.microsoft.com/technet/community/chats/trans/sbs/sbs0630.mspx In it (about 3/4 of the way down), a question was asked how can one "test" or "verify" an MSDE backup.
database' (default) to 'File'. 6) Switch to the 'Fields' tab, click 'Select All', and then click OK. 7) In the 'Task Pane', click 'Configure Web Proxy Logging' under 'Logging Tasks', and then switch the 'log storage format' from 'MSDE database' (default) to 'File'. 8) Switch to the 'Fields' tab, click 'Select All', and then click OK. 9) Click 'Apply' to save changes and update the configuration. 10) Temporarily disable the Firewall service. To do that, please click Monitoring | Services tab, and then right click 'Microsoft Firewall' to choose 'Stop'
two of our clients. When \\tmfm1 is opened in explorer, the regular shares are not visible. Instead "Users Shared Folders" and "Users" display as the only 2 shares (16+ shares should be available). The problem can be fixed by typing in the fully qualified domain name, tmfm1.tmfm.local. Once this is done, all shares are visible on the two machines that were having issues. To make matters worse, at times the troubled machines will actually start seeing the shares temporarily with just \\tmfm1. We have checked ip info on the client machines, and everything is as it should be. We have tried deleting the WINS entries on the server for the troubled machines. One of the machines started resolving after this, but then stopped after sometime. Any ideas? Thank You.Please post
, I'd do so. How to obtain and install SQL Server 2000 Desktop Engine (MSDE 2000) http://support.microsoft.com/kb/324998/en-us Or get SQL Express from http://msdn.microsoft.com/vstudio/express/sql/register/default.aspx. There'll be an install guide somewhere along in there with the download.Thanks for the quick response. Will installing 2005 Express affect the existing MSDE at all?It shouldn't. I have not installed Express on an SBS, but I have a member server with several MSDE databases and one Express database - no issues at all. That management tool for Express - the name escapes me - will manage MSDE databases as well. However, the SharePoint and other databases that ship with SBS are a special version that can't be managed like plain vanilla
not has been upgraded. When I ran SP3 (for the new instance) I could choose for an instance SHAREPOINT (which was not available, as previouse mentioned, now it is) ???? Then I de-installed SQL2000. I installed it again and came to the option to choose for an new instance or .. and now is the upgrade-option greyed out ??? How come ?? MSDE has been still installed, why is the option disabled ? regards, Ger.Hi Ger, Thanks for your post. standard edition but not the SBS server 2003. Is it correct? However, based on my knowledge, the PREMIUMINSTALLSTEPS.htm file only exist in the SBS premium disc. So, what version of SQL server are your try to install? If you have any concern on this thread, I am glad to be of further assistance. We look forward to hearing from you. Jerry Zhao
How can I tell if I have MSDE SP4 installed?on the system tray, Right click on the SQL server and select about. It should tell you what version you are running.Are you talking about the Service Manager? If so, it only says 8.00.2039Sean, 8.00.2039 is the build number for SP4. HOW TO: identify your SQL Server Service Pack version and edition http://support.microsoft.com/default.aspx?scid=kb;en-us;321185 FYI.. the build number is also in the errorlog file in
Right click on Service Manager, then click Delete To remove the icon fromSystray: 1. Right click the icon in Systray 2. Click Exit This only occur on the Standard version of SBS 2003 with only MSDE installed, if you are using the SQL server 2000 it will not occur, I am sorry for any inconvenience in this issue. More info: =========== 829358 Critical update for SQL Server 2000 Desktop Engine (Windows) . Charles Yang (MSFT) Microsoft CSS Online Newsgroup Support Get Secure! - www.microsoft.com/security ====================================================== This newsgroup only focuses on SBS technical issues. If you have issues regarding other Microsoft products, you'd better post in the corresponding newsgroups so that they can be resolved in an efficient and timely
that houses the data. All he did was make it accessible and searchable by running the database index from his workstation. Hope I havent lost anyone yet anyway, we want to move that database index from MSDE on his workstation to SQL on our SBS 2003 server. The data will stay where it is on the other, is there a way to move the database index? Thanks in advance, KenIf the data is stored in a SQL Server (or MSDE) database, then the "index" will be part of the table(s) definition, and stored on the database server.Steve, the data is stored on a Novell File server, not in the MSDE database. I believe the only thing the MSDE database stores is the database index, which contains the links to the data files individually as well as a key word search query utility.