Community
Maya Forum
Welcome to Autodesk’s Maya Forums. Share your knowledge, ask questions, and explore popular Maya topics.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Maya 2015-17 NOT WORKING... tried everything.

13 REPLIES 13
Reply
Message 1 of 14
willMarciano
1193 Views, 13 Replies

Maya 2015-17 NOT WORKING... tried everything.

Hello, My name is Will and I am part of the education community of Autodesk. 

I have previously used other animation software, and have decided to make the switch to Maya, because it is very professional.

However, about a week and a half back, I tried to install 2017, and no success. It kept coming up with the error screen: "Fatal Error. Attempting to save in C:/Users/....." Same thing every time. I tried searching online for a solution, but nothing worked. After trying for several hours, I decided to try Maya 2016 and 2015, neither worked, and both gave me the same error message: "// Error: file: C:/Program Files/Autodesk/Maya2016/scripts/startup/layerEditor.mel line 4330: Could not find attribute named "defaultRenderLayer.precompTemplate" //"

 

Something to note is below:

 

Every time I try to start a Maya version, mo matter what version (2015,16, and 17), it brings up an output window and says this. It may seem normal, but notice that the "Driver" line is empty except for a period. Is Maya not recognizing my video card drivers? Geforce says my drivers are 100% up to date, so I don't know what the problem could be.

 

------------------OUTPUT WINDOW------------------
Initialized VP2.0 renderer {
Version : 6.3.16.0. Feature Level 4.
Adapter : GeForce GT 620/PCIe/SSE2
Vendor ID: 4318. Device ID : 4169
Driver : .
API : OpenGL V.4.5.
Max texture size : 16384 * 16384.
Max tex coords : 8
Shader versions supported (Vertex: 4, Geometry: 4, Pixel 4).
Shader compiler profile : (Best card profile)
Active stereo support available : 0
GPU Memory Limit : 1024 MB.
CPU Memory Limit: 15527.8 MB.
}
OpenCL evaluator is attempting to initialize OpenCL.
Detected 1 OpenCL Platforms:
0: NVIDIA Corporation. NVIDIA CUDA. OpenCL 1.2 CUDA 8.0.0.
Supported extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer
OpenCL evaluator choosing OpenCL platform NVIDIA Corporation.
Choosing OpenCL Device GeForce GT 620. Device Type: GPU Device is available.

 

 ------------------PC SPECS------------------

Operating System: Windows 10 Home 64-bit

CPU: Intel Core i7 3770 @ 3.40GHz + Ivy Bridge 22nm Technology
RAM: 16.0GB Dual-Channel DDR3 @ 798MHz (11-11-11-28)
Motherboard: Dell Inc. 0NW73C (CPU 1)
Graphics: DELL S2340M (1920x1080@60Hz) + 1023MB NVIDIA GeForce GT 620 (NVIDIA) 
Storage: 1863GB Seagate ST2000DM001-1CH164 (SATA) 
Optical Drives: TSSTcorp DVD+-RW SH-216BB
Audio: Realtek High Definition Audio

 

Please help, I have spent hours and hours trying to solve this issue. I have uninstalled and reinstalled each version several times. I don't know what I can do. I have tried near everything. 

13 REPLIES 13
Message 2 of 14
sean.heasley
in reply to: willMarciano

Hi @willMarciano and welcome to the community!

First off you should try deleting your settings/preferences.

Second step would be to fully uninstall. I know you mentioned you've uninstalled Maya before but you might not have deleted everything.

After uninstalling go to your C: Drive and your Documents folder and delete all the Maya and Autodesk folders in both locations.


Let me know if this solves your issue!

Please hit the Accept as Solution button if my post fully solves your issue, or reply with additional details if the problem persists.

Kudos are greatly appreciated. Everyone likes a thumbs up!

Message 3 of 14
willMarciano
in reply to: sean.heasley

Just tried both of those solutions, neither worked.

 

I get the same "Fatal Error" message. Something to note is it always appears when Maya is "Initializing Channel Box and Layer Editor" as seen in the attached screenshot. 

 

The output window was the same as before, with the "Driver" slot empty.

 

Stack trace shows the following:

 

