April CTP installation failed

I've already installed VSTS 2005 Beta2 and I try to install workstation components of April CTP. What should I try to pass th error?
The error is at the end of installation:

Failed to generate type library 'C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.tlb' for 'Microsoft.SqlServer.MSMQTask, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'.
System.EnterpriseServices

Server stack trace:
at System.EnterpriseServices.RegistrationDriver.InstallAssembly(RegistrationConfig regConfig, Object obSync)

at System.EnterpriseServices.RegistrationHelperTx.InstallAssemblyFromConfig(RegistrationConfig& regConfig, Object sync)

at System.Runtime.Remoting.Messaging.Message.Dispatch(Object target, Boolean fExecuteInContext)

at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
at System.EnterpriseServices.RegistrationThreadWrapper.PropInstallResult()

at System.EnterpriseServices.RegistrationHelper.InstallAssemblyFromConfig(RegistrationConfig& regConfig)

at System.EnterpriseServices.RegistrationHelper.InstallAssembly(String assembly, String& application, String partition, String& tlb, InstallationFlags installFlags)

at System.EnterpriseServices.RegistrationHelper.InstallAssembly(String assembly, String& application, String& tlb, InstallationFlags installFlags)

at Microsoft.SqlServer.Setup.SetupHelper.InstallAssembly(String AssemblyName)
End of Log is:
--
MSI (s) (00:10) [20:06:56:332]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI1A4.tmp, Entrypoint: CommitTransaction
05/17/05 20:06:56 DDSet_Status: LANGID: 1049
05/17/05 20:06:56 DDSet_Entry: CommitTransaction started
05/17/05 20:06:56 DDSet_Status: LANGID: 1049
05/17/05 20:06:56 DDSet_Entry: CMsHelpObject constructor
05/17/05 20:06:56 DDSet_Status: LANGID: 1049
05/17/05 20:06:56 DDSet_Entry: CHelpCrypto constructor
05/17/05 20:06:56 DDSet_Exit: CHelpCrypto destructor
05/17/05 20:06:57 DDSet_Status: CommitTransaction()->IHxRegisterSession::CommitTransaction() returned 0.
05/17/05 20:06:57 DDSet_Status: CommitTransaction()->{90032DD0-ABEE-4424-AC1E-B076BDD4E350} was successfully committed.
05/17/05 20:06:57 DDSet_Exit: CMsHelpObject destructor
05/17/05 20:06:57 DDSet_Exit: CommitTransaction ended
MSI (s) (00:4C) [20:06:57:707]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI1A5.tmp, Entrypoint: Do_sqlAssemblyRegSvcs
<Func Name='LaunchFunction'>
Function=Do_sqlAssemblyRegSvcs
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='0'>
Doing Action: Do_sqlAssemblyRegSvcs
PerfTime Start: Do_sqlAssemblyRegSvcs : Tue May 17 20:06:59 2005
<Func Name='Do_sqlAssemblyRegSvcs'>
Unable to install .NET Framework Service C:\Program Files\Microsoft SQL Server\90\DTS\Tasks\Microsoft.SqlServer.MSMQTask.dll
<EndFunc Name='Do_sqlAssemblyRegSvcs' Return='1603' GetLastError='14007'>
PerfTime Stop: Do_sqlAssemblyRegSvcs : Tue May 17 20:07:55 2005
Gathering darwin properties for failure handling.
Error Code: 1603
MSI (s) (00!3C) [20:08:07:770]: Product: Microsoft SQL Server 2005 Tools CTP -- Error 29635. The setup has encountered an unexpected error while Installing .NET Frameworks Assemblies. The error is : .

Error 29635. The setup has encountered an unexpected error while Installing .NET Frameworks Assemblies. The error is : .

<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='14007'>
Doing Action: Do_sqlAssemblyRegSvcs
PerfTime Start: Do_sqlAssemblyRegSvcs : Tue May 17 20:08:07 2005
--

I am encountering the same error. Does anyone have a solution?

Thx.|||Hi,

I believe that this link can help http://lab.msdn.microsoft.com/vs2005/get/vsbeta2installissues/default.aspx

regards
Nilton

|||Hi,
I ignored the error and the rest of the install proceeded fine. I did have problems with launching Management Studio(see my post here).

These issues may or may not be related. I got this error (the one you refer to) when installing from a copy of the DVD handed out at a seminar. The funny thing is , when i installed from the ISO, i didnt get the error but management studio didnt launch either.

Did you Abort or Ignore the error? Try IGNORE and see what happens?

HTH

Cheers
Benjy|||Actually I really have ignored the error and tools were installed.
Management Studio cannot run. It tries to send an error report to Microsoft. Other tools work fine.
Some info about error can be found in the Application log:

