On 5/14/2019 6:14 AM, kuronen wrote:
>
> I have MS SQL Server driver in the latest Designer (CentOS 7 x86_64).
>
> When I try to export the driver the to an XML file I get the first
> prompt for the server to use for exporting but after that the prompt
> windows disappears and nothing happens. It goes back to the state where
> it was before export action as if nothing was done. It is not stuck nor
> indicating anything, all is responsive and usable.
>
> Other drivers do export well. This driver can be exported to XML file if
> i import the driver set into a new project and export it from there.
>
> I tried running startdesigner.sh from console but got nothing new there.
> Tried doubling the heal sized but no help. I re-checked packages and
> they are all up-to-date. However I am running version control and I have
> a little suspicions that it is messing things up but no evidence of any
> kind to support that hunch.

Turn on the Error view, and see if anything shows up in there.

Trace in Designer with all options / addons turned on only produced XML processor tracing but without that zero output. Or is there another error view besides the trace log in Designer?

It seems that somehow that driver configuration is messed up. When I look at driver - properties - driver configuration - driver parameters I see only driver options tab and no subscriber / publisher channel tabs. GUI shows me some driver options but separated by several empty lines as if Designer could not interpret all of the the XML. If I go to XML edit and come back to GUI i get a duplicate driver options tab. If i repeat it i get another driver options tab appears. I cross checked the options XML to an identical driver and it is precisely same. If I copy paste the options XML from the working identical driver I just get another driver options tab.

This driver was made by duplicating the identical driver from it's XML export. Maybe that process is not fool proof after all?

On 5/15/2019 12:54 AM, kuronen wrote:
>
> Trace in Designer with all options / addons turned on only produced XML
> processor tracing but without that zero output. Or is there another
> error view besides the trace log in Designer?

If you are in a later Designer (like 4.5 or higher) in the upper right
corner is a text entry spot. Type error and open the errror log that
pops up as an option. Not the trace you are looking at.


> It seems that somehow that driver configuration is messed up. When I
> look at driver - properties - driver configuration - driver parameters I
> see only driver options tab and no subscriber / publisher channel tabs.
> GUI shows me some driver options but separated by several empty lines as
> if Designer could not interpret all of the the XML. If I go to XML edit
> and come back to GUI i get a duplicate driver options tab. If i repeat
> it i get another driver options tab appears. I cross checked the options
> XML to an identical driver and it is precisely same. If I copy paste the
> options XML from the working identical driver I just get another driver
> options tab.
>
> This driver was made by duplicating the identical driver from it's XML
> export. Maybe that process is not fool proof after all?
>
>

On 5/15/2019 12:54 AM, kuronen wrote:
>
> Trace in Designer with all options / addons turned on only produced XML
> processor tracing but without that zero output. Or is there another
> error view besides the trace log in Designer?

If you are in a later Designer (like 4.5 or higher) in the upper right
corner is a text entry spot. Type error and open the errror log that
pops up as an option. Not the trace you are looking at.


> It seems that somehow that driver configuration is messed up. When I
> look at driver - properties - driver configuration - driver parameters I
> see only driver options tab and no subscriber / publisher channel tabs.
> GUI shows me some driver options but separated by several empty lines as
> if Designer could not interpret all of the the XML. If I go to XML edit
> and come back to GUI i get a duplicate driver options tab. If i repeat
> it i get another driver options tab appears. I cross checked the options
> XML to an identical driver and it is precisely same. If I copy paste the
> options XML from the working identical driver I just get another driver
> options tab.
>
> This driver was made by duplicating the identical driver from it's XML
> export. Maybe that process is not fool proof after all?
>
>