June 30, 2009 | In Development | No Comments
Having created a new site on my development machine using the MS Charting controls (see my previous post here) I published to my test server. I found two things that must be rememered when doing this.
First up you will need the System.Web.DataVisualization assembly on the server, else you will receive an ‘assembly not found’ error (that one’s obvious really). This is installed from the MSChart.exe (Microsoft Chart Controls for Microsoft .NET Framework 3.5). I believe the assembly is to included in the .NET Framework 4 by default.
The second is that an entry is created in your web.config file for storage of the temporary images that are used to display the charts. This needs to be changed to that of a directory that you have write permission for. The default is set to whichever drive you were originally developing on. I’d suggest setting to a physical path somewhere inside the website root. You will need to find the absolute path for this using something like Server.MapPath (if you don’t know it already).
June 29, 2009 | In Development | No Comments
I received this error message when I was trying to add a data connection to a SQL Server 2008 instance from Visual Studio Web Developer 2008 Express in Windows 7:
Unable to add data connection.
Could not load file or assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
For me the answer was install the following from the Microsoft SQL Server 2008 Feature Pack, August 2008 site:
- Microsoft SQL Server Management Objects
and do a repair install on
- Microsoft SQL Server System CLR Types
June 21, 2009 | In Development | No Comments
I received the following error from Windows 7 when trying to connect to my office server (running Microsoft Windows Server 2008):
Error: 812 The connection was prevented because of a policy configured on your RAS/VPN server. Specifically, the authentication method used by the server to verify your username and password may not match the authentication method configured in your connection profile. Please contact the Administrator of the RAS server and notify them of this error.
It seems this is a common problem from users with Vista too.
The solution was that the user account did not have dial-in permissions set in Active Directory. Simple as that.