Can't Execute Package from BIDS Solution Explorer Post SP2 Install

Yesterday, SQL Server 2005 SP2 was installed on our DEV Server (Windows 2003 SP1 x86) and now I cannot right-click a package in the Solutions Explorer window in BIDS and Execute Package. When I do, I get the following error

===================================

Object reference not set to an instance of an object. (Microsoft Visual Studio)

Program Location:

at Microsoft.DataTransformationServices.Project.DtsPackagesFolderProjectFeature.ExecuteTaskOrPackage(ProjectItem prjItem, String taskPath)

I know I could do this yesterday morning pre SP2. I've attempted this with a couple of different packages and solutions, so it is probably not a corrupt package (unless now they are all corrupt). I can execute in debug mode if I open the package first and then hit Start Debugging. However this is not always an optimal solution because I sometimes have many connected packages and sometimes what gets executed is not what is expected.

Your thoughts would be appreciated.

I'm having the identical problem. If I create a new package, it will work for a short period of time. I didn't measure the time precisely, but it is within 15 minutes and an hour or so. I appreciate your run-in-debug solution, but it is still not a clean fix.sql

Can't create a new FT Catalog

Hi
We are having a problem creating a Full-Text catalog on our production
server and would appreciate any pointers to a solution.
The scenario is as follows:
1. Existing version of product running perfectly happily on production
server with Full Text indexing enabled and running. Lets call it Server 1
(Running SQL 2000 stndard sp3 on W2K Server )
2. New product developed on development server (Server 2). Full-text
indexing enabled and running.
3. Database transferred from Server 2 to Server 1 using DTS
4. Attempted to create FT catalog on new database on Server 1 using
Enterprise Manager. Failed, error given is:
An unknown full-text failure (80004005) occurred in function EnumCatalogs on
full-text catalog
Meanwhile it is still possible to create a new FT catalog on the existing db
(still on server 1)
We have done the usual web-searching to find a solution but anything turned
up appears to address the issue that it is impossible to create a FT catalog
on the server, this isn't our case, our problem is that we can't create the
FT index on the new db.
Any ideas?
Also if you need more info please ask.
Regards
Russell Wyatt
have you referred to this kb article yet?
http://support.microsoft.com/default...b;en-us;295772
"Russell Wyatt" <russellw_REMOVE_THIS_TO_REPLY_@.ihs.com.au> wrote in message
news:%23VcY80SxEHA.2172@.TK2MSFTNGP14.phx.gbl...
> Hi
> We are having a problem creating a Full-Text catalog on our production
> server and would appreciate any pointers to a solution.
> The scenario is as follows:
> 1. Existing version of product running perfectly happily on production
> server with Full Text indexing enabled and running. Lets call it Server 1
> (Running SQL 2000 stndard sp3 on W2K Server )
> 2. New product developed on development server (Server 2). Full-text
> indexing enabled and running.
> 3. Database transferred from Server 2 to Server 1 using DTS
> 4. Attempted to create FT catalog on new database on Server 1 using
> Enterprise Manager. Failed, error given is:
> An unknown full-text failure (80004005) occurred in function EnumCatalogs
> on
> full-text catalog
> Meanwhile it is still possible to create a new FT catalog on the existing
> db
> (still on server 1)
> We have done the usual web-searching to find a solution but anything
> turned
> up appears to address the issue that it is impossible to create a FT
> catalog
> on the server, this isn't our case, our problem is that we can't create
> the
> FT index on the new db.
> Any ideas?
> Also if you need more info please ask.
> Regards
> Russell Wyatt
>
|||Thanks Hilary
Yes, we have referred to the article. (I say "we" because my colleague and
myself are trying to solve the problem). However, we can create a full-text
catalog on a different (already existing) database just not on the new one.
So catalog creation isn't completely broken, just for new databases. AFAIK
the kb article is useful if catalog creation doesn't work at all.
Russell
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:eBqVoSTxEHA.2624@.TK2MSFTNGP11.phx.gbl...
> have you referred to this kb article yet?
> http://support.microsoft.com/default...b;en-us;295772
> "Russell Wyatt" <russellw_REMOVE_THIS_TO_REPLY_@.ihs.com.au> wrote in
message[vbcol=seagreen]
> news:%23VcY80SxEHA.2172@.TK2MSFTNGP14.phx.gbl...
1[vbcol=seagreen]
EnumCatalogs[vbcol=seagreen]
existing
>