topic Re: CCTV processor error in State & Local Government Questions

CCTV processor error

JoshWhite — Wed, 10 Sep 2014 21:04:27 GMT

I tried to run the model and get the following error. I do have some information already in each of the tables. I don't find any help on this with the CCTV processor as it focuses on using ArcGIS Online which is not something I was interested in. What in the world does this error mean? How do I fix it?

ERROR 999999: Error executing function.

The Microsoft Jet database engine cannot find the input table or query 'GDB_ObjectClasses'. Make sure it exists and that its name is spelled correctly.

Failed to execute (Add Attachments).

Failed at Wed Sep 10 15:57:29 2014 (Elapsed Time: 0.14 seconds)

Failed to execute (CCTVtoAGOL).

Failed at Wed Sep 10 15:57:29 2014 (Elapsed Time: 14.97 seconds)

I want to run this model and just have my new results added to CCTVCondtions each time. Is that not what the intent is here? This model looks to create everything the first time, how do I alter it to just do what I want it to do?

Re: CCTV processor error

JoshWhite — Wed, 10 Sep 2014 21:21:18 GMT

Another thought I had was, can I just simply run the Points Along a Polyline by Distance tool and I will attempt that if I have to and just manually do the rest of it. Seems odd to have to enable attachments every time the model is run which may be the problem.

Re: CCTV processor error

MikeMillerGIS — Thu, 11 Sep 2014 14:06:26 GMT

Josh,

You must be running 10.1. Also, the output should be a FGDB. I am not sure how personal(Access based) gdb handle attachments. The model attempts to enable attachments, so it can load the photos into each point. The model is designed to create a new output each time. If you would like to maintain one layer with all results, you will need to add an append step to the model.

Re: CCTV processor error

MikeMillerGIS — Thu, 11 Sep 2014 14:07:13 GMT

Yes, you can just run the script. We packaged this script up into a workflow to not only create the points, but publish them to online. You are free to modify this process to match what is required for your organization.

Mike

Re: CCTV processor error

JoshWhite — Thu, 11 Sep 2014 14:27:41 GMT

I'm running 10.2 is that my problem? I had planned to output to a FGDB. The input is Access though as that is what IT Pipes exports to. Should I create a new feature class to append to at the end of the model? I may just have to work with it until I get it the exact way I want it.

Re: CCTV processor error

MikeMillerGIS — Thu, 11 Sep 2014 14:33:42 GMT

10.2 is what is required. If you want to package up what you have and send it to me, I can test.

Re: CCTV processor error

JoshWhite — Thu, 11 Sep 2014 14:56:36 GMT

I'm still getting that error. The Microsoft Jet database engine cannot find the input table or query 'GDB_ObjectClasses'. Make sure it exists and that its name is spelled correctly. Where would I find that table or query to make sure it exists?

Re: CCTV processor error

MikeMillerGIS — Thu, 11 Sep 2014 14:59:20 GMT

Can you try to right click the GDB and register it? It looks like the tools think the MDB is a GDB and it is not.

Re: CCTV processor error

JoshWhite — Fri, 12 Sep 2014 14:21:45 GMT

Register is not an option for the file geodatabase. I'm wondering if it would be best if I import the tables from the mdb into the gdb and see if that helps and let you know. I will likely just import the tables and attachment table into an sde.

Re: CCTV processor error

JoshWhite — Fri, 12 Sep 2014 16:56:50 GMT

Wow, this thing just must not be in the cards for me. I tried to set up the model and now at the point the inspection and conditions tables are joined I get a mysterious error. I have attached my toolbox. CCTVObservations2 is the one I modified and get the join error, CCTVObservations is the one with the JET database error.

Re: CCTV processor error

MikeMillerGIS — Fri, 12 Sep 2014 16:59:24 GMT

I think there are issues with Access. Can you export the data to a file GDB and use that. I will look into what is going on with Access based databases.

Re: CCTV processor error