Stack trace:
Foundation.dll!TdataHashTable<Tstring,Tstring>::find
Shared.dll!Tworkspace::getFileRule
Shared.dll!TcontainerTemplate::checkDNAMessages
Shared.dll!TcontainerTemplate::getTemplateLocations
Shared.dll!TcontainerTemplate::setDNASearchPath
Shared.dll!TcontainerTemplate::setDNASearchSettings
Shared.dll!TcontainerTemplate::templateExists
Shared.dll!TbaseTemplateAction::handleExists
Shared.dll!TbaseTemplateAction::doCommand
CommandEngine.dll!TmetaCommandPtrArray::catenate
CommandEngine.dll!TmelVariableList::`default constructor closure'
CommandEngine.dll!TminMelArgList::nextDigit
CommandEngine.dll!melScanDouble
CommandEngine.dll!TminMelArgList::nextDigit
CommandEngine.dll!melScanDouble
CommandEngine.dll!melScanDouble
CommandEngine.dll!TminMelArgList::nextDigit
CommandEngine.dll!melScanDouble
CommandEngine.dll!TminMelArgList::nextDigit
CommandEngine.dll!melScanDouble
CommandEngine.dll!TminMelArgList::nextDigit
CommandEngine.dll!melScanDouble
CommandEngine.dll!TminMelArgList::nextDigit
CommandEngine.dll!TminMelArgList::nextDigit
CommandEngine.dll!SophiaExecutable::evaluate
CommandEngine.dll!TcommandEngine::executeCommand
CommandEngine.dll!TpythonFlagException::cache
python27.dll!PyCFunction_Call
python27.dll!PyEval_GetFuncDesc
python27.dll!PyEval_EvalFrameEx
python27.dll!PyEval_GetFuncDesc
python27.dll!PyEval_GetFuncDesc
python27.dll!PyEval_EvalFrameEx
python27.dll!PyEval_GetFuncDesc
python27.dll!PyEval_GetFuncDesc
python27.dll!PyEval_EvalFrameEx
python27.dll!PyEval_EvalCodeEx
python27.dll!PyImport_ExecCodeModuleEx
python27.dll!PyImport_ExecCodeModuleEx
python27.dll!PyImport_ImportModuleLevel

 

 

Note that it seems to stop on the Python 2.7 dll's. Not sure if this is significant at all.

 

Thank you for your fast reply, hopefully we can figure this out!

Message 4 of 14
sean.heasley
in reply to: willMarciano

Ah this is tough. I'll list some other potential fixes I'll list below:

Missing latest directX runtime files. You can install latest from Microsoft

Missing latest C runtime files. You can install latest Visual Studio 2010 sp1 runtime files from Microsoft

Let me know if these work!

Message 5 of 14
willMarciano
in reply to: sean.heasley

Just tried both of those, neither worked again.

 

Interesting to note is (most likely because of all the times I have tried to install maya,) there are several duplicates of the Microsoft Redistributables on my computer. (Screenshot attached)

 

Another thing I didn't mention previously is that fact that Maya has never run on this computer. Never has it launched past the errors.

 

Any other Ideas?

Message 6 of 14
sean.heasley
in reply to: willMarciano

Hey @willMarciano

Try rolling back your GPU drivers to an older version or two. It's possible Maya may be having trouble recognizing the most recent drivers.

Let me know if that works!

Message 7 of 14
willMarciano
in reply to: sean.heasley

I just went back and loaded 4 different drivers, 2 from earlier 2017, 1 from 2016, the one of the Maya certified hardware sheet for the GeForce GTX 680 (because my GT 620 is not listed), and 1 for 2015. None worked.

 

Driver slot on the 'Output Window' remained blank on every driver test. 

 

Should I try others, or should we try something else? 

Message 8 of 14
sean.heasley
in reply to: willMarciano

Hi @willMarciano

My co-worker just showed me the microsoft fix it tool that you can use.

You'll want to download this, run it and uninstall Maya, Arnold and any other plug-ins or programs related to Maya.

After this try reinstalling and see if that solves your issue!

Message 9 of 14
willMarciano
in reply to: sean.heasley

Just tried it. No success.

 

Same error, same output window. 

 

😧

Message 10 of 14
mspeer
in reply to: willMarciano

Hi!

 

1. If you have a Dell System sometimes pre-installed software can cause problems with other applications.

Example:

https://knowledge.autodesk.com/support/maya/troubleshooting/caas/sfdcarticles/sfdcarticles/On-some-D...

Search online for more information and examples.

 

 

2. After a short research it seems your motherboard is not compatible with Win 10 and could cause problems with external 3D Graphic Card not working correct.

If you are sure your system is compatible with Win 10 please post a link to this statement.

Message 11 of 14
willMarciano
in reply to: mspeer

Geez, didn't know that. I have used this computer with Windows 10 for several months and haven't experienced any trouble. I have used 3d applications before, Adobe software, etc, without problems. Never thought there was anything wrong like that.

 

So what do you suggest that I do? Is there any way around this?

Message 12 of 14
mspeer
in reply to: willMarciano

Hi!

 

Issues like the one you experiencing are hard to troubleshoot in a forum.

 

You could try using onboard graphic only (remove NVIDIA card) to see what happens then.

 

But it looks more like a software problem, maybe something like this (Python 27.dll):

https://forums.autodesk.com/t5/installation-licensing/maya-2015-fatal-error-crash-at-startup/td-p/51...

 

 

Message 13 of 14
willMarciano
in reply to: mspeer

Hi, I tried disabling the video card and reverting to my integrated graphics. 

My output window from that is below:

 


Graphic device does not support OpenGL Core Profile, fallback to OpenGL renderer.
VP2 Error : Failed to initialize graphics device.
Stack trace:
Foundation.dll!TdataHashTable<Tstring,Tstring>::find
Shared.dll!Tworkspace::getFileRule
Shared.dll!TcontainerTemplate::checkDNAMessages
Shared.dll!TcontainerTemplate::getTemplateLocations
Shared.dll!TcontainerTemplate::setDNASearchPath
Shared.dll!TcontainerTemplate::setDNASearchSettings
Shared.dll!TcontainerTemplate::templateExists
Shared.dll!TbaseTemplateAction::handleExists
Shared.dll!TbaseTemplateAction::doCommand
CommandEngine.dll!TmetaCommandPtrArray::catenate
CommandEngine.dll!TmelVariableList::`default constructor closure'
CommandEngine.dll!TminMelArgList::nextDigit
CommandEngine.dll!melScanDouble
CommandEngine.dll!TminMelArgList::nextDigit
CommandEngine.dll!melScanDouble
CommandEngine.dll!melScanDouble
CommandEngine.dll!TminMelArgList::nextDigit
CommandEngine.dll!melScanDouble
CommandEngine.dll!TminMelArgList::nextDigit
CommandEngine.dll!melScanDouble
CommandEngine.dll!TminMelArgList::nextDigit
CommandEngine.dll!melScanDouble
CommandEngine.dll!TminMelArgList::nextDigit
CommandEngine.dll!TminMelArgList::nextDigit
CommandEngine.dll!SophiaExecutable::evaluate
CommandEngine.dll!TcommandEngine::executeCommand
CommandEngine.dll!TpythonFlagException::cache
python27.dll!PyCFunction_Call
python27.dll!PyEval_GetFuncDesc
python27.dll!PyEval_EvalFrameEx
python27.dll!PyEval_GetFuncDesc
python27.dll!PyEval_GetFuncDesc
python27.dll!PyEval_EvalFrameEx
python27.dll!PyEval_GetFuncDesc
python27.dll!PyEval_GetFuncDesc
python27.dll!PyEval_EvalFrameEx
python27.dll!PyEval_EvalCodeEx
python27.dll!PyImport_ExecCodeModuleEx
python27.dll!PyImport_ExecCodeModuleEx
python27.dll!PyImport_ImportModuleLevel

 

 

as you can see, it stops on the same python DLL. So maybe it doesnt have anything to do with the graphics card.

 

I also read that other forum and tried to uninstall + reinstall python 2.7, which is what they said worked. Didn't work for me 😞

 

What next?

Message 14 of 14
mspeer
in reply to: willMarciano

Hi!

 

Sorry i can't help you further with this (as i said, too hard and time consuming in a forum, needed to sit in front of the PC).

 

You could try re-installing the OS or try an other one and then start again.

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk Design & Make Report