Collection job creation

[damocue]

Hello,

I have a new problem with Veeam Reporter. When I create a new Collection Job (the first), I get an exception: "The job does not exist". I know the job doesn't exist, I'm creating it. It successes after writing the job name, when I click "Next". Any idea?

David

I feel strange asking ever and not answering ...

[Alexey D.]

That's strange. i have nothing to say but to advise contacting our support team, please send all the logs.

[damocue]

Thank you. I've just opened a case at Support.

It's very strange...

[Alexey D.]

I agree it's strange. It may be caused by installing not to a clean VM (with use of pre-existing database which could be occasinally corrupted).

[damocue]

Well, the installation is over a physical server, and SQL Server was installed with Veeam Backup and SQL Server 2008 with SSRS with Veeam Reporter. This isn't the first time I make this kind of installation, but it's the first time I get this exception.

[Alexey D.]

Ok... please keep in touch with our support. Thanks!

[andrew86my]

Is there any solution for this issue? I'm having the same problem.

[Vitaliy S.]

Andrew, the OP hasn't mentioned his ticket number, so I cannot update you with the resolution. Please contact our support team for further investigation.

[damocue]

Hi,
The problem here is the name resolution by SQL Server, so it's a problem out of Veeam. SQL Server doesn't resolve very well the name of the host.

Regards,

[Alexey D.]

David, thanks for posting back!