by joe.pesch
27. February 2009 20:04
The following syntax will stack two values on top of each other in a single text box:
=Fields!FieldName1.Value & Chr(13) & Chr(10) & Fields!FieldName2.Value
4fd34c67-d3ae-42ca-aeab-2335baed5f39|0|.0|96d5b379-7e1d-4dac-a6ba-1e50db561b04
Tags:
C#, Windows
SSRS
by joe.pesch
16. February 2009 18:21
<scriptid="SetOpacity"type="text/javascript"language="Javascript">
function SetOpacity(obj, val) { val = (val > 100) ? 100 : val;
val = (val < 0) ? 0 : val;
obj.setAttribute('SetOpacity', val); alert(obj.id);
if (navigator.appName.indexOf("Netscape") != -1 && parseInt(navigator.appVersion) >= 5) { obj.style.MozOpacity = val / 100;
obj.style.opacity = val / 100;
}
elseif (navigator.appName.indexOf("Microsoft") != -1 && parseInt(navigator.appVersion) >= 4) { obj.style.filter = 'alpha(opacity=' + val + ')'; //obj.filters.alpha.opacity = val
}
}
</script>
87d5b97f-c56c-425b-92aa-176a5f70646a|0|.0|96d5b379-7e1d-4dac-a6ba-1e50db561b04
Tags:
C#, Windows
HTML
by joe.pesch
13. February 2009 21:19
d140887a-3453-40dc-8685-cfb501f58f4a|0|.0|96d5b379-7e1d-4dac-a6ba-1e50db561b04
Tags:
C#, Windows
SQL Server
by joe.pesch
11. February 2009 14:27
Error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - Only one usage of each socket address (protocol/network address/port) is normally permitted.)
This error was encountered on a web application running a batch upload of records into a SQL server database. Each iteration in the master batch upload process contained approximately 50+ individual SQL transactions. The issues appears to be that the web server was running out of dynamic ports due to the large volume of individual connections to the SQL server.
http://support.microsoft.com/kb/328476
Adjust the MaxUserPort and TcpTimedWaitDelay settings
Note that the MaxUserPort and TcpTimedWaitDelay settings are applicable only for a client computer that is rapidly opening and closing connections to a remote computer that is running SQL Server and that is not using connection pooling. For example, these settings are applicable on an Internet Information Services (IIS) server that is servicing a large number of incoming HTTP requests and that is opening and closing connections to a remote computer that is running SQL Server and that is using the TCP/IP protocol with pooling disabled. If pooling is enabled, you do not have to adjust the MaxUserPort and TcpTimedWaitDelay settings.
The following changes to the registry key are used to override the default values: HKEY_LOCAL_MACHINE\System\CurrectControlSet\services\Tcpip\Parameters Value Name: MaxUserPort Data Type: REG_DWORD Value: 30000 (Decimal) Value Name: TcpTimedWaitDelay Data Type: REG_DWORD Value: 30 (Decimal)