We just upgraded to the new version of Team Server 2017. Our Project folders are being displayed in the Model Explorer but none of the models are available. According to all the documentation the synchronization process is automatic between the repository and the reporting (portal) database but I am not sure that is occurring. I tried to find a way to force synchronization but without success. I am in the Admin account so permissions should not be a problem. Has anyone else seen this problem?
I'm not sure what steps you've taken or what version you've upgraded from but when you upgrade you still need to run through the publication. So I would suggest that you take one model that you want to publish and go to the Admin side, ER/Studio Publication page and publish one model. This initial model will take a while as it sets things up but after that the next time you publish models it should go quicker.
The automatic publication happens after you've published the model once. Then the next time you check in any changes to the repository this all gets pushed out to Team Server automatically.
We migrated from XE7. All the models are available through Data Architect tool. I have tried to "publish" a model in Team Server but it does not provide any check boxes except at the Projects and Workspaces level. I keep getting the message to select a model.
Okay, it seems like this may be still setting everything up on the database side so that could take some time. One thing to check is in the <TeamServer install>\logs there is a configurator.log. That should tell you what's happening and if there are any errors.
You may want to let this sit for a bit and then if nothing changes, then I would suggest opening up a support case.
Nothing bad in configurator.log file but I did find the following in the error log on a periodic basis.
[2018-02-07 15:52:01,644] ERROR org.springframework.scheduling.support.TaskUtils$LoggingErrorHandler - Unexpected error occurred in scheduled task.javax.persistence.EntityNotFoundException
at com.embarcadero.erstudio.portal.sync.SynchronizationStateDaoImpl.getDiagramSynchronization(SynchronizationStateDaoImpl.java:232) at com.embarcadero.erstudio.portal.sync.SynchronizationStateDaoImpl.getERObjectSynchronizationFromResultSet(SynchronizationStateDaoImpl.java:317) at com.embarcadero.erstudio.portal.sync.SynchronizationStateDaoImpl.getNextScheduledERObjectSynchronizationsLinkedByObject(SynchronizationStateDaoImpl.java:290) at com.embarcadero.erstudio.portal.api.v1.sync.ScheduledSynchronizationService.checkSynchronizations(ScheduledSynchronizationService.java:51) at sun.reflect.GeneratedMethodAccessor158.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:64) at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:53) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
There are basically three steps to upgrading completely from XE7:
1) Install and configure Team Server (make sure configuration execution completes on the final page).2) Run the Diagram Data Version Upgrade from Data Architect to upgrade the dm1 files.3) Publish the diagrams from Ready state.
Once that's done then subsequent check-ins will automatically kick off the republication of changes.
The error you pasted above is usually not relevant, but going through logs is best done by taking the case to support.
All that was done. Guess the next step is call tech support. Thanks.