Thanks for the reply, Hilary. I appreciate it.
Yes, I have pulled what I feel is most relevant and trimmed it. Here's what I see:
03/02/2012 10:10:37.20 w3wp.exe (0x01E8) 0x1208 Forms Server Forms Services Deployment 6ins Medium ConversionAppDomain: Creating new AppDomain for conversion
03/02/2012 10:10:37.28 OWSTIMER.EXE (0x0A84) 0x114C Windows SharePoint Services General 0 Medium Entering MRU trim routine.
03/02/2012 10:10:37.95 w3wp.exe (0x01E8) 0x1208 Forms Server Forms Services Deployment 9ekc Medium ConversionAppDomain is adding a sponsor to an initial lease: 00:05:00
03/02/2012 10:10:37.95 w3wp.exe (0x01E8) 0x1208 Forms Server Forms Services Deployment 9ek8 Medium ConversionAppDomainSponsor created on AppDomain /LM/W3SVC/xxxxxxxxxxxxx-xxxxxxxxxx-xxxxxxxxxx-xxxxxxx, will renew 55 times.
03/02/2012 10:10:37.96 w3wp.exe (0x01E8) 0x1208 Forms Server Forms Services Deployment 140x High Begin Conversion of 00000000-0000-0000-0000-000000000000
03/02/2012 10:10:38.21 w3wp.exe (0x01E8) 0x1208 Forms Server Forms Services Runtime 939k Medium IPFS has just come up
03/02/2012 10:10:38.03 w3wp.exe (0x01E8) 0x1208 Windows SharePoint Services Topology 9e7d Medium Initializing the configuration database connection.
03/02/2012 10:10:38.37 OWSTIMER.EXE (0x0A84) 0x1580 Windows SharePoint Services General 0 Medium Exiting MRU trim routine.
03/02/2012 10:10:40.62 w3wp.exe (0x01E8) 0x1208 Forms Server Forms Services Deployment 140y High End Conversion of 00000000-0000-0000-0000-000000000000
03/02/2012 10:10:41.84 w3wp.exe (0x01E8) 0x15F4 Forms Server Forms Services Runtime 89mj Medium Forms Server Conversion AppDomain is unloading.
03/02/2012 10:10:41.84 w3wp.exe (0x01E8) 0x1208 Forms Server Forms Services Deployment 4n01 Medium ConversionAppDomain: Unload AppDomain - end. xxxxxxxxxxxxx-xxxxxxxxxx-xxxxxxxxxx-xxxxxxx
03/02/2012 10:11:02.68 OWSTIMER.EXE (0x0A84) 0x0EC4 SharePoint Portal Server Business Data 79bv High Initiating BDC Cache Invalidation Check in AppDomain 'DefaultDomain'
03/02/2012 10:11:02.68 OWSTIMER.EXE (0x0A84) 0x0EC4 SharePoint Portal Server Business Data 79bx High Completed BDC Cache Invalidation Check in AppDomain 'DefaultDomain'
03/02/2012 10:11:09.01 w3wp.exe (0x01E8) 0x1208 Forms Server Forms Services Deployment 8gem Medium GenerateWssSolutionPackage: creating CAB with =137 files xxxxxxxxxxxxx-xxxxxxxxxx-xxxxxxxxxx-xxxxxxx
03/02/2012 10:11:11.26 Microsoft.Office.Server.Convers (0x0504) 0x0654 Document Conversions Load Balancer Service 7jhf Medium RegisterLauncher called with uri http://MYSERVERNAME:1234/HtmlTrLauncher
03/02/2012 10:11:15.92 w3wp.exe (0x13D8) 0x15E0 SharePoint Portal Server Runtime 8gp7 Medium Topology cache updated. (AppDomain: /LM/W3SVC/1748148616/Root-x-xxxxxxxxxxxxxxxxxxx)
03/02/2012 10:11:18.34 OWSTIMER.EXE (0x0A84) 0x01B4 SharePoint Portal Server SSO 8inc Medium In SSOService::Synch(), sso database conn string:
03/02/2012 10:11:21.56 w3wp.exe (0x0CA4) 0x0BF8 SharePoint Portal Server Runtime 8gp7 Medium Topology cache updated. (AppDomain: /LM/W3SVC/872172851/Root-x-xxxxxxxxxxxxxxxxxxx)
03/02/2012 10:12:07.81 wsstracing.exe (0x09C4) 0x0C18 ULS Logging Unified Logging Service uls2 Monitorable Not enough free disk space available. The tracing service has temporary stopped outputting trace messages to the log file. Tracing will resume when more than 220 MB of disk space becomes available.
Also; inside \Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\FT-01-.... (as it relates to this particular feature) I have over 300 folders totaling 1GB in space.
Please tell me if I am mistaken; but, it appears that the server is borrowing space to create the new cab file and once done, it will replace the one that's present already. Unfortunately, it doesn't have enough available space for the process. I am guessing that I may kill old versions from the above mentioned feature folder and lose all versioning.
Again, this is a test box and this is just something I'd like to fully understand. Hopefully your insight will help others that run into this.
Thanks,
....Later same day.
I have fixed the issue, but had to kill the library and republish the form do so. A note: I watched closer on the server after I had deleted all of the versions but current inside \12\TEMPLATE\FEATURES\FT-01-.... When I published using central admin, it took 4 minutes and wrote out 45 solution folders inside \12\TEMPLATE\FEATURES\FT-01-.... This was one publish totaling about 250MB. I will follow up when I have everything documented.