SQL Express CTP 2 provides a checkbox that will enrol the user installing the software as a database administrator. If the user fails to check this box, they run as an ordinary user, and hence are not allowed to perform functions such as create database.
In the process of deploying an application via ClickOnce, if SQL Express is not present it will be installed automatically. Also, in the process of deploying a ClickOnce application, we should usually expect to need to create a new database. Currently, if the user takes the default install of SQL Express they will not be a database administrator and will not be able to create the database. The installation will thus fail.
Is anything being done with SQL Express for ClickOnce applications deploying to Vista that will allow us to automatically enrol the user installing SQL Express as a database administrator?
I'm working on an app in Visual Studio 2005 that needs to have installed locally SQL Express to handle its own data.
This app is in a strong upgrading process. I've been using clickonce to publish the app and let my users upgrade automatically (by the way this works amazing ...).
Yet many times changes to the DB are made. Is there a simple way to upgrade their local SQL Express DB like click once does with the app?
I've written a ClickOnce app that deploys a Sql Server Express data file (.mdf) and log file (.ldf) along with the other application files. SQL Express SP2 is a prerequisite for this app. After the applicaiton installs and starts up it copies these files to a specific folder and attaches them by calling the AttachDatabase() method of a Microsoft.SqlServer.Management.Smo.Server object.
This method works fine using Windows XP, however when I run it on Windows Vista I get the following exception:
Microsoft.SqlServer.Management.Smo.FailedOperationException: Attach database failed for Server 'localhostSQLEXPRESS'. ---> Microsoft.SqlServer.Management.Common.ExecutionFailureException: An exception occurred while executing a Transact-SQL statement or batch. ---> System.Data.SqlClient.SqlException: Unable to open the physical file "C:WashMasterDatabasewasshmaster.mdf". Operating system error 5: "5(Access is denied.)".
This exception occurs when I try to programmatically attach the database.
I've searched through the MSDN forums for a solution and I've only found two suggestions:
1.) Create all database connections using a User Instance. 2.) Create the database (using SQL) in the target folder, rather than copying it over from the deployment folder.
I don't like the idea of using User Instances because my entire data access layer is currently written using Ole and I would rather not rewrite it if I don't have to. I cannot find any way to use User Instances with Ole.
I also don't like the idea of creating the database using SQL because it is fairly large.
Here are my questions:
1.) Can User Instances be used with Ole?
2.) Can I somehow programmatically set the permissions of the copied data and log files so that SQL Express can access them without error?
3.) Is there a better method for doing what I'm trying to do or am I destined to have to either rewrite in data access layer so I can use User Instances or create my large database rather than copy it to the target directory?
I'm posting this in the ClickOnce forums as well...
My application doesn't include the .mdf and .ldf files, rather it creates the database the first time the application is run using a script that is included in the build. I want to create the database in the ClickOnce data directory. The problem I'm having is that SQL Server complains when I execute the CREATE DATABASE command as follows:
CREATE DATABASE [C:Documents and SettingsxxxxxLocal SettingsApps2.0DataPQCK6EXN.5KGAW630RPT.VGOifie..tion_014028c05b1d6ec6_0001.0002_0e86966f19503c89DataiFieldMobile.mdf] ON PRIMARY ( NAME = N'myDatabase', FILENAME = N'C:Documents and SettingsxxxxxxLocal SettingsApps2.0DataPQCK6EXN.5KGAW630RPT.VGOifie..tion_014028c05b1d6ec6_0001.0002_0e86966f19503c89DatamyDatabase.mdf' , SIZE = 3136KB , MAXSIZE = UNLIMITED, FILEGROWTH = 1024KB ) LOG ON ( NAME = N'myDatabase_log', FILENAME = N'C:Documents and SettingsxxxxLocal SettingsApps2.0DataPQCK6EXN.5KGAW630RPT.VGOifie..tion_014028c05b1d6ec6_0001.0002_0e86966f19503c89DatamyDatabase_log.ldf' , SIZE = 1024KB , MAXSIZE = 2048GB , FILEGROWTH = 10%) END
Here's the error:
System.Data.SqlClient.SqlException "The identifier that starts with 'C:Documents and SettingsxxxxxxLocal SettingsApps2.0DataPQCK6EXN.5KGAW630RPT.VGOifie..tion_014028c05b1d6ec6_0001.00' is too long. Maximum length is 128."
I have prepared an installer with 2 prerequisites for my project using Bootstrapper. It checks .NET framework 2.0 and then SQL Express 2005. The isntaller works fine on XP sp2 and windows server 2003 but when I tested it on Vista, it is giving me an exception. I checked the log file and found this in the log file. "Result of running operator 'ValueNotEqualTo' on property 'ProcessorArchitecture' and value 'Intel': true Result of checks for command 'SqlExpresssqlexpr32.exe' is 'Fail' 'SQL Server 2005 Express Edition' RunCheck result: Fail A prerequisite failed for Package "SQL Server 2005 Express Edition" Package failed with message "This version of SQL Server 2005 Express Edition is not supported for the current processor architecture."
I am using sql server 2005 express edition with SP2. I think it is failing to use sqlexpr32.exe here. Is there any problem of this exe running on vista? Please help..."
anyone know of any issues related to installing and running SQL Express on Vista? Please provide a link or some tips I need to consider for deployment.
I have heard something about the windows authentication not working unless you connect the windows login to a sql server login.
Actually I should have said #22 but this is beyond the point. It seems the errors pop up and then go away for no reason, then appear again.
I had Sql Server Express with Advanced Features set up all right as far as I can see. It is the connection issue that is causing the headache.
Currently when I try to make a connection with an Sql database I get an error in Visual Studio:
Generating user instance in Sql Server is disabled. Use sp_configure 'user instances enabled' to generate user instances.
So I go to Sql Server, log in, open a new query and type:
sp_configure 'user instances enabled' GO
I get a table where I can see that
name minimum maximum config_value run_value user instances enabled 0 1 1 1
Are they enabled? I think, yes. I go back to Vsisual Studio and get the same error. It is possible that I will have to log out in order for all this security garbage to take effect and I will try it but in the meantime, how can I set more than one instance.
I want to complain that these new security provisions that came apparently with SP2 and Vista are totally unnesessary for my applications. I do not have any high security info to worry about, e.g. social security numbers, etc. I would not mind to turn all this stuff off if it is possible at all.
Hi, Vista Business, SQL 2005 Express SP2 I am a big time newbi to SQL 2005 Express any help appriciated. When I add a new data base to my asp.net page I get this >>> "Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed." Any suggestions? Thank you for reading my mail any repliers.
I am having issues with adding a new database in vwd 2008 as i keep getting the error “Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.� I have tried most of the tips on the net already including changing SQLEXPRESS Built-in account to Local System instead of Network Service, running as a administrator and going into surface area to add new admin and adding priveledges to my account. None of these have helped. I can create a database in the management studio but can't create it in vwd and also the asp.net applications doesn't run either. can anyone help as i have no idea what to do.
I'm having issues talking to Vista Sql Express, but selectivly.
The following diagram shows you what works, and what doesn't :
http://www.craznar.com/junk/sqlissue.png
As you can see, the Vista/Express server is running - has all the required connectivity enabled, however we cannot talk from the Windows Server 2003 SQL to the Vista SQL.
The error that is given suggests issues with remote access enabling on Vista - but this is working alsoVista's firewall turned off (We can connect to it).
All machines are on the same subnet, behind the same firewall - Neptune and Headoffice are on a domain, Neptune points to Headoffice for DNS, Headoffice forwards DNS requests to the same DNS all other machines use.
File sharing and Ping work from Headoffice to Neptune ... just can't get SQL connection to work.
I tried installing SQL Server 2005 Express on my VISTA Beta 2 Box but before doing so, I checked if IIS is already installed and running. During the assesment of my current configuration, SQL Server 2005 Express is still looking for IIS. Are the conflicts regarding IIS 7.0 to SQL Server Express or the feature is not yet available. I will be continuing to do experiments with this one and hope there will be people who can share their experiences too.
We are in the process of converting our MSDE-enabled products to using SQL Express for compatability with Vista. With help from the msdn article at http://msdn2.microsoft.com/en-us/library/ms165716.aspx I've been able to create a test install that works fine under XP, but fails under Vista. We have our application installing under the "Program Files" directory, and are copying the database's MDF file into the same directory. We are using AttachDbFileName to connect to the database and under XP the LDF file is created fine. Under Vista we receive an error that the database cannot be attached and I've noticed that the LDF file is not being created. I was receiving the exact same error under XP until I removed the LDF file from the install and allowed SQL Express to create it. I'm guessing that it is an issue in the permissions necessary to write the LDF file out to the applications directory, but that's just a guess. So, I was wondering what the Microsoft recommended method for doing a SQL Express XCopy deployment under Vista was?
I'm trying to install sql express sp2 2005 in my laptop but i can't, give me this error
Machine : W7J Product : Microsoft SQL Server 2005 Express Edition Product Version : 9.2.3042.00 Install : Failed Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0015_W7J_SQL.log Last Action : InstallFinalize Error String : SQL Server Setup could not connect to the database service for server configuration. The error was: {Microsoft}{SQL Native Client}{SQL Server}Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online. Error Number : 29515
I'm choosing Windows autentication mode, so i don't know it says "sa" user.
I'm preparing to install VS2005 along with SQL Server 2005 express on VISTA. Honestly, I just hope nothing will get screwed up...
- After installing VS2005, I will first install SQL Server 2005 express from my VS2005 DVD - I will then install SQL Server 2005 express with Advanced services SP2 as well as SQL Server 2005 express toolkit SP2 upgrades.
A few technical questions:
1. Considering the fact that I have Office2007 as well as Outlook 2007 installed on my VISTA machine, is there any install issues regarding SQL Server 2005 and Office2007? I remember having read posts reporting install problems... Any feedback would be appreciated.
2. After I install SQL Server 2005 Express from VS2005 DVD, do I need to install SQL Server 2005 Express SP1 before installing SP2?
I purchased a Dell laptop with Vista. I then downloaded MSSQL Express Edition with Advanced Services (after first downloading .NET 3.5) and when it tried to run the executable, it gave an error that it was not a valid win32 app.
How to I correct this and successfully install MSSQL Express?
I have written a custom executable thats purpose is to find and uninstall a named instance. It works as intended on PC's running XP and Vista with UAC turned off. However when I try to run the exe on a Vista Machine with UAC on, it does not fully remove the named instance.
It leaves behind in the folder path: "C:Program FilesMicrosoft SQL ServerMSSQL.2MSSQL" three folders: "Data", "LOG", and "Template Data". However it does remove all of the registry entries and all of the services attached to that named instance.
Why oh why does it have permission to remove everything else besides these 3 folders, and how (programmatically) can I give it the proper admin rights?
the code that does all the work from the cmd:
msiexec /x "ProductCode" /passive
The removal of these three folders is important b/c when you try to reinstall the namedinstance it gives an error message saying files already exist inside the "Data" Folder.
I have been trying to get Visual Basic 2005 Express and Visual Web Developer Express to work with SQL Server 2005 Express. I am using Windows Vista.
I am running VB as an administrator. SQL Server SP2 is installed and working, and I can use SSMSEE to connect to it, create databases etc.
But VB and Web Developer cannot connect to it. Can anyone tell me how to get these products working on Vista (or do they in fact simply not work on Vista)?
Can someone tell me what I need to get Express on Vista, I see a lot of contradictory information. Michael Otey notes in his column SP1, but then I here SP2.... Do I have something I can run today ...if not when..
I installed SQLE 2005 on vista home prem, and when I go to the studio and attempt to create a database, I get the message below. I am running under an admin account, but the system sees me as a standard user.
Do I need to re-install and tell the system to allow me to log on via. an ID/PW?
Is there a vista patch?
Should I re-install XP?
Also, not having this issue with the same SQLE version and an XP machine.
Thanks
TITLE: Microsoft SQL Server Management Studio Express------------------------------Create failed for Database 'test'. (Microsoft.SqlServer.Express.Smo)For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+Database&LinkId=20476------------------------------ADDITIONAL INFORMATION:An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Express.ConnectionInfo)------------------------------CREATE DATABASE permission denied in database 'master'. (Microsoft SQL Server, Error: 262)For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3042&EvtSrc=MSSQLServer&EvtID=262&LinkId=20476------------------------------
We use SQL Express in our Applikation in file mode. Users can create databases in different folders and pathes. Each time a user loggs into our applikation, we attach the db he choosed, and every time he closes the applikation, we detach the db.
While this works fine in Windows XP, we have serious problems with Windows Vista.
We tried a connectiong string with "attachdbfilename", "sp_attach_db" and SMO server.AttachDatabase
Where could we get some more advice for our problem. It is in fact an issue of UAC.
Question about deploying a SQL compact database with Clickonce. Deploying the first time is straightforward and that works OK but I am not so sure about consequent releases, how do I deal with the that? If I mark the file as dont deploy that will, of course, work fine for those that have installed the first release but not for thoses that havent. What about if I make a change to the database, adding a table for example. How do I go about that? I obviously dont want to loose any of the existing data?
ok, today i upgraded to Vista, but i can't create database. create database permission denied in database master. ("Microsoft sql server Error 262") it must be the Vista thing because i don't have any problem with xp. yes, i the patch installed. I use SQl server management studio with Windows Authentication
When I install SQL Express on my XP Machine, the registry keys under local machine (ie, MSSQL.1, etc) show up, but on my Vista 64bit machine, the MSSQL.1 etc keys are not there. SQL Server still works, but the reg keys are missing.
Code Snippet[05/30/07,17:59:59] Microsoft SQL Server 2005 Express Edition x86: [2] Component Microsoft SQL Server 2005 Express Edition x86 returned an unexpected value. ***EndOfSession***[05/30/07,17:59:59] Microsoft SQL Server 2005 Express Edition x86: [2] Component Microsoft SQL Server 2005 Express Edition x86 returned an unexpected value. [05/30/07,18:00:02] VS70pgui: [2] DepCheck indicates Microsoft SQL Server 2005 Express Edition x86 is not installed. [06/04/07,21:30:31] Microsoft SQL Server 2005 Express Edition x86: [2] Component Microsoft SQL Server 2005 Express Edition x86 returned an unexpected value. ***EndOfSession***[05/30/07,17:59:59] Microsoft SQL Server 2005 Express Edition x86: [2] Component Microsoft SQL Server 2005 Express Edition x86 returned an unexpected value. [05/30/07,18:00:02] VS70pgui: [2] DepCheck indicates Microsoft SQL Server 2005 Express Edition x86 is not installed. [06/04/07,21:30:31] Microsoft SQL Server 2005 Express Edition x86: [2] Component Microsoft SQL Server 2005 Express Edition x86 returned an unexpected value. [06/04/07,21:30:34] VS70pgui: [2] DepCheck indicates Microsoft SQL Server 2005 Express Edition x86 is not installed. [06/05/07,03:21:33] Microsoft SQL Server 2005 Express Edition x86: [2] Component Microsoft SQL Server 2005 Express Edition x86 returned an unexpected value. ***EndOfSession***[05/30/07,17:59:59] Microsoft SQL Server 2005 Express Edition x86: [2] Component Microsoft SQL Server 2005 Express Edition x86 returned an unexpected value. [05/30/07,18:00:02] VS70pgui: [2] DepCheck indicates Microsoft SQL Server 2005 Express Edition x86 is not installed. [06/04/07,21:30:31] Microsoft SQL Server 2005 Express Edition x86: [2] Component Microsoft SQL Server 2005 Express Edition x86 returned an unexpected value. [06/04/07,21:30:34] VS70pgui: [2] DepCheck indicates Microsoft SQL Server 2005 Express Edition x86 is not installed. [06/05/07,03:21:33] Microsoft SQL Server 2005 Express Edition x86: [2] Component Microsoft SQL Server 2005 Express Edition x86 returned an unexpected value. [06/05/07,03:21:39] VS70pgui: [2] DepCheck indicates Microsoft SQL Server 2005 Express Edition x86 is not installed. [06/05/07,11:30:05] Microsoft SQL Server 2005 Express Edition x86: [2] Error code 258 for this component means "The wait operation timed out. " [06/05/07,11:30:06] Microsoft SQL Server 2005 Express Edition x86: [2] Component Microsoft SQL Server 2005 Express Edition x86 returned an unexpected value. [06/05/07,11:30:06] Microsoft SQL Server 2005 Express Edition x86: [2] Return from system messaging: The wait operation timed out.
***EndOfSession***[05/30/07,17:59:59] Microsoft SQL Server 2005 Express Edition x86: [2] Component Microsoft SQL Server 2005 Express Edition x86 returned an unexpected value. [05/30/07,18:00:02] VS70pgui: [2] DepCheck indicates Microsoft SQL Server 2005 Express Edition x86 is not installed. [06/04/07,21:30:31] Microsoft SQL Server 2005 Express Edition x86: [2] Component Microsoft SQL Server 2005 Express Edition x86 returned an unexpected value. [06/04/07,21:30:34] VS70pgui: [2] DepCheck indicates Microsoft SQL Server 2005 Express Edition x86 is not installed. [06/05/07,03:21:33] Microsoft SQL Server 2005 Express Edition x86: [2] Component Microsoft SQL Server 2005 Express Edition x86 returned an unexpected value. [06/05/07,03:21:39] VS70pgui: [2] DepCheck indicates Microsoft SQL Server 2005 Express Edition x86 is not installed. [06/05/07,11:30:05] Microsoft SQL Server 2005 Express Edition x86: [2] Error code 258 for this component means "The wait operation timed out. " [06/05/07,11:30:06] Microsoft SQL Server 2005 Express Edition x86: [2] Component Microsoft SQL Server 2005 Express Edition x86 returned an unexpected value. [06/05/07,11:30:06] Microsoft SQL Server 2005 Express Edition x86: [2] Return from system messaging: The wait operation timed out.
[06/05/07,11:30:10] VS70pgui: [2] DepCheck indicates Microsoft SQL Server 2005 Express Edition x86 is not installed. [06/05/07,11:52:13] Microsoft SQL Server 2005 Express Edition x86: [2] Component Microsoft SQL Server 2005 Express Edition x86 returned an unexpected value. ***EndOfSession*** I try to install it from visual studio net professional 2005, every time it fails. Any idea?
Alright I glanced over the forums to see if there was an answer for this and I didn't see one. I saw a few similar issues however nothing that fixes my issue. Here is my problem.
I installed SQL Server 2005 Express on my Vista partition along with Visual C# Express. For some reason I cannot get the SQL Server 2005 Express to function correctly. Back when installed this on XP it worked flawlessly, and I don't even recall doing anything special...I installed it and it worked. I do know that you have to manually add the user account to the admin list for the SQL server on Vista, and I did that. I chose the option to have it do it during installation as well as through the SQL Server Surface Area Configuration just to be sure.
I am just trying to get the basics of it working right, and that is connecting to the server using C# and filling a dataset...it shouldn't be this hard. This morning when I started with this I could connect and fill my DataSet programmatically however it wouldn't pass the test through the Data Source Configuration Wizard. When I did it manually, as I said it worked and filled the DataSet with the info I asked for below in the code sample. After getting annoyed by it not working through the wizard I decided that maybe I had my permissions wrong and I may have messed up when installing it. So I uninstalled everything to do with SQL Server 2005 and reinstalled it fresh.
This time when I installed it I made sure to set it up to use Windows Authentication. Now it will pass the Test in the Data Source Configuration Wizard and everything is working by doing it that way. However now it doesn't work when I do it manually with the code below(same code as before when it worked...lol). When I use the code below it crashes with the error: "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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)". When I go through it with the debugger it throws that error at the call dataAdapter.Fill(...). The code is the following:
string commandStr = "Select CompanyName, ContactName from Customers";
SqlDataAdapter dataAdapter = new SqlDataAdapter(commandStr, connStr);
DataSet dataSet = new DataSet();
dataAdapter.Fill(dataSet, "Customers");
DataTable dataTable = dataSet.Tables[0];
foreach(DataRow dataRow in dataTable.Rows)
lbCustomers.Items.Add(dataRow["CompanyName"]+
" ("+dataRow["ContactName"]+")");
Why doesn't that work yet I can basically ask for the same information and it will work if I do it through the wizard? If it works 1 way I wouldn't think there could be any issues with the server being accessed remotely, right?
