Diagnosis
The cause of the error cannot be determined exactly.
A service in the old format may exist, for which in the new format noentries for the service itself but entries for subobjects exist. Thismay happen when transports with subobjects have been imported into thesystem, but not the service itself.

Procedure
The errors need not be corrected during the upgrade.
If you do not use an ITS (Internet Transaction Server), the productiveoperation is not hindered. Productive operation is not hindered eitheras long as you only use standalone ITS installations. Only as of Basisrelease 6.40 the ITS is available as part of the application server, soall installations up to that release are always standalone ITSinstallations.
A check and, if necessary, error correction is necessary only before youuse the ITS as part of the application server with one of the defectiveservices or before you publish or further develop one of the defectiveInternet services.
Error Analysis and Correction:
The messages below (expand the log further) inform you about theservices concerned. On development systems, you can use transactionSIAC1 to display an overview of the services in the old format and tryto convert them into the new format. Note that you can ignore allobjects that still exist in the old format unless they belong to one ofthe services explicitly marked as defective or to your own developments.
The report SIAC_XPRA_CONVERT_FROM_4X_70 can be started again after theupgrade. However, after a complete run no changes are to be expected.