DLL issue when installing SS05 64bit

I uninstalled a 32-bit eval Std Ed SQL Server 2005. I then attempted to install 64bit licensed Std Ed. The database engine and other components install fine, but SSIS is throwing a DLL error (first error following). How can I solve this issue? I have attempted to IGNORE the error, but when I try to run SSIS - I get a DLL error (second error following). All assistance is appreciated.

TITLE: Microsoft SQL Server 2005 Setup

Failed to install and configure assemblies C:\Program Files\Microsoft SQL Server
\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll in the COM+ catalog.
Error: -2146233087
Error message: Unknown error 0x80131501
Error description: One or more of the components being installed are already registered as 32 bit components in the target application. You must install the 64 bit versions of the components being installed in a different COM+ application, or delete the existing 32 bit versions of the components being installed from the target COM+ application prior to attempting install of the 64 bit versions. COM+ applications cannot contain bit neutral components.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=29549&EvtType=sqlca%5csqlassembly.cpp%40Do_sqlAssemblyRegSvcs%40Do_sqlAssemblyRegSvcs%40x80131501

TITLE: Connect to Server

Cannot connect to SERVERNAME.

ADDITIONAL INFORMATION:

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

Connect to SSIS Service on machine "SERVERNAME" failed:
Error loading type library/DLL.

I've seen this issue in the forums a couple times, but haven't been able to repro it on my box. Here is a thread regarding this issue with a few suggestions. Feel free to take a look to see if it pertains to your situation. The people on the thread seem to have a handle on the issue, so they may be able to help out if you get stuck.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=136467&SiteID=1

Thanks,
Sam Lester (MSFT)|||The is in the Component Services in com+ called Microsoft.Sqlserver.MSMQTask. You need to delete that one. After that the install will run just fine.

Theo Ekelmans

Distribution agent action messages in session details

We are using SQL 2K std with SP4 and push subscription. We have situation
between our publishing SQL server and subcribing SQL server.
Here is what I see when I double click an action message (listed as Timeout
Expired) in the listing of Distribution Agent history.
3:24 pm Initializing
3:29 pm The process is running and is waiting for a response from one of
the backend connections.
3:29 pm Timeout expired
The sequence of action took exactly five minutes. And the timeout happened
again at 3:30 pm and last until 3:35 pm. Then at 3:36, it started working
and delivered the transactions.
Can someone tell me what the 'backend connection' the distribution agent is
waiting for?
Also, during this problem period, both publishing and subscribing SQL
servers all of a sudden became activity dead meaning there is no IO and no
SQL internal activity (my perf monitor showed almost a blank screen except
cpu time), the publishing SQL server's cpu time is very minimal but the
subscribing SQL server's cpu is 60% peak and no IO. I checked the proces of
the CPU in Em and it was for replication but it had long wait time. It
looked all a sudden nobody can connect to the SQL servers. In fact, we
confirmed that users can't connect to the web application that use SQL
servers. I don't see any networking error shown in the event log in both
servers. I am assuming there is a 'disconnect' or something is 'hanging', I
like to know if the 'disconnect or hanging' caused the distribution agent to
time out or the distrbitution timeout problem caused the SQL server system to
become 'disconnect or hang'?
wingman
The replication subsystem issues commands and waits for responses. If it
doesn't get a response in a predetermined amount of time it gives the
waiting for a response from one of backend connections.
I can't explain why no-one could connect - perhaps the database or tlog was
auto-growing at that time.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:76F91F8B-925F-4152-9C2D-ACB9EA89FCD5@.microsoft.com...
> We are using SQL 2K std with SP4 and push subscription. We have situation
> between our publishing SQL server and subcribing SQL server.
> Here is what I see when I double click an action message (listed as
> Timeout
> Expired) in the listing of Distribution Agent history.
> 3:24 pm Initializing
> 3:29 pm The process is running and is waiting for a response from one of
> the backend connections.
> 3:29 pm Timeout expired
> The sequence of action took exactly five minutes. And the timeout
> happened
> again at 3:30 pm and last until 3:35 pm. Then at 3:36, it started working
> and delivered the transactions.
> Can someone tell me what the 'backend connection' the distribution agent
> is
> waiting for?
> Also, during this problem period, both publishing and subscribing SQL
> servers all of a sudden became activity dead meaning there is no IO and no
> SQL internal activity (my perf monitor showed almost a blank screen except
> cpu time), the publishing SQL server's cpu time is very minimal but the
> subscribing SQL server's cpu is 60% peak and no IO. I checked the proces
> of
> the CPU in Em and it was for replication but it had long wait time. It
> looked all a sudden nobody can connect to the SQL servers. In fact, we
> confirmed that users can't connect to the web application that use SQL
> servers. I don't see any networking error shown in the event log in both
> servers. I am assuming there is a 'disconnect' or something is 'hanging',
> I
> like to know if the 'disconnect or hanging' caused the distribution agent
> to
> time out or the distrbitution timeout problem caused the SQL server system
> to
> become 'disconnect or hang'?
> wingman
>
>
|||Is it a good idea to increase the query timeout from 300 seconds (default) to
maybe 600 seconds in Distribution Agent profile to accomendate any potential
long running process?
Wingman
"Hilary Cotter" wrote:

> The replication subsystem issues commands and waits for responses. If it
> doesn't get a response in a predetermined amount of time it gives the
> waiting for a response from one of backend connections.
> I can't explain why no-one could connect - perhaps the database or tlog was
> auto-growing at that time.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Wingman" <Wingman@.discussions.microsoft.com> wrote in message
> news:76F91F8B-925F-4152-9C2D-ACB9EA89FCD5@.microsoft.com...
>
>
|||QueryTimeout is more often used in merge replication than in transactional
replication. I normally set the inactivity level to something higher, but
this could mask other problems.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Wingman" <Wingman@.discussions.microsoft.com> wrote in message
news:649BE7BF-C83E-44DC-8B8A-BD5A498510CB@.microsoft.com...[vbcol=seagreen]
> Is it a good idea to increase the query timeout from 300 seconds (default)
> to
> maybe 600 seconds in Distribution Agent profile to accomendate any
> potential
> long running process?
> Wingman
>
> "Hilary Cotter" wrote: