Website URL shows router admin page from inside internal network

If you have a domain like or and host these websites on you’re own server. The websites will show the router admin page from inside you’re network.
Changing the windows host file in C:\Windows\System32\drivers\etc, routing the internal ip adres lets say to solves the problem.



The host file on all client pc’s on you’re internal network should look like this:




Setup the US Robotics USR5436 Wireless USB Print Server on Vista x64

I had some trouble installing the US Robotics USR5436 Wireless USB Print Server on a Vista x64 laptop.


During the “User” setup I encountered an err = 1805 AddMonitor Fail error.


During the printer driver port setup, I encountered a AddPort fail error.


However there where 2 ports installed (USB001 Virtual printer port for USB and USB002 Virtual printer port for USB).
Using these port resulted in an error trying to print a test page, but using a TCP/IP port worked for me.

Here is the complete list of steps:
> Connect the US Robotics USR5436 Wireless USB Print Server to an wired UTP cable
> Connect the US Robotics USR5436 Wireless USB Print Server to the printer with an USB cable
> Turn on the printer
> Connect the US Robotics USR5436 Wireless USB Print Server to a standard power outlet
> Download
> Extract the zip and run the Autorun.exe
> Click Setup Wizard
> During the setup wizard the ip address of the print server will be shown, write it down.
> Add a printer:
> Start > Control Panel > Printers > Add Printer > Add a local printer


> Check Create a new port and select Standard TCP/IP Port


> Enter the IP address (written down during setup)


> Select Generic network card

> Select you’re printer driver
> The rest of the wizard is “Next Next Finish”

Conclusion: don’t use the USB001 and USB002 ports, just create you’re own TCP/IP port and the printer will just work fine under Windows Vista x64

Check if table has an identity column "id" – TSQL

declare @tablename varchar(100)

set @tablename = ‘Product’

if exists (select 1 from sys.columns sc inner join sys.objects so on so.Object_Id = sc.Object_Id where = ‘Id’ and sc.is_identity = 1 and so.Type = ‘U’ and so.Name = @tablename)


  print ‘Table has an identity column named id’


This can be used to determine if the reseed function can be called on a table.

Stop all MOSS 2007 services

To stop all Microsoft Sharepoint Services 2007 – Windows Services, create a bat file and enter the following lines:

net stop “SPTimerV3”
net stop “SPAdmin”
net stop “SPTrace”
net stop “SQLWriter”
net stop “OSearch”

Error on calling stored procedure with LLBLGen Pro {"The ConnectionString property has not been initialized."}

When you get the error {“The ConnectionString property has not been initialized.”} on calling a stored procedure with LLBLGen Pro, you probably forgot to set the parameter “DataAccessAdapter adapter” on you’re LLBLGen Pro methode call:

RetrievalProcedures.MyStoreProcedure(param1, param2, dataAccessAdapter);

if you call the function like RetrievalProcedures.MyStoreProcedure(param1, param2); you will get the error {“The ConnectionString property has not been initialized.”}

SQL Server Stored Procedure with temp table select, does not return correct result in LLBLGen Pro

When you create a stored procedure like:

if exists (select 1 from sysobjects where name = 'GetDataFromTempTable' and xtype = 'p')
    drop procedure [dbo].[GetDataFromTempTable]

create procedure [dbo].[GetDataFromTempTable]

-- Create temp table
create table #MyTempTable
    [Id] int not null primary key,
    [Nummer] varchar(10) not null

insert #MyTempTable ([Id], [Nummer]) values (1, 'Test1')

-- Return all rows from the temp table



and generate code with LLBLGen Pro to call this stored procedure,
it will generate an Action Stored Procedure Call instead off a Retrieval Stored Procedure Call.
This is, because LLBLGen Pro by default automatically generates the return type. see

By changing the user preference AutoDetermineSProcType to false, you can manually change the amount of result sets during the catalog refresh.

Change AutoDetermineSProcType
LLBLGen Pro > File > Preferences… > AutoDetermineSProcType > set to false

Refresh catalog
LLBLGen Pro > Project > Refresh All Catalogs… > Manually select the stored procedures to retrieve
> New number of Resultsets for selected procedures > set to 1

The stored procedure can now be added to Retrieval Stored Procedure Calls instead of Action Stored Procedure Calls.