Data Services 4.0 Designer. Job Execution but empty log file no matter what

[Former Member]

Hi all,

am running DS 4.0. When i execute my batch_job via designer, log window pops up but is blank. i.e. cannot see any trace messages.

doesn't matter if i select "Print all trace messages" in execution properties.

Jobserver is running on a seperate server. The only thing i have locally is just my designer.

if i log into the Data Services management console and select the job server, i can see trace and error logs from the job. So i guess what i need is for this stuff to show up in my designer?

Did i miss a step somewhere?

can't find anything in docs about this.

thanks

Edited by: Andrew Wangsanata on May 10, 2011 11:35 AM

Added additional detail

[Former Member]

Hi Andrew,

I am facing same issue. Did you please tell me how you resolved this ?

Brief: Job is running successfully but cannot see the logs in DI monitor. Same behaviour is on DI server as well. I have job server on DI server only.

Regards,

Rishit

[Former Member]

I managed to resolve this issue. What I noticed Is during
the installation two folders to keep the logs were created. The other one is
empty and the other one keep all the logs when the jobs run, but the Designer
is reading from an empty folder.

LOG PATH:

C:\ProgramData\SAP BusinessObjects\Data Services\log\JOBSERVER\DATABASE
SERVER_REPOSITORYDATABASE_USER NAME

Where  :JOBSERVER= yor save name on the Data services manager

              : DATABASESERVER = database server of the local repository database

              : REPOSITORYDATABASE = repository database

              : Database USER NAME= SQL log user name

My resolution: I went to Data services manager  click on Configuration
Editor

This will open  the
Job server configuration editor, select your Jobserver and click on delete.

After deleting you will have to Create a new Jobserver which
will match the Log path… in my case my logs were saved in this path:

C:\ProgramData\SAP BusinessObjects\Data
Services\log\JobServer_1\localhost_sqlexpress_repo_sa

Use the last folder to create your Jobserver:  localhost_sqlexpress_repo_sa

Now create
your Jobserver with the same name, and the below configuration this should
always match yours

Database server name:localhost\sqlexpress

Database Name:repo

UserName: sa

[Former Member]

the log file a read from Job server

check the job server log file (server_event log ) located in %LINK_DIR%\log folder

do you see any errors ?

[Former Member]

Hi Manoj,

Thanks. I know where the log files are on the job server and can see they are being populated. This is not the issue.

My issue is that the log doesn't stream in the designer like it normally does. Is this not possible if the designer is not local to the Job Server?

thanks

/andrew

[Former Member]

Hi Manoj,

Thanks. I know where the log files are on the job server and can see they are being populated. This is not the issue.

My issue is that the log doesn't stream in the designer like it normally does. Is this not possible if the designer is not local to the Job Server?

thanks

[Former Member]

not the job log files, the log files are displayed in Designer by sending a request to JobServer and jobServer send the data (log file content) to the Designer, this communcation requires sockets its possible that some ports on Designer machine are blocked or firewall issues etc, which is unlikely since you are able to run the job from Designer

if there is any error in this communication that will be logged in the %LINK_DIR%\log\<JobServerName>\server_eventlog_<date>.txt file, check this file if there are any errors logged

the Designer wll show the log file from remote JS also as soon as you start the Job from Designer

[Former Member]

awesome. Thanks Manoj

I found the log file. in it relevant lines for last job i ran are

