Dailycode.info

Short solution for short problems

SPF CREATE DATABASE permission denied in database 'master'

While installing SPF on I kept gettings this error: CREATE DATABASE permission denied in database 'master'.

So I was giving the user sufficient rights tfor this, but still I got the error. After some googling around, I found out that the user who is running the setup need to have these rights, not the user you provide to the wizard.

So after I gave my user sufficient rights it worked. Hope some people will be helped with this!

 


Click once deployment configuration. (Tutorial)

Setting up your VS project (WPF, Win and Console) for click once deployment.
 
Before you deploy the Windows application, you set properties for Security and Publish from the application's Properties window.
 The Security property sets the permissions for your application. By default, the ClickOnce deployment has a limited subset of permissions. You can set the permissions to deploy only to client machines on the Intranet or Internet, or to allow full permissions.
 The Publish property sets the deployment location to a Web Site URL, an FTP server, or a file path. Also, this property sets necessary prerequisites and updates to the deployed application.

 To set the ClickOnce Deployment Options.

1.       In the Solution Explorer, right-click the bold project name, and click Properties.
2.       Click on the Security tab.
3.       Select Enable ClickOnce Security Settings.
By default, the ClickOnce security permission is set to: This is a full trust application.
   
4.       Click on the Publish tab, and then click Prerequisites.
5.       Here you can set any prerequisites for theprogram.
Note   Encourage your clients to install the .NET Framework or any other runtime before you deploy the Windows application, because installation time increases significantly if you use ClickOnce to install the prerequisites.
6.       Click OK.
7.       On the Publish tab, click Updates. From the Application Updates dialog box, ensure the following options are selected:
a.       Select: The application should check for updates.
b.      In the Choose when the application should check for updates list, select: Before the application starts.
  
8.       Click OK to close the dialog box.
9.       From the File menu, click Save All.
 
 
 

To publish a Windows application.

1.       In the Solution Explorer, right-click the bold project name, and click Publish.
2.       Choose where to publish the application.
  
3.       Choose the location where the users will install the application from (Use the same location but provide the UCN path name (Do not use mapped drive names-see example below)).
  
4.       Choose the first option that the application is available offline.  
 
5.       Click finish
  
 

Installing the application on a client.

1.       Go to the installation directory and click on the setup.exe.
  
2.       Click run
  
3.       Click on install.
  
4.       The application is automatically opened.
  
 

Deploying a new version

1.       Raise the assembly version.
2.       Republish the files (Same flow as described in previous chapter).
3.       Open the program on the client
4.       Choose whether to update to the new version or keep working with the current version.
  
5.       If you click skip, the next time you open the program, it will not ask to be updated again until a newer version is deployed or a republish is done of the current version. You can configure a minimum version, if the client version is below the minimum version, the update will occur without asking the client to Skip or press OK.
  
6.       If you click OK then the new version is installed and opened.
  
 

Uninstalling the application

1.       Remove the application using the windows program management
  
  
2.       You can also restore the application to a previous version. 

Installing WSS 3.0

Today I started with the installation of WSS 3.0 on a windows 2003 server using MS SQL 2000. Normally this proces takes up a few hours max.

The only difference is that this time I'm installing it in a company that has very strict regulations. It is not possible to reboot a server without permission, etc. I started with lots of courage because I never had big problems in the past. The only problem I ever had with installing WSS would come to haunt me again!

First I had to install IIS, framework 2.0 and 3.0. Still no problem here. I dindn't had to reboot the server! Then I started the installation of WSS.

GRRRaaaghhh, there it was. The collission of the database was not correct! So I created a database, with the correct collision (Latin1_General_CI_AS_KS_WS). But still it will not install. The default collission of the server needs to be changed because the install proces wants to create a database and therefore it needs the default collission. The last time a had this problemn, I could reinstall the server with the correct collission and all problems were solved. But in this case it is not an option.

So I started looking for other options. There is a tool called rebuildm.exe that rebuilds the master database to the new collision, resetting the default collission of the server. But this tool wasn't present. Because in the installation of the server, this tool was not included. Now I have to wait for the administrator to approve the change, which I'm guessing he won't allow. I'll have to prove that rebuilding the master DB does not affect the collission and data of the user databases. This is the challenge I'm up to now. I will write the solution in this post later.

If people have a better solution then rebuilding the master DB or reinstalling the SQL server, please inform us!