Hi all, I'm trying to install MSDE in silent mode and without using a .ini file (on a machine with windows 2000 server and SQL 2000 already insatalled). At the end of the installation, the machine reboot automatically, but I need to stop this reboot. Someone can help me? Thanks all
Have a production server, 12 Enterprise, and we are adding a new app to an existing instance. Next app needs SSRS and that was not put in the install request a year ago for the instance.
I do not think a reboot is required but have been wrong before. There are no SPs applied to this server and only last week we were given go ahead from one app vendor to apply SPs. That would have been done in monthly maintenance cycle next weekend. Our test server is doing just fine with all apps on SP1.
was installing MSDE for use with Web matrix thot had done all correctly ie the setup.exe sapwd=xxxxx securitymode=sql from the command prompt was told that setup has failed where is the problem
I had partitioned my harddrive to have both XP PRO and Red Hat. Got fed up with all that and so used Partition Magic 8.0 to repartition the drive to be one 16 Gig drive. I still have over 8 Gig left on it even after installing VS .NET on it.
I have successfully installed Visual Studio .NET Pro 2003 on it and I can now write programs in VB and see it on my intranet at c:/wwwroot/.
I am now trying to install MSDE 2000 for Developers Using VS .NET. I have downloaded the file from Microsoft and then when I go to install it on my hard drive it tells me it cannot; I have to free up 92.44 Megs for it to be able to extract it to my c drive.
I am a newbee and any help will be GREATLY appreciated!!
I am using VB.net to build ASP.net pages. I finally decided it was time to start using SQL server based code. So, I installed MSDE....or so I thought.
I have the server Icon in the bottom systray and it's green and seems to be running.
I have been able to use Microsoft Access' Database Upgrade Wizard to create BB.adp file.
An in VB.net I see a master.dbo connection in Server Explorer.
But I can't figure out how to access the database via the SQL server. When I right click on Server Explorer....the Create a New SQL database menu item is greyed out.
My concern is that my installation is not complete and/or I don't know how to locate and verify the server.
I'm trying to setup the ASP.Net forum on my local XP Pro PC and am having problems with MSDE security. I had an old version of MSDE on the PC and uninstalled it and downloaded/setup the version on the download page with the forum.
Looking at the MSDE readme I did the Windows Authentication mode instead of the mised mode - was that wrong?
When setup tries to setup the DB I get the log entry: Determined SQL Server version (8.00.194).
[Fail] Could not add ASPNET user to SQL Server. SQL Server does not exist or access denied.
The server is up and running and I have already used another tool to setup its DB so the server is up an running and functioning fine.
I have search around on the net about MSDE persmissions but the hits have not been helpful - they usually refer to client tools not provided with MSDE. Even if I could find instructions on setting up a user the ASPForumSetup doesn't say what user name or permissons are needed.
I can't find any spot in the XP Pro environment to setup access permissions to MSDE - is finding that the key? My login is a member of the Administrators group.
I'm leaning C# and ASP.NET at the same time using the book "Microsoft ASP.NET Programming with Microsoft Visual C# .NET Step by Step". In Appendix C, P 577, it says to locate setup.exe under …Microsoft Visual Studio .NETSetupMSDE and "run setup.exe to install MSDE."
This was my first mistake, because there are more recent versions available with security patches (for the slammer virus). I have been unable to successfully update the old version. The install program for MSDE has got to be a hackers delight because only a hacker can make it work. I decided to uninstall the old version of MSDE 2000 and install the latest download from the MSDN website. The new version would get most of the files installed and then rollback the install, removing all the files. When I tried to reinstall the old version, it did the same thing. At least the new version requires a password parameter for the sa user. The bad news is that the new password is ignored. Since I already installed the first version with a blank sa password by running setup.exe with no parameters the password will remain blank until I change it using the user friendly osql command line utility. More about osql later…
Here is how I solved the rollback problem:
I first (after many hours trying to modify the registry to clean up the mess Windows uninstaller left there) used the command line switch /L*V <your logfile name> to get a verbose log file. I noticed a property listed called "Disablerollback" this was set to 0. So, I ran setup on the command line as below (all one line):
>setup DisableRollback=1 /L*V "C:Program FilesMicrosoft Visual Studio .NETSetupMSDEsetupbat.log" SAPWD="ignored password"
The setup still failed, but its tracks were preserved for XP to complain about on system restart. I then restarted the system and logged in. XP threw an error dialog box with the message "Your server installation is either corrupt or has been tampered with (unknown package ID)…" I clicked OK and waited a few extra minutes for XP to finish logging me in.
After logging in, I closed the Service Manger from the taskbar notification area. I then deleted the folders 80, and MSSQL (name of default instance) from the target install directory. Finally, I ran setup.exe again as shown:
>setup /L*V "C:Program FilesMicrosoft Visual Studio .NETSetupMSDEsetupgood.log" SAPWD="ignored password"
This time, after restarting, my old MSDE worked. This approach seems to only work with the first old version of MSDE that was shipped with Visual Studio .NET. I still have yet to figure out how to upgrade and get MSDE to work again.
Once you get MSDE to work, here are some tips on how to administer it using the osql command tool. To change the sa password do the following (use null for a blank password): >osql -U sa Password: 1> sp-password @old=null, @new='newpassword', @loginame='sa' 2> go Password has been changed 3> quit
On page 113 of the authors' first attempt with the book "Microsoft ASP.NET Programming…", the hacks wrote: Set up the SQL Server session state database by running the InstallSQLState.sql batch (located in …) against the SQL Server you plan to use. (For more information about running batch statements, check with your database administrator or the SQL Server Books Online.)
Here is how to do it with osql:
> osql -S MSSQLSERVER -U sa -i InstallSQLState.sql
For less characters than it took to write the last parenthetical sentence, they could have just given the same example I supplied here.
If you want a graphical interface to administer you MSDE server, try downloading the small package for "Microsoft SQL Web Data Administrator" from Microsoft's website. This even comes with a modern installer. Here are some tips on how to connect to your locally installed MSDE using this utility:
The main dialog just requires that you click the start button. A login page comes up. To log in as sa, do the following:
? Click the "SQL Login" radio button. ? Under "Please enter a SQL Server name:" fill in the following text boxes: ? Username: sa ? Password: [your password | leave blank if no password is set] ? Server: (local)
This should get you to the server tools page. Click "Security", then Logins. Now, on the Logins page, you can add new users. If you install MSDE for mixed mode, you can add "Windows Integrated" user accounts. This best since you won't have to put passwords in your code to allow database access to these users. To add a user, click on "Create New Login". Set Authentication Method to "Windows Integrated" in the combo box. For Login Name you need to use the form <computername><username> . For example, "MSSQLServerDan".
If you did like I did, and installed MSDE in SQL login mode only, you can do the following registry hack to change it to mixed authentication mode:
1. Locate either of the following subkeys (depending on whether you installed MSDE as the default MSDE instance or as a named instance: HKEY_LOCAL_MACHINESoftwareMicrosoftMSSqlserverMSSqlServer
I have extracted the files from the Microsoft download and am all ready to run SETUP for the MSDE 2000 release A for Visual Studio .NET 2003 Pro.
Is there anything I need to know about or run or configure for it all to work?? I am a newbee and I am the only user on my XP Pro machine under Administrator.
Hi folks, i need ur guidance. I have a few DDL and DML scripts which i want to be automatically applied during MSDE setup; or an .MDF file be attached automatically. Please suggest an easier way!
Our NT person thinks that rebooting the SQL 2000 (on WIn 2000) server every month is a good idea (this is a client production box). I am strongly against it. For starters any trends I am trying to capture with performance monitor become useless every time we do this. I am willing to listen to every one's opinion, but I hope by now that SQL 2000 is stable enough not to have to do this.
I'm very new to SQL Server. I need to reboot the server for some reason. I need your help to list out what a the step that I need to follow to perform this process.
Hello,I have a server running Windows 2000 Advanced and Sql Server. Thesystems runs fine throughout the day but reboots at night, somtimesmultiple times. The event log has a message that reads "The previoussystem shutdown at X:XX PM was unexpected."Any ideas?Paul
I have XP Pro SP2 with MDAC 2.8.1022. It had a problem so I tried to reinstall MDAC and got a Fatal Setup Error. This setup does not support installing on this operating system. I downloaded MDAC 2.8 1177 and get the same error.
I thought of uninstalling/reinstalling SP2, but this is a 2 month old Dell Latitude 610 with factory installed XP. There is no Windows Service Pack 2 option listed in the Control Panel > Add/Remove Programs.
There's some other strange things, so I wonder if they are related.
1) I have Paul set up as an administrator account. Some folders like MSSQL show that account with no permissions. I grant all the permissions to Paul for that folder. I come back later and the permissions are gone.
2) I deleted 20 files in Explorer, but 7 of them did not go away. I deleted those 7 again and they instatnly reappeared. I deleted those 7 again and then they finally went away.
3) I get a slow reaction time for things like Windows Explorer and opening and closing programs. This is suprising since it has 2 gig of RAM and 2.3 Gig processor. Could it be a memory handling problem that's causing OS problems. Probably, the memory didn't handle the OS installation well and the whole system is compromised now.
We're doing upgrades from SQL 2008 R2 to SQL 2014. This is blocked due to RS is installed but not configured. Our desired action is to uninstall RS and proceed with the upgrade. But when setuparp.exe is raised, it does not list all the features on the 'Select Features' page. In fact, it only lists the last 2 shared features (SQ Client Connectivity SDK and Microsoft Sync Framework). However, all items appear to be listed on the 'Select Instance' page including RS. I've seen this issue on 2 of our SQL 2008 R2 Servers already.
We have to add some hardware and I was wondering if someone could provide a stepwise tip to do it .
It is a 3 Server Environment Pub/Dist/Sub All three running under SQL2K Here is what I am planning.
a. Uncheck the Enable in Distributed Agent for each replication b. Wait for all replications to complete c. Shut down Publisher ? Or do I have to do something else before that.
I've just rebooting the db server and I've currently got 82 connections open to the server. vb6 apps connect fine but .Net apps are sruggling - sa is sql200 query analyzer. they can't get a connection to the server - it just hangs for ages. any idea?
Here is the block of the sproc that I?ve created. All lines executefine except for the ?exec master..xp_cmdshell @reboottc?. In order tomake this work from the query analyzer I had to set the MSSQLSERVERservice to have the same credentials as the thin clients we are tryingto shut down, that means the service is running as an Administrator onthe sql server with the same u/p as administrator on thin clients.declare @RoomNumber varchar(6) -- for testingset @RoomNumber = '1144' -- for testingDECLARE @RoomIP varchar(15), @RebootTCvarchar(120), @shutdownStart varchar(20), @shutdownEnd varchar(85)-- @ShutDownStart and @ShutDownEnd will be usedwith the @RoomIP to build the shutdown command sent to the thinclientsSET @ShutDownStart = 'shutdown -r -f -m \'SET @ShutDownEnd = ' -t 5 -c "MandatoryiConnect Reboot issued during guest check in/out process"'SELECT @RoomIP = IP FROM Rooms WHERERoomNumber = cast(@RoomNumber AS INT)SET @RebootTC = @ShutDownStart + @RoomIP +@ShutDownEnd-- print @RebootTC -- for testing-- @RebootTC ends up looking like the line below based on the@RoomNumber-- shutdown -r -f -m \172.18.16.103 -t 5 -c "Mandatory iConnectReboot issued during guest check in/out process?-- Also the command below runs correctly when executed from SQL QueryAnalyzerEXEC master..xp_cmdshell @RebootTC
An IT dept. I have been consulting with has started to reboot SQL server every night. They are saying that this is the best practices. I would like to know if anyone has any other ideas on this subject. What is the best practices for how often a SQL server should be rebooted, daily, weekly, monthly ... ?
I just installed SP2. I wanted to install the AdventureWorksDW database as part of the Database Engine Tuning Advisor tutorial. It said my install was not finished and I had a "pending reboot requirement." I shut down, and 8 different updates ran. When I tried to install the AdventureWorksDW database again, I got the same message. I'll see if there are still more updates to run.
I installed SP1 for SS 2005 on a quasi-production server, which is why I didn't mind rebooting the server. Unfortunately, it's been 5 hours and the server still hasn't rebooted. (I see a gray screen and a pointer, and that's it... but there's still disk access happening. I'm not really sure what it's doing.)
What's the best way to avoid the 5 hour reboot in the future?
I'm not sure if it's the setup I did wrong, but I can't seem to get my text datatype in my database to store more than 900 characters. I'm trying to setup a news database for my website, which will populate the information into a datagrid. To test, I manually added a news item in the database through the visual studio 2003 gui. I immediately noticed a problem as the I was getting an error after a long news item saying:
"The value you entered is not consistent with the data type or length of the column, or over grid buffer limit."
I couldn't find anthing to set the buffer limit and the datatype is "text" filled with simple text in the column. As a further test, I simply entered 12334567890123... up to 900 characters and still recevied the error.
I would appreciate someone leading me in the right direction on this one.
I am running SQL Server 7.0 on a Web server and recently the SQL Server has been acting up. Basically what happens is every time the server is restarted the Service Manager fails to restart. I even get an error telling me that the service failed to start. So, when I log back in I have to physically restart the Service Manager. I have the services set to start automatically. Can anyone direct me where to look...perhaps a SQL Server log that might give me a clue. My application and error logs only tell me that it stops. Any ideas?
I have transactional replication set up between two dedicated servers. Server A is the PDC and Server B is a BDC (they are both Win2000 boxes). Both the servers are brand new, and replaced the two that were running like clock work (replication wise) for the last 12 months. I never had this problem with the old servers....
When the servers are shut down (as the case was a couple of weeks back with a power failure) or just recently when they were move to another room. Both servers boot up at the same time. Server B (which is the server holding the db being replicated) boots quicker and as a result replication fails and is then 'sucessfully stopped'. Unless I am aware of the server being rebooted and can monitor this potential problem, within 2 days the logfile grows to large and everything comes to a crashing halt.
I just remove replication, truncate and shrink the log, reset replication and we're away.... BUT I really need to know why it is happening in the first place. I figure there must be a setting that I have forgotten about or something.