ERROR 000732 View does not exist or unsupported after 10.3 upgrade

[BugPie]

We have a few models that update a point and polygon feature class in our DB a few times a day using a view into our projects DB. We have exported this to py and made a small change "arcpy.env.overwriteOutput = True" and set to run using windows task manager. All good until we moved our beta to 10.3 earlier this week. I realized after a few days that the script was failing in task manager.

I ran the script in Idle to see if I could trace the problem. Viola... this is what we see.

ExecuteError: Failed to execute. Parameters are not valid.

ERROR 000732: XY Table: Dataset Database Connections\inserrtservername.sde\EBISDE.dbo.project_tel_new_vw does not exist or is not supported

Failed to execute (MakeXYEventLayer).

The view works. I return records when I view in SSMS and Catalog. The model works, and writes new features to the features in the DB. I even deleted my DB connection in catalog, made a new one. Opened the models and re-pointed the GP tools to the view and features hoping this would clear up any mis-matched connection names etc. and export to python. 

What happened at 10.3 that python is unable to make the DB connection? Seems straight forward, but I'm stumped.

[JoshuaBixby]

You had this exact workflow working on this exact machine using an earlier version?  What version?

[BugPie]

I've been digging. IT made a change in that they moved this virtual server to a new physical machine. Is that possibly in play? All variables including the SQL are located on this machine so I can't imagine it is?

Otherwise, yes same workflow. Only real change was we went from 10.1 SP1 to 10.3 where I suspect the problem is.

Full connection path:

ERROR 000732: XY Table: Dataset Database Connections\washout.sde\EBISDE.dbo.project_tel_new_vw does not exist or is not supported

[MichaelVolz]

Collin:

You might need to provide the full path to the database connection, if you are not already doing so.

Are you running this script on a Windows Server?  If so, is the new server the same version as the old server?

[BugPie]

Yes, this script is being utilized from a Windows Server 2008r2 standard SP 1. Both before the physical move and afterwards. Nothing in the Virtual env. has changed.

[SamuelTompsett]

Can you please post the script? It would be easier for people to look at it directly.

Thanks.

[BugPie]

Whoops, sorry, that would be helpful. I have attached a zip to this entry that contains a script that is now failing in what looks to be the connection to the DB. Thanks in advance!

[SamuelTompsett · Accepted solution]

Hello Collin,

Thanks for posting the script.

Have you tried giving the full path to the database connections? Especially for the input view?

Thanks,

Sam

[BugPie]

HI Sam,

No I have not tried that approach yet. I haven't done much yet, wanted to wait on what the community thought before I started anything new other than re-exporting from 10.3.  I will look into your suggestion and report back later.

Thank you !!

[BugPie]

This was the solution. Thank you Sam.

Any ideas if this change is due to 10.3? I'd like to get a better understanding of the underlying cause.