sqlwb.exe, 2000.90.1116.0, msenv.dll, 8.0.50215.44, 0x000a209e.

Error of application ..., version ..., module ..., version ..., address ...

I don't have any workaround. Try to reinstall didn't help.

WBR,
Stone

Anyone used ISql tool

Hi
Has anyone used ISql tool that comes with the windows installation. I'm
trying to run an SQL script using it giving the command
iSql -U user -P password -S server -d Database -i <path to sql script file>
What happens is that it does start executing the script but takes so much
time if the script contains around 100-200 statements. When I execute the
same script using MS SqlServer Managment studio, it executes it all within
2-4 seconds. Is there any way to speed up the process using ISql tool, like
if i'm missing any argument or something. Or if there's any alternative
method to do so. Actually I've to do so from my VC++ code so looking for any
alternative method possible.
Regards
UsmanUsman,
I don't know why isql is that slow, but you shouldn't use it anyway.
Isql is only included for backward compatibility. Better use
sqlcmd.exe.
M

Anyone used ISql tool

Hi
Has anyone used ISql tool that comes with the windows installation. I'm
trying to run an SQL script using it giving the command
iSql -U user -P password -S server -d Database -i <path to sql script file>
What happens is that it does start executing the script but takes so much
time if the script contains around 100-200 statements. When I execute the
same script using MS SqlServer Managment studio, it executes it all within
2-4 seconds. Is there any way to speed up the process using ISql tool, like
if i'm missing any argument or something. Or if there's any alternative
method to do so. Actually I've to do so from my VC++ code so looking for any
alternative method possible.
Regards
UsmanUsman,
I don't know why isql is that slow, but you shouldn't use it anyway.
Isql is only included for backward compatibility. Better use
sqlcmd.exe.
M

Anyone use Litespeed?

I attempted installing yesterday on a cluster, and the installation
went fine, but when I kicked off the backup via Litespeed, I received
the following error...
[Microsoft][SQL Native Client][SQL Server]Failed to create the security
environment for VDI. Ensure that the SQL Server Service account has
administrator access to this server. Note: Administrator privilege
can be restriced by registry/file and policy changes that can prevent
this operation from succeeding.
The SQL Service acct does have admin rights on the server. I installed
it as someone in the admin group. And I kicked off the backup as an
admin. I'm waiting for a call back from Imceda software on this, but
wanted to see if anyone out there had any ideas.Corey,
Might try making sure the SQL Agent is running under the SYSADMIN fixed
server role and that the domain user account for the SQL Server and SQL
Server Agent services have the necessary permissions to write backup files
to the disk.
HTH
Jerry
"Corey Bunch" <unc27932@.yahoo.com> wrote in message
news:1129206377.601106.49240@.z14g2000cwz.googlegroups.com...
>I attempted installing yesterday on a cluster, and the installation
> went fine, but when I kicked off the backup via Litespeed, I received
> the following error...
> [Microsoft][SQL Native Client][SQL Server]Failed to create the security
> environment for VDI. Ensure that the SQL Server Service account has
> administrator access to this server. Note: Administrator privilege
> can be restriced by registry/file and policy changes that can prevent
> this operation from succeeding.
> The SQL Service acct does have admin rights on the server. I installed
> it as someone in the admin group. And I kicked off the backup as an
> admin. I'm waiting for a call back from Imceda software on this, but
> wanted to see if anyone out there had any ideas.
>|||The account for the agent is a local administrator, and it always
writes it native backups to the same spot, so still not sure why
Litespeed isn't working. I installed on a standalone server (not a
cluster) in the same domain, and pointed to the same backup loaction,
and everything worked. I've got a ticket in with Imceda, so I'll write
back with the results/findings.
Jerry Spivey wrote:
> Corey,
> Might try making sure the SQL Agent is running under the SYSADMIN fixed
> server role and that the domain user account for the SQL Server and SQL
> Server Agent services have the necessary permissions to write backup files
> to the disk.
> HTH
> Jerry
> "Corey Bunch" <unc27932@.yahoo.com> wrote in message
> news:1129206377.601106.49240@.z14g2000cwz.googlegroups.com...
> >I attempted installing yesterday on a cluster, and the installation
> > went fine, but when I kicked off the backup via Litespeed, I received
> > the following error...
> >
> > [Microsoft][SQL Native Client][SQL Server]Failed to create the security
> > environment for VDI. Ensure that the SQL Server Service account has
> > administrator access to this server. Note: Administrator privilege
> > can be restriced by registry/file and policy changes that can prevent
> > this operation from succeeding.
> >
> > The SQL Service acct does have admin rights on the server. I installed
> > it as someone in the admin group. And I kicked off the backup as an
> > admin. I'm waiting for a call back from Imceda software on this, but
> > wanted to see if anyone out there had any ideas.
> >