I’ve come up with a big list of questions to ask when all else fails getting Wavepoint to work. Over the years I’ve implemented Wavepoint a good number of times, and there are a bunch of gotchya’s to be aware of.
The application is highly valued by those who use it. It is a good, lightweight, and simple way to view fiber features and network connectivity. It helps get answers fast about fiber availability or when trying to splice a path together for a customer.
I intentionally stopped myself from ordering these questions logically.
I know if you’ve gotten to the point of looking up troubleshooting assistance online you have had your head down for a while. It is a good idea to take a fresh look in this way to make sure you didn’t miss something small.
Run through the below questions and hopefully you can get enough insight here to solve your problems and get this nice application running with your fiber data.
- Is your ArcGIS Server (or servers) functioning correctly? Can you publish and delete services?
- Did you check the compatibility between your version of ESRI and ArcFM desktop, server, Wavepoint, and Windows Server?
- Did you publish the Wavepoint service with credentials that can view the MM tables?
- Did you include all the fiber (usually F_) tables in the MXD/Stored Display before you published the Wavepoint service?
- Can you ping the ArcGIS Server services or sites from the Wavepoint box?
- Did new security or Active Directory changes take place recently?
- Did the network configurations change recently?
- Have you tried stopping and starting ArcGIS Server/ArcFM Server services?
- Did you make sure your Wavepoint box has all the roles and features included from your version of the Wavepoint Configuration Guide that is appropriate to the Windows Server version you are working on?
- Do you have a Wavepoint line item ready to go in your license file or your license manager?
- Did you forget to add the ArcFM SOE to your ArcGIS Server?
- Did you make sure the Wavepoint application pool item is set to .NET 4.x?
- Did you set the Wavepoint site authentication properties in IIS?
- Do all of the Fiber Manager tools and features work properly?
- Did the SDE file you used really have the credentials of the data owner of the Fiber feature classes and tables?
- Have you tested and confirmed that your fiber data in the map being used to publish the Wavepoint service is truly registered with ArcGIS Server?
- Have you tried publishing your Wavepoint service from a fresh MXD/Stored Display with no symbology, labels, joins, definition queries, or absolutely anything else?
- Did you run …Wavepoint/Verify (or in forms authentication log in as admin and go to …Wavepoint/Account/Verify) and fix the red X’s on features, tables, and relationships you have included in your model?
- Are you using a service account to be the “Run As” user for your Wavepoint Service? Does this account have local machine administrator permissions?
- Can you hit the ArcGIS Server service using the URL you used in the web.config file on the AGSRoot and AGSMapServicePath lines? If you can’t and are trying to go through port 6080, do you have a Web Adaptor set up to forward that traffic through port 43?
- If using Windows Authentication and specifying allowed users in the web.config file, are you using a domain before the individual users? (<allow users=”DOMAIN\username1, DOMAIN\username2″ /> is correct)
- If using Windows Authentication and specifying allowed domain groups in the web.config file, are you using the role tag and not using a domain before the individual users? (<allow roles=”adgroup1, adgroup2″ /> is correct)
- If using Windows Authentication do you know that you must specify allowed users and roles first in the web.config file, and then if you include <deny users=”*” /> it will behave counter-intuitively like “allow these users and roles, then deny anyone else”.
- Do you know that a custom basemap must be cached tile service? Do you know it cannot be a secured service? Did you make sure this was in the Web Mercator projection to match the ArcGIS Online and Bing default maps?
- Have you tried using the vanilla Minerville sample database to publish a service and test Wavepoint with?
- Does your data look right with all the fields like THISFIBERCLASSMODELNAME, FIBERPARENTCLASSMODELNAME, FIBERCHILDCLASSMODELNAME, etc. populated with logical values according to your model?
- Do the port favorites and data have values for spacing and position and status?
- Have you gone through the object and field class model names with a fine-toothed comb?
- Do all your feature classes and tables have the correct privileges?
- When all else fails and Wavepoint throws errors when trying to view data or run traces, have you tried dropping and rebuilding your geometric network?
What do you think?