Showing posts with label agent. Show all posts
Showing posts with label agent. Show all posts

Friday, March 30, 2012

Problems installing Client tools and BOL

I have tried several times to install SQL Server 2005 Enterprise Edition on a cluster. SQL Server, SQL browser and SQL Agent installs ok but when the installer start to setup Books on line and client tools (BIDS) and SS Management Studio the installer stops and end the installation.

I get this error (from SQLSetup0021_WBOGSQL01_Core(Local).log)

Remote setup(s) are ready
Notify package to begin: 29539
Notify package to commit: 29539
Waiting for remote setup(s) to get ready to end
Remote setup(s) are ready
Notify package to end: 29539
Error: Action "UninstallForRS2000Action" failed during execution. Error information reported during run:
Action: "UninstallForRS2000Action" will be marked as failed due to the following condition:
Condition "rs was successfully upgraded." returned false.
Installation of package: "patchRS2000" failed due to a precondition.
Waiting for actions from remote setup(s)
Remote setup(s) are ready
Notify package action is determined: 0
Running: InstallToolsAction.10 at: 2006/6/23 2:3:42
Error: Action "InstallToolsAction.10" threw an exception during execution. Error information reported during run:
Target collection includes the local machine.
Fatal Exception caught while installing package: "10"
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.

Source File Name: sqlchaining\sqlprereqpackagemutator.cpp
Compiler Timestamp: Tue Aug 9 01:14:20 2005
Function Name: sqls::SqlPreReqPackageMutator::modifyRequest
Source Line Number: 196

- Context --
sqls::InstallPackageAction::perform
sqls::InstallPackageAction::getReferringPackageId
ch::installA
WinException caught while installing package. : 1603
Error Code: 0x80070643 (1603)
Windows Error Text: Fatal error during installation.

Source File Name: packageengine\installpackageaction.cpp
Compiler Timestamp: Fri Jul 1 01:28:25 2005
Function Name: sqls::InstallPackageAction::perform
Source Line Number: 167

- Context --
sqls::InstallPackageAction::perform
sqls::InstallPackageAction::getReferringPackageId
ch::installA
Cancelling setup due to failure on remote machine: 1603
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0021_WBOGSQL01_.NET Framework 2.0.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0021.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0021_WBOGSQL01_.NET Framework 2.0 LangPack.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0021.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0021_WBOGSQL01_.NET Framework Upgrade Advisor.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0021.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0021_WBOGSQL01_.NET Framework Upgrade Advisor LangPack.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0021.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0021_WBOGSQL01_.NET Framework Windows Installer.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0021.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0021_WBOGSQL01_.NET Framework Windows Installer LangPack.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0021.cab" Error Code : 2
Running: UploadDrWatsonLogAction at: 2006/6/23 2:6:2
Message pump returning: 1603

Why does the installation process stop there and what can I do next?

Best regards

Andres

See this article but it hasn't solved the problem for me.

http://support.microsoft.com/?kbid=916760

Wednesday, March 21, 2012

Problems Connect a Network Drive with SQL Server Agent

Hello
I have MS SQL 7.00.1094 on NT 4.0
When I connect a Network Drive (net use.../User:local User
on Remote System) with SQL Server Agent I cannot access
this.
If I take the same command on the desktop (Command Shell)
the access is o.K.
The SQL Server Agent is started with the same Account as I
logged on locally.
Even I connect a network drive z.B. U: local, I can not
access this from SQL Server Agent though is the same
global user.
But this Problem exist only 7 days ago.
Thanks
MartinDid someone add a proxy account to the SQL agent? Go to Enterprise Manger
and check the properties for SQL server agent | Job System tab. You should
verify then that you can map the drive with the proxy account.
****************************************
***************************
Andy S.
MCSE NT/2000, MCDBA SQL 7/2000
andymcdba1@.NOMORESPAM.yahoo.com
Please remove NOMORESPAM before replying.
Always keep your antivirus and Microsoft software
up to date with the latest definitions and product updates.
Be suspicious of every email attachment, I will never send
or post anything other than the text of a http:// link nor
post the link directly to a file for downloading.
This posting is provided "as is" with no warranties
and confers no rights.
****************************************
***************************
"Martin" <anonymous@.discussions.microsoft.com> wrote in message
news:106b801c3f46d$5ee8bef0$a301280a@.phx
.gbl...
> Hello
> I have MS SQL 7.00.1094 on NT 4.0
> When I connect a Network Drive (net use.../User:local User
> on Remote System) with SQL Server Agent I cannot access
> this.
> If I take the same command on the desktop (Command Shell)
> the access is o.K.
> The SQL Server Agent is started with the same Account as I
> logged on locally.
> Even I connect a network drive z.B. U: local, I can not
> access this from SQL Server Agent though is the same
> global user.
> But this Problem exist only 7 days ago.
> Thanks
> Martin|||A service, such as SQL Server Agent, is not supposed to be able to see
mapped drives. You should use a URL from a service.
180362 INFO: Services and Redirected Drives
http://support.microsoft.com/?id=180362
Cindy Gross, MCDBA, MCSE
http://cindygross.tripod.com
This posting is provided "AS IS" with no warranties, and confers no rights.