@Anonymous wrote:
I apologize for losing my temper earlier, it's been a crappy day but I should not have acted the way I did...
Yes, I had done some poking around looking for the Journal, but apparently not enough as I found it only when searching %LOCALAPPDATA%\Autodesk\ with nothing after it, and yes it is in Revit then Revit LT. I have attached the most recent one for you.
Also, yes Rendering is listed with my included Services - however it does not show up in supported files in my Rendering Gallery, only AutoCAD and Fusion do.
No worries on the temper. I've had enough bad days myself to not take it personally when somebody else has one.
I took a look at the Journal file - glad you tracked it down - and Revit progresses past the authorization call, so we can discount an entitlement issue as the point of failure.
It appears to be failing at the point of transferring the scene to the Cloud Rendering service, which indicates the network conditions of the machine are somehow preventing the transfer of the data. Since we've ensured your machine has the POODLE patch - included in Revit 2015 UR8 - we can discount that as well. This leaves the firewall as the likely culprit.
This document captures the network conditions that need to exist to transact with our A360 services. I'd recommend you send it to your IT staff and see if they can verify thise conditions are accessible. The simplest way to prove it out is to try the cloud rendering in another network environment. If you have a laptop, it's a matter of connecting it to another WiFi network outside your company. If it's a Desktop Workstation hardwired to your Ethernet, then that's a bit more of a challenge.
Unfortunately the process of debugging firewalls is not trivial, so hopefully you have a resource available to help you out with the process. If that's not the case, we can get a support request going to try and resolve. I feel like I owe you a beer after all these steps...
-Kyle

Kyle Bernhardt
Director
Building Design Strategy
Autodesk, Inc.