Global Label Management

[Former Member]

Hello,

I have created a material, complated lable view

and done all customization req for GLM

now when i am trying to print label via CBGL_MP01 - Label Printing

WWI server is UP and Running...

i am getting following error

Error on WWI server SERVER_IE6_812_1: Results file not found

Message no. C$830

Diagnosis

The results file of the generation was not found on the WWI server SERVER_IE6_812_1.

System Response

Generation was not carried out.

Procedure

Advise your system administrator to check the WWI installation on the WWI server SERVER_IE6_812_1.

Check the Windows event log on the WWI generation server. The event log may contain other error messages.

SAP Note 1058521 provides possible solutions for this error.

Please note that "SERVER_IE6_812_1" is my WWI Server.

RFC name also SERVER_IE6_812_1

Please guide me in this regard.

Amol Joshi

[Former Member]

Hello Amol,

As mentioned in the error log, please access SAP Note numbered 1058521, it contains the information on what are the possible reasons.

Read the section titled - C$ 830 Error on WWI server &1: Results file not found, under the SAP Note.

Thanks

Jayakumar

[Former Member]

Hi Jayakumar,

Firstly thanks for the quick reply.

as mentioend by you I am checking the sap note 1058521.

meanwhile i have cheked the error log which is as below

I000 C:\Program Files\EHS\WWI\wwi_genserver_sh1_syn\l00000000000000000023.doc

I000 28.01.2010

I000 10:26:25

I000 Resolve-DLL : 3.2 / 2.7B SP18; 2005,110,96,345; C:\Program Files\EHS\WWI\WWIRES32.dll; 19.09.2008 12:15

I000 Configuration : C:\Program Files\EHS\WWI\WWI.INI

I000 GLM Labeling : 3.2 / 2.7B SP18; 1,0,54,1; C:\Program Files\EHS\WWI\WwiLabel.dll; 19.09.2008 12:15

E615 Report Type 'EHS_REPORT' not supported by GLM.

I000 10:26:26

I think E615 Report Type 'EHS_REPORT' not supported by GLM. this is the problem?

could you pleas guide me how to resolve this?

Regards,

Amol

[Former Member]

Hello,

As mentioned by you, I have cheked SAP note no 1058521. and follwing the result..

1. Analyze the WWI logs in the Windows event display in the SAP application log (transaction SLG1, object EHRE) during the report body generation or in the flow trace during report shipping.

--> checked in SLG1. NO error

2.Check whether a process "WinWord.Exe" hangs on the WWI server. Terminate this in the task manager on the WWI server. See Note 788573

--> checked. "WinWord.Exe" file is not running in Task Manager on WWI server.

3.Check the printer configuration on the WWI server. See Note 788573

--> In this note actually Printer Config is NOT given. This note is all about genearl setting..which I have done.

4. Check the macro security in Microsoft Word as described in Note 549858.

Error messages that refer to "Word8_MacroStart" or "Word8_AttachTemplate" indicate this problem.

--> Micro Security is checked. I have set it to LOW

5.Check the Distributed Component Object Model (DCOM) authorizations as described in Note 580607. The error "CreateDispatch failed: Access denied" or "Error: Word8_Initialize(): Exception from CreateDispatch: Access denied" in the WWI log indicates this problem.

--> As mentioend above, I am NOT getting "Error: Word8_Initialize(): Exception from CreateDispatch: Access denied" in the WWI log. so this is not relevet for my problem

but still I have cheked the sttings.. DCOM is not installed. but the solution mentioend in the note is not working. Paths and tabs they have mentioned in the note, I am not able to find in my system.

6.Check the entries C$ 835 Error file in log in CG5Z and the .ERR generation file on the WWI server for error messages.

--> in CG5z, there is no LOG entry.

7.Refer to Note 744096 if you are printing or shipping inbound documents.

--> check this note. all setting are correct

8. This error can also occur due to an incorrect report template. Check for table nesting errors in the relevant report templates, as described in Note 1145017.

--> report template is correct. I have cheked the template. there is no error in systax.

9. This error may be caused by a value that is too low for WordTimeout. See Note 788573.

The system issues the following message in the WWI log:

"Error process winword.exe had to be kill! (Process XXX was killed, timeout of XXX sec was reached!)"

--> i have set timelimit to 180 sec in WWI.INI.

Could you please guide me, now How should you progress to resolve this problem.

Regards,

Amol

[SujitKumar]

Hi Amol,

I am facing also a similar issue in EHS . Have you resolved the issue . If yes can you let me know how.

[former_member212503]

Hello Amol,

I did a lot of troubleshoot for this issue but was not able to get a clue .

Regards,

M D