(14.0) 05-11-11 16:52:27 (2272:2472) JobServer:  Starting job with command line -PLocaleUTF8 -Utip_coo_ds_admin 
                                                -P+04000000001A030100100000328DE1B2EE700DEF1C33B1277BEAF1FCECF6A9E9B1DA41488E99DA88A384001AA3A9A82E94D2D9BCD2E48FE2068E59414B12E
                                                48A70A91BCB  -ek********  -G"70dd304a_4918_4d50_bf06_f372fdbd9bb3" -r1000 -T1073745950  -ncollect_cache_stats 
                                                -nCollectCacheSize  -ClusterLevelJOB  -Cmxxx -CaDesigner -Cjxxx -Cp3500 -CtBatch  -LocaleGV 
                                                -BOESxxx.xxx.xxx.xxx -BOEAsecLDAP -BOEUi804716
                                                -BOEP+04000000001A0301001000003F488EB2F5A1CAB2F098F72D7ED1B05E6B7C81A482A469790953383DD1CDA2C151790E451EF8DBC5241633C1CE01864D93
                                                72DDA4D16B46E4C6AD -Sxxx.xxx.xxx -NMicrosoft_SQL_Server -Qlocal_repo  coo ds local
                                                repo_azdzgq4dnuxbm4xeriey1_e" -l"C:\Program Files (x86)\SAP BusinessObjects\Data Services/log/js01/tip coo ds local
                                                repo_azdzgq4dnuxbm4xeriey1_e/trace_05_11_2011_16_52_27_9__70dd304a_4918_4d50_bf06_f372fdbd9bb3.txt" -z"C:\Program Files
                                                (x86)\SAP BusinessObjects\Data Services/log/js01/tip coo ds local
                                                repo_azdzgq4dnuxbm4xeriey1_e/error_05_11_2011_16_52_27_9__70dd304a_4918_4d50_bf06_f372fdbd9bb3.txt" -w"C:\Program Files
                                                (x86)\SAP BusinessObjects\Data Services/log/js01/tip coo ds local
                                                repo_azdzgq4dnuxbm4xeriey1_e/monitor_05_11_2011_16_52_27_9__70dd304a_4918_4d50_bf06_f372fdbd9bb3.txt" -Dt05_11_2011_16_52_27_9
                                                (BODI-850052)
(14.0) 05-11-11 16:52:27 (2272:2472) JobServer:  StartJob : Job '05_11_2011_16_52_27_9__70dd304a_4918_4d50_bf06_f372fdbd9bb3' with pid '148' is kicked off
                                                (BODI-850048)
(14.0) 05-11-11 16:52:28 (2272:2072) JobServer:  Sending notification to <inet:10.165.218.xxx:56511> with message type <4> (BODI-850170)
(14.0) 05-11-11 16:52:28 (2272:2472) JobServer:  AddChangeInterest: log change interests for <05_11_2011_16_52_27_9__70dd304a_4918_4d50_bf06_f372fdbd9bb3> from client
                                                <inet:10.165.218.xxx:56511>. (BODI-850003)
(14.0) 05-11-11 17:02:32 (2272:2472) JobServer:  RemoveChangeInterest: log change interests for <05_11_2011_16_52_27_9__70dd304a_4918_4d50_bf06_f372fdbd9bb3> from client
                                                <inet:10.165.218.xxx:56511>. (BODI-850003)
(14.0) 05-11-11 19:57:45 (2272:2468) JobServer:  GetRunningJobs() success. (BODI-850058)
(14.0) 05-11-11 19:57:45 (2272:2468) JobServer:  PutLastJobs Success.  (BODI-850001)
(14.0) 05-11-11 19:57:45 (2272:2072) JobServer:  Sending notification to <inet:10.165.218.xxx:56511> with message type <5> (BODI-850170)
(14.0) 05-11-11 19:57:45 (2272:2472) JobServer:  GetHistoricalLogStatus()  Success. 05_11_2011_16_52_27_9__70dd304a_4918_4d50_bf06_f372fdbd9bb3 (BODI-850001)
(14.0) 05-11-11 19:57:45 (2272:2472) JobServer:  GetHistoricalLogStatus()  Success. 05_11_2011_16_52_27_9__70dd304a_4918_4d50_bf06_f372fdbd9bb3 (BODI-850001)

it does not look like i have any errors with respect to connectivity? ( or any errors at all....)

Please advise on what, if anything you notice from log file and/or next steps i can take.

thanks.

[Former Member]

Hi Andrew,

Were you able to resolve this issue? I am experiencing the same thing.

Thanks,

Lisa