JoshWhite — Fri, 12 Sep 2014 18:05:14 GMT

That's what I am doing. For each parameter I am starting with an import from the Access database into a file geodatabase. I guess I could do this separately in two different models.

EDIT: More info...I tried to separate the processes into two separate models. Now the tables that I put into the model are from a file gdb.

Executing (Join COND+INSP): JoinField in_memory\CONDITIONS_COPY InspectionID C:\GIS\ENVIRONSERV\SanitarySewer\CCTV.gdb\INSPECTIONS InspectionID Pipe_Segment_Reference;Direction

Start Time: Fri Sep 12 15:11:52 2014

ERROR 999999: Error executing function.

Failed to execute (Join COND+INSP).

This appears to be an unknown error. Why is the in_memory necessary for conditions table? I don't know why I'm asking that since removing it gave the same error but I am curious about it.

Re: CCTV processor error

JoshWhite — Mon, 15 Sep 2014 14:43:22 GMT

Well, I finally worked out the part where it created CCTVConditions with all of the points and the link to the videos but I cannot get the attachments to function correctly. I think I'm still running into the issue with reruns of the model not reworking all of the outputs. I am thinking that it would be easier to just link to the snapshots as I have the videos.

Re: CCTV processor error

JoshWhite — Fri, 19 Sep 2014 19:49:04 GMT

One additional thing that I think may need some work. When I import the tables from Access (generated by IT Pipes), into a file gdb, the first field such as ConditionID is changed to ObjectID in the file gdb automatically. That appears to be because the field is type AutoNumber in Access. I have to manually create the fields and recalculate them off of the ObjectID in order for the model to work correctly. I may try to model this so it will be easy each time.

Re: CCTV processor error

JoshWhite — Fri, 26 Sep 2014 20:19:29 GMT

I just discovered that the Points along a polygon distance tool does not appear to be honoring the upstream/downstream. Everything just goes downstream. What am I doing wrong? I have the geometric network on and I'm going in the direction of the digitized line, every time I try to turn on the arrows using the network tools, arcmap crashes so I cannot confirm whether or not the network is set up correctly.

Re: CCTV processor error

MikeMillerGIS — Fri, 26 Sep 2014 20:26:00 GMT

I would delete the geometric network and recreate it. Can you share a sample that is not working?

Re: CCTV processor error

JoshWhite — Fri, 26 Sep 2014 21:16:58 GMT

Didn't help to rebuild, and I used the Utility Network Analyst Toolbar to show the flow arrows, this time it showed the arrows but all with indeterminate flow (just a dot rather than an arrow). I hit the Set Flow Direction button and nothing happens. I tried hitting the button on the Water Utility Network Editing Toolbar that sets the flow of network based on the digitized direction of the line and it crashes every time. Did you want the model sample?

Re: CCTV processor error

JoshWhite — Wed, 01 Oct 2014 21:19:02 GMT

Isn't there somebody that can help me out there? I had it working just fine but now it fails every time. I even tried using the original PointsAlongLineDistance script and I get an error every time. How can this script just stop working? The data should not be any different. All I really want to do is be able to use the conditions table and create a point feature class using the distances in the table. I can add on the joins later, I just want to be able to create the points based on a distance in a table along a polyline.

Re: CCTV processor error

MikeMillerGIS — Thu, 02 Oct 2014 09:36:29 GMT

Josh,

I am not sure what is going on. We have been able to repo the Access issue and are working on scripts to fix it. As for the crashing and the points not being created, I am not sure. If you have time today, give me a call and we can walk through it together and try to figure out what is going on.

My phone is 610-644-3374 x5926

Re: CCTV processor error

MikeMillerGIS — Tue, 07 Oct 2014 20:57:47 GMT

Josh and All,

We have reworked the scripts. Attached is the first draft. They now import from a non GDB access database and create the output FGDB. They also create a copy of the mains that where surveyed and trim them to the length surveyed.