Wednesday, November 23, 2011

AutoCAD 2012: How to Create Network Images

AutoCAD 2012 is here! Although it comes with headaches if you need to make network images.

Environment:

Windows 7 SP1 x64 Quad-Core 8 GB

Novell Network

Creating a network image is frustrating in 2012. I have only tried with Revit MEP 2012 and Civil 3D 2012. Both versions failed every time.

Revit MEP 2012:

When the image was being created it would stop with an error message when install the VSTA ART.

"vstaart createadminimage failed 1603"

Civil 3D 2012:

The image would also fail and would rollback the install.

Solution:

Make sure you are logged in as the administrator

Create the images locally to a folder on the root of your hard drive. Do not apply any updates when preparing the image.

C:\C3D2012_64n


After you create the image you need to transfer the entire folder "C3D2012_64n" to the network share.

Brace yourself because this can take a while


You may receive some permissions errors while copying the data from the workstation to the server.

Make note of any directories or files that do not copy over. This will make it easier to find these missing directories once the transfer is finished.


If some directories did not copy correctly to the server, go back now and try to copy it again manually.

Now you will need to change 3 files to get the image to work.

The shortcut, AdminImagex64.ini, and C3D2012_64n.ini.


The Shortcut:

Located on the network share in the C3D2012_64n folder.


Right click on the shortcut and click properties.

We need to change the Target and the Start in properties in the Shortcut tab.

Old Target:

\\Itpc\rmep2012_64\AdminImage\Setup.exe /qb /I \\Itpc\rmep2012_64\AdminImage\RMEP2012_64.ini


Old Start in:

\\Itpc\rmep2012_64\AdminImage


New Target:

"\\10.1.1.12\vol1\AutoDesk Images\RMEP2012_64\AdminImage\Setup.exe" /qb /I \\10.1.1.12\vol1\AutoDesk Images\RMEP2012_64\AdminImage\RMEP2012_64.ini


New Start in:

"\\10.1.1.12\vol1\AutoDesk Images\RMEP2012_64\AdminImage"


AdminImagex64.ini:

Located on the network share in the C3D2012_64n\AdminImage folder.

Right click on AdminImagex64.ini and move the cursor to Open with.

Choose Notepad

If Notepad is not there select Choose default program - Select Notepad - Uncheck Always use the selected program to open this kind of file.


Under Global MSI Properties change the ADMIN_IMAGE_LOCATION to point to the network share. In our case it would be.

\\10.1.1.12\vol1\AutoDesk Images\C3D2012_64n

Save

C3D2012_64n.ini:

Located on the network share in the C3D2012_64n\AdminImage folder.

Right click on AdminImagex64.ini and move the cursor to Open with.

Choose Notepad

If Notepad is not there select Choose default program - Select Notepad - Uncheck Always use the selected program to open this kind of file.


Under Global MSI Properties change the ADMIN_IMAGE_LOCATION to point to the network share. In our case it would be.

\\10.1.1.12\vol1\AutoDesk Images\C3D2012_64n


Under Global MSI Properties change the NETWORK_LOG_PATH to point to the network share. In our case it would be.

\\10.1.1.12\vol1\AutoDesk Images\C3D2012_64n\log


Try to run the network install from a workstation.

If the install won't run you can try to run the Create & modify a deployment tool. Running this tool should fix some of the inconsistencies of creating the image local and trying to move it to the network share.  You will need to set the Target  and Start in properties. Adjust the paths below accordingly.

Target:

"\\10.1.1.12\vol1\AutoDesk Images\RMEP2012_64\AdminImage\Setup.exe" /MD \\10.1.1.12\vol1\AutoDesk Images\RMEP2012_64\AdminImage\RMEP2012_64.ini /ML


Start in:

"\\10.1.1.12\vol1\AutoDesk Images\RMEP2012_64\AdminImage"


Tip:

If the image can run, but still fails at a different point. Try looking at the logs. Sometimes the logs give vague errors so if you can use the Create & modify a deployment tool. Change the image to NOT run silently. Rerun the image and you may receive a more specific error. 

Saturday, June 25, 2011

Display Driver Stopped Responding and Has Recovered

NVIDIA ERROR

 

 

 

 

Error: Display driver stopped responding and has recovered. Display driver NVIDIA Windows Kernel Mode Driver, Version 275.36 stopped responding and has successfully recovered.

Our graphics department was just recently upgraded to Windows 7 x64 machines. These are Quad Core 8 GB Intel boxes. The video cards are brand new NVIDIA Quadro 2000. The user stated that the error message happens frequently through out the day and randomly when completing different tasks.

 

Related Errors:

Display driver nvlddmkm stopped responding and was recovered.

Display driver atikmdag stopped responding and was recovered.

Display driver xxxxxxxx stopped responding and was recovered.

Blue Screen Of Death – nvlddmkm.sys

Blue Screen Of Death – stikmdag.sys

Blue Screen Of Death – xxxxxxxx.sys

 

Research:

This is a post from an NVIDIA forum moderator jimbonbon.

…this is not an nVidia issue. It is not an ATI issue either. These errors are triggered by a Windows service called 'Timeout Detection and Recovery' (TDR). You will only see this error on Windows Vista and Windows 7, as TDR is a feature of the new WDDM driver model (implemented first in Windows Vista). TDR is supposed to be there to help stop BSOD's by resetting the GPU and/or driver when there is an issue. If the problem happens multiple times in a row, a BSOD can occur.

Common issues that can cause a TDR:

  • Incorrect memory timings or voltages
  • Insufficient/problematic PSU
  • Corrupt driver install
  • Overheating
  • Unstable overclocks (GPU or CPU)
  • Incorrect MB voltages (generally NB/SB)
  • Faulty graphics card
  • The issue can potentially be caused by a badly written driver or piece of software, but this is an unlikely cause in most cases.
  • Driver conflicts
  • Another possibility that people tend not to like to hear, is that you are simply asking too much of your graphics card. What I mean by this, is that if you have your settings too high and the graphics card struggles and falls to very low FPS, then something graphically complex occurs, it could trigger a TDR.

Solution:

I checked all of the above in this situation and was still unsuccessful. However, uninstalling FireFox was the one thing that worked! Yes, Mozilla was the culprit in our situation. If you have exhausted all other options and still can not figure out this issue try uninstalling FireFox.

 

notes: If you are still receiving this error message go to this link and try some of the other troubleshooting techniques listed.