Showing posts with label launch. Show all posts
Showing posts with label launch. Show all posts

Tuesday, March 27, 2012

Failed to launch 'osql'

I use one-way Transactional Replication on 38 servers with same configuration.
On one server I have problem with OSQL.EXE path.

On
Publication properties ->
snapshot ->
Additional scripts ->
Before applying the snapshot, execute this script:
Is set preinit script (C:\ReplData\ReplPreInit.sql).

On Distribution agent properties -> step "Run Agent"
I set additional command for log problem.
command= -Output C:\ReplOutFile.txt -Outputverboselevel 2

Here is part of ReplOutFile.txt:
--
The osql command is: "C:\Program Files\Microsoft SQL Server\80\Tool\Binn\osql.exe" -U"***" -P"***" -i "\\STROSBB\ReplData\unc\STROSBB_antikor_DataCDB\20060908104051\ReplPreInit_0.sql" -S "BTSVR" -d "AntikorCDB" -o "C:\WINNT\TEMP\ReplPreInit_0.sql_20060912150416.log" -b -X1
Launching osql to apply the script 'ReplPreInit_0.sql'
[9/12/2006 3:04:16 PM]STROSBB.distributionAntikor: {call sp_MSadd_distribution_history(1, 3, ?, ?, 0, 0, 0.00, 0x00, 1, ?, 0, 0x01, 0x00)}
Agent message code 20130. Failed to launch 'osql'
[9/12/2006 3:04:16 PM]STROSBB.distributionAntikor: {call sp_MSadd_distribution_history(1, 6, ?, ?, 0, 0, 0.00, 0x01, 1, ?, 4, 0x01, 0x01)}
Adding alert to msdb..sysreplicationalerts: ErrorId = 1233,
Transaction Seqno = 00000491000618f4007000000001, Command ID = 4
Message: Replication-Replication Distribution Subsystem: agent STROSBB-antikor-BTSVR-1 failed. Failed to launch 'osql'[9/12/2006 3:04:16 PM]STROSBB.distributionAntikor: {call sp_MSadd_repl_alert(3, 1, 1233, 14151, ?, 4, N'STROSBB', N'antikor', N'BTSVR', N'AntikorCDB', ?)}
ErrorId = 1233, SourceTypeId = 3
ErrorCode = '3'
ErrorText = 'The system cannot find the path specified.
--

Problem is that the path to osql command in log ReplOutFile.txt is
C:\Program Files\Microsoft SQL Server\80\Tool\Binn\
but SQL is installed on path
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\

Diferences is between Tool vs. Tools

I think that when server create OSQL command for preinit sql script he use STATIC path to osql.exe and there is my problem.

Where is this path stored and can I change it?

Hi Marco, the osql path was constructed based on the value of HKLM\Software\Microsoft\Microsoft SQL Server\80\ClientSetup\SQLPath (+"\Binn\osql.exe") so you may want to check whether the registry value correctly reflects how SQL Server is set up on the machine where the distribution agent is running.

-Raymond

|||

In my server was registry path:

HKLM\Software\Microsoft\Microsoft SQL Server\80\Tools\ClientSetup\SQLPath

Many Thanks.

Friday, February 24, 2012

Extremely critical. problems with OLAP SERVER (sorry)

I am so sorry fot insist this way, such be a pain, i know but it is very
critical.
A lot!
When I launch my routine from our back-end vb appears this:
Cannot open connection to Analysis server 'BUESSQL01'.
Error in data [Possible data corruption] ''
..
Set m_dsoServer = New DSO.Server
m_dsoServer.Connect m_strMDSERVER
What is happening?
-That servers is reached via PING.
-OLAP services are up and running.
-OLAP server belong to NT domain.
-User which is being responsible for that (via vb code) belong to NT Domain.
?
Any help will be welcomed.
Thanks,1. Ping is against a different service, so it has nothing to do.
2. Service running and database corruption are two different things
3. Domain membership does not appear to be the problem here (database or use
r)
It does not appear that you have an authentication issue, based on your
post. I would check your analysis services database and make sure it is not
corrupt. If it is, no amount of tinkering will help.
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***************************
Think Outside the Box!
***************************
"Enric" wrote:

> I am so sorry fot insist this way, such be a pain, i know but it is very
> critical.
> A lot!
>
> When I launch my routine from our back-end vb appears this:
> Cannot open connection to Analysis server 'BUESSQL01'.
> Error in data [Possible data corruption] ''
> ..
> Set m_dsoServer = New DSO.Server
> m_dsoServer.Connect m_strMDSERVER
>
> What is happening?
> -That servers is reached via PING.
> -OLAP services are up and running.
> -OLAP server belong to NT domain.
> -User which is being responsible for that (via vb code) belong to NT Domai
n.
> ?
> Any help will be welcomed.
> Thanks,
>|||Have you changed your password lately? I have seen this error when I change
my network password but still have an open connection (remote) with the old
password. If this is the case logoff and login again.
"Enric" <Enric@.discussions.microsoft.com> wrote in message
news:6FA71B2A-BCD6-4475-946A-8DBE80640272@.microsoft.com...
>I am so sorry fot insist this way, such be a pain, i know but it is very
> critical.
> A lot!
>
> When I launch my routine from our back-end vb appears this:
> Cannot open connection to Analysis server 'BUESSQL01'.
> Error in data [Possible data corruption] ''
> ..
> Set m_dsoServer = New DSO.Server
> m_dsoServer.Connect m_strMDSERVER
>
> What is happening?
> -That servers is reached via PING.
> -OLAP services are up and running.
> -OLAP server belong to NT domain.
> -User which is being responsible for that (via vb code) belong to NT
> Domain.
> ?
> Any help will be welcomed.
> Thanks,
>