Have you already checked all the known issues with 6.2[0]
Was the upgrade done in place or a content migration using CRX2OAK?
Before deploying your code, could you access all the standard consoles? System/console, CRXDE? After you deployed your code, can you access the standard consoles?
When starting your instance is there any exceptions in the error.log file?
The above investigations would allow us to help you better :)
Have you already checked all the known issues with 6.2[0]
Was the upgrade done in place or a content migration using CRX2OAK?
Before deploying your code, could you access all the standard consoles? System/console, CRXDE? After you deployed your code, can you access the standard consoles?
When starting your instance is there any exceptions in the error.log file?
The above investigations would allow us to help you better :)
I would request you to please share Error.log (any error there), and full detail browser log.
Which 500 error it is? (500.11,500.12,......500.100)
500.0
Module or ISAPI error occurred.
500.11
Application is shutting down on the web server.
500.12
Application is busy restarting on the web server.
500.13
Web server is too busy.
500.15
Direct requests for Global.asax are not allowed.
500.19
Configuration data is invalid.
500.21
Module not recognized.
500.22
An ASP.NET httpModules configuration does not apply in Managed Pipeline mode.
500.23
An ASP.NET httpHandlers configuration does not apply in Managed Pipeline mode.
500.24
An ASP.NET impersonation configuration does not apply in Managed Pipeline mode.
500.50
A rewrite error occurred during RQ_BEGIN_REQUEST notification handling. A configuration or inbound rule execution error occurred.
500.51
A rewrite error occurred during GL_PRE_BEGIN_REQUEST notification handling. A global configuration or global rule execution error occurred.
500.52
A rewrite error occurred during RQ_SEND_RESPONSE notification handling. An outbound rule execution occurred.
500.53
A rewrite error occurred during RQ_RELEASE_REQUEST_STATE notification handling. An outbound rule execution error occurred. The rule is configured to be executed before the output user cache gets updated.