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.

Microsoft Visual Studio bat and cmd file encoding problems

When you create a bat or cmd file in Microsoft Visual Studio 2008 it will be saved as UTF-8 encoding, but bat files should have ASCII enconding.
Running a bat file starting with @echo off, creates an error:

‘∩╗┐@echo’ is not recognized as an internal or external command, operable program or batch file.

Saving the file as ASCII in Microsoft Visual Studio 2008 solved the problem

System.OutOfMemoryException on SSIS Script Task

I created a SSIS package with a script task in it. The script task created a XML file, but consumed more then 256MB of memory. The default value for the MemToLeave setting.

MemToLeave is virtual address space (VAS) that’s left un-used when SQL Server starts so that external components called by SQL Server are saved some address space. So in order for these technologies, .NET CLR and SSIS, to operate


Event Type:    Error
Event Source:    SSIS Package CDS Rapportage
Event Category:    None
Event ID:    3
Date:        4/21/2009
Time:        12:59:29 PM
User:        N/A
Computer:    NLPRC173N59
Unexpected exception Exception.Message[Exception of type ‘System.OutOfMemoryException’ was thrown.]

For more information, see Help and Support Center at



Setting the MemToLeave to 512MB solved the problem.