i bought alex's MFC yesterday but haven't been able to successfully register. alex is helping me via email (even though it's the weekend) but we haven't figured it out yet.
the last time i had to re-register nebula was in 2011 after upgrading my DAW. everything has been working fine since.
even though all of my libraries have been working fine i decided to upload my nebula.ser file just to make sure that it's not the nebula registration that's preventing MFC from working.
everything went fine and i was emailed my new INIT files.
but i actually run nebula server and have nebulaserver.ser in nebularepository.
i can't upload nebulaserver.ser to the AA server for registration. i get a message saying 'you have reached the maximum number (0 of 0)of license requests for the product class', 'you are not enabled to authorize the product requested'.
why would i have a nebulaserver.ser file if i can't register it?
could this be preventing MFC from working?
4 years with nebula and it can still be confusing.
thanks for the reply. i'm running server 1.3.678. the SER file being generated was never a problem. the file was generated the first time that i loaded MFC. the problem is that the AUT file i received doesn't authorize.
i have re-installed, sent a second SER to alex and even the newer AUT file doesn't work.
I know little of the AUT system, other than following along. Heck, I was neveous about upgrading the Server version ... but now I'm glad I did ... much more stable AND, I can use the MFC. Sorry didn't mean it that way !
My 'system' is fairly much at default locations ... so my MFCPRO.aut file is in the main c:/nebulatemprepository folder.