Wednesday, June 11, 2008
Result set was not generated by a SELECT statement
This obscure error occurred when using PHP ODBC to retrieve values from a stored procedure. It turns out this occurs when the stored procedure SELECTs data from one or more TEXT columns. Convert these columns to VARCHAR(8000) and you're good to go.
Monday, June 9, 2008
AGONY: Vista Business x64 and SQL Server Management Studio
I have been fighting this one for days: my computer is currently joined to our corporate domain, but I am logged in as a local user. I've used "Manage network passwords" to add all of the relevant credentials for domain access. However, I still get the following error when logging in via Windows Authentication in SSMS:
Login failed for user ''. The user is not associated with a trusted SQL Server connection.
The error logs show that the SSPI handshake is failing - meaning that Windows is not passing along my valid domain credentials to SQL Server.
Finally, I found a workaround that deals with what I'm experiencing by making use of the runas command. It's hacky, and this is definitely due to Vista's "wonderful feature", but it gets the job done. Thanks to Jason Follas for the following tip:
http://www.jasonfollas.com/wiki/Default.aspx?Page=SQL%20Management%20Studio%20on%20Vista&AspxAutoDetectCookieSupport=1
For the record, we should not have to do this.
Login failed for user ''. The user is not associated with a trusted SQL Server connection.
The error logs show that the SSPI handshake is failing - meaning that Windows is not passing along my valid domain credentials to SQL Server.
Finally, I found a workaround that deals with what I'm experiencing by making use of the runas command. It's hacky, and this is definitely due to Vista's "wonderful feature", but it gets the job done. Thanks to Jason Follas for the following tip:
http://www.jasonfollas.com/wiki/Default.aspx?Page=SQL%20Management%20Studio%20on%20Vista&AspxAutoDetectCookieSupport=1
For the record, we should not have to do this.
Labels:
64,
agony,
login failed,
network passwords,
SQL Server,
trusted connection,
user,
vista
Wednesday, April 23, 2008
How to install Windows SharePoint Services 3.0 Tools to XP or Vista
Another blog ripoff, this time from Janne Mattila, on how to trick XP or Vista machines into thinking that WSS 3.0 is installed so that you can install WSS 3.0 Tools for Visual Studio 2005:
http://blogs.msdn.com/jannemattila/archive/2007/08/16/how-to-install-windows-sharepoint-services-3-0-tools-to-xp-or-vista.aspx
Details: it's a registry hack...
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0]
"Sharepoint"="Installed"
http://blogs.msdn.com/jannemattila/archive/2007/08/16/how-to-install-windows-sharepoint-services-3-0-tools-to-xp-or-vista.aspx
Details: it's a registry hack...
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0]
"Sharepoint"="Installed"
Tuesday, April 22, 2008
How to Create a MOSS 2007 VPC Image
Wonderful series of posts by Tony Zink outlining exactly what you need to do to set up Microsoft Office SharePoint Server 2007 on a Virtual PC with a SQL Server 2005 backend and full e-mail capabilities:
http://www.pptspaces.com/sharepointreporterblog/Lists/Posts/Post.aspx?ID=28
http://www.pptspaces.com/sharepointreporterblog/Lists/Posts/Post.aspx?ID=28
Thursday, April 3, 2008
LINQ to SQL and the DataGridView control
A DataGridView control won't bind directly to an IEnumerable object, so two options are:
1. Create a BindingSource, set its DataSource to the IEnumerable object, then set the DataGridView.DataSource property to the BindingSource.
2. Bind the DataGridView.DataSource property to the IEnumerable object's ToList() method.
Thanks to Ken Tucker on Microsoft Forums for this tip.
1. Create a BindingSource, set its DataSource to the IEnumerable object, then set the DataGridView.DataSource property to the BindingSource.
2. Bind the DataGridView.DataSource property to the IEnumerable object's ToList() method.
Thanks to Ken Tucker on Microsoft Forums for this tip.
Labels:
BindingSource,
DataGridView,
DataSource,
empty grid,
IEnumerable,
LINQ to SQL
Monday, March 3, 2008
How to resolve "__doPostBack is not defined" error
Thanks to Julien Pinquié:
When I ran across this, I found that I'd closed a <script> tag referring to an external .js file with /> notation instead of <script></script>; the <script> tag doesn't accept this notation for whatever reason.
When I ran across this, I found that I'd closed a <script> tag referring to an external .js file with /> notation instead of <script></script>; the <script> tag doesn't accept this notation for whatever reason.
Sunday, February 17, 2008
Simple Port Scan
The following function will check to see if connectivity is enabled for a particular host on a particular port via TCP/IP:
Function ScanPort(ByVal strHost As String, ByVal intPort As Integer) As Boolean
Dim aobjIPs() As System.Net.IPAddress = System.Net.Dns.GetHostEntry(strHost).AddressList
If aobjIPs.Length > 0 Then
Dim objEndpoint As New System.Net.IPEndPoint(aobjIPs(0), intPort)
Using s As New System.Net.Sockets.Socket(System.Net.Sockets.AddressFamily.InterNetwork, System.Net.Sockets.SocketType.Stream, System.Net.Sockets.ProtocolType.Tcp)
Try
s.Connect(objEndpoint)
Return s.Connected
Catch ex As Exception
Return False
End Try
End Using
Else
Return False
End If
End Function
Function ScanPort(ByVal strHost As String, ByVal intPort As Integer) As Boolean
Dim aobjIPs() As System.Net.IPAddress = System.Net.Dns.GetHostEntry(strHost).AddressList
If aobjIPs.Length > 0 Then
Dim objEndpoint As New System.Net.IPEndPoint(aobjIPs(0), intPort)
Using s As New System.Net.Sockets.Socket(System.Net.Sockets.AddressFamily.InterNetwork, System.Net.Sockets.SocketType.Stream, System.Net.Sockets.ProtocolType.Tcp)
Try
s.Connect(objEndpoint)
Return s.Connected
Catch ex As Exception
Return False
End Try
End Using
Else
Return False
End If
End Function
Subscribe to:
Posts (Atom)