A temporary profile is loaded after you log on to a Windows Vista-based system

A temporary profile is loaded after you log on to a Windows Vista-based system

Symptom

After you log on to a Windows Vista-based system, you may notice that a temporary profile has been loaded instead of the profile that corresponds to the current user. Therefore, any changes that you make to the current desktop are lost after you log off the system. Additionally, the notification area may display the following error message:

Your user profile was not loaded correctly! You have been logged on with a temporary profile.

Changes you make to this profile will be lost when you log off. Please see the event log for details or contact your administrator.

Finally, the following event is logged in the Application log:

Log Name: Application
Source: Microsoft-Windows-User Profiles Service
Date: Date
Event ID: 1511
Task Category: None
Level: Warning
Keywords: Classic
User: User
Computer: Computer
Description:
Windows cannot find the local profile and is logging you on with a temporary profile. Changes you make to this profile will be lost when you log off.

Cause

This problem occurs if the current user's profile was accidentally deleted from the system.

Resolution

 Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

To resolve this problem, follow these steps:

1. Log on to the system by using an administrative user account other than the user account that is experiencing the problem.
2. Back up all data in the current user's profile folder if the profile folder still exists, and then delete the profile folder. By default, the profile resides in the following location:

%SystemDrive%\Users\UserName

3. Click Start, type regedit in the Start Search box, and then press ENTER.

If you are prompted for an administrator password or for confirmation, type your password, or click Continue.

4. Locate the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

5. Under the ProfileList subkey, delete the subkey that is named SID.bak.
   
   Note SID is a placeholder for the security identifier (SID) of the user account that is experiencing the problem. The SID.bak subkey should contain a ProfileImagePath registry entry that points to the original profile folder of the user account that is experiencing the problem.
6. Exit Registry Editor.
7. Log off the system.
8. Log on to the system again.

After you log on to the system, the profile folder is re-created.

AutoCAD splash screen starts up and then closes

AutoCAD splash screen starts up and then closes (Standalone)

Issue

When running the software, it becomes unresponsive and freezes your computer. When you restart the computer and you try to restart AutoCAD, the splash screen starts up and then closes down with no apparent error message.

This symptom is very similar to http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=14908069&linkID=9240617

Solution

1. Check the file "productname201xENUAdlm.log" located here:

Windows XP
C:\Documents and Settings\All Users\Application Data\Autodesk\ADLM

Vista/Windows 7
C:\ProgramData\Autodesk\ADLM

2. The error will typically be:

Reason=Fatal error
ComputerName=COMPUTER
OS=5.1.2600.Service Pack 2
File=AdlmIntSATSLicense.cpp,Line=1150
AdlmIntError=38 [Error getting license usage and behavior]

Reason=Fatal error
ComputerName=COMPUTER
OS=5.1.2600.Service Pack 3
File=AdlmIntSATSLicense.cpp, Line=347
VendorID=2 [ADLMACT]
VendorError=101 [The license cannot be accessed/loaded/opened]

This indicates that the ADLM trusted storage file has been corrupted when AutoCAD crashed.

3. Rename the following file by adding a .bak extension at the end of the filename.

Windows XP
C:\Documents and Settings\All Users\Application Data\FLEXnet\adskflex_*_tsf.data

Vista/Windows 7
C:\ProgramData\FLEXnet\adskflex_*_tsf.data

This file contains all activations for all 2010 and 2011 products. You will need to re-register all your products if this file is renamed/deleted.

4. Restart AutoCAD and it will automatically re-register via Register Today and it will start up as expected. A new adskflex_*_tsf.data file will be created when you re-register your product.

 *If the a new adskflex_*_tsf.data is not created even after restarting the machine.

Make sure "FLEXnet Licensing Services" is running and it should be automatic. 

Even after completing all the steps it's not working, then we need to uninstall the AutoCad completely. Install AutoCad again and need to do the ofline activation.

For Offline activation key you need to send a request to AutoCad from your registered email.

Applies to:
AutoCAD® 2013
AutoCAD® 2012
AutoCAD® 2011
AutoCAD® 2010.

----------------------------------------------------------------------------------------------------------

AutoCAD splash screen starts up and then closes (Network)

Issue

When running the software, it becomes unresponsive and freezes your computer. When you restart the computer and you try to restart AutoCAD, the splash screen starts up and then closes down with no apparent error message.

Solution

For a network version of AutoCAD, you will need to delete the following file:

CascadeInfo.cas.

When you restart AutoCAD, it will re-create this file. This file is located in the following directory:

Windows Vista/Windows 7
C:\ProgramData\Autodesk\ADLM

Windows XP
C:\Documents and Settings\All Users\Application Data\Autodesk\ADLM

Corrupt CascadeInfo.cas file results in failure of cascading functionality

Issue

Cascading functionality is lost due to a corrupt CascadeInfo.cas file.

Solution

If the CascadeInfo.cas file is corrupt due to a power failure or any reason, cascading functionality will not be available. This issue only applies to network licensed products and does not affect stand-alone licensed products.

Example:

Given the following cascading sequence and a license server with a license for Product B & Product C:

Product A -> Product B -> Product C

Cascading failure may present itself in the following way:

Startup Problems:

Scenario 1: A product that did not have its own license and that was previously starting by using a shared license through cascading will fail to start.

Example: The Product B license is available on the server. If the CascadeInfo.cas file is corrupt, Product A will not start on license B.

Example: The Product B license is borrowed to a system where Product A is also installed. If the CascadeInfo.cas is corrupt, Product A will not run on the borrowed license.

Example: If Product B is already running and CascadeInfo.cas is corrupt, Product A will not share the B license and will fail to start.

Wasted licenses:

Scenario 2: An already running product will fail to cascade up to and share another license.

Example: Product B is already running then Product C starts up. If CascadeInfo.cas is corrupt, Product B will not switch over to share product C's license after a few minutes.

Expected Log File output

Here is the expected log file output. You should see a fatal error message with a vendor id of 10 (eVendorIDCascade) and a vendor error of 6 (ADLM_CASCADE_STATUS_DECRYPTION_ERROR). It will also be followed by an AdlmInt error of 47 (ADLM_STATUS_ERROR_CASCADING_OPERATION) or 2 (ADLM_STATUS_INTERNAL_ERROR).

1012 2009/09/16 15:07:20 Reason=Fatal error
1012 2009/09/16 15:07:20 ComputerName=MyComputer
1012 2009/09/16 15:07:20 OS=5.2.3790.Service Pack 2
1012 2009/09/16 15:07:20 File=AdlmIntLicense.cpp,Line=xxxx
1012 2009/09/16 15:07:20 VendorID=10
1012 2009/09/16 15:07:20 VendorError=6
1012 2009/09/16 15:07:20 Reason=Fatal error
1012 2009/09/16 15:07:20 ComputerName=MyComputer
1012 2009/09/16 15:07:20 OS=5.2.3790.Service Pack 2
1012 2009/09/16 15:07:20 File=AdlmIntNWFBLicense.cpp,Line=xxx
1012 2009/09/16 15:07:20 AdlmIntError=47

WorkAround

The current workaround it to rename/remove the corrupt CascadeInfo.cas file following these steps.

Return any borrowed licenses

Check in any checked out licenses and exit all Autodesk products

Rename or delete the corrupt CascadeInfo.cas

The CascadeInfo.cas file can be found in the following locations:

Windows XP:

C:\Documents and Settings\All Users\Application Data\Autodesk\Adlm

Windows Vista and Windows 7:

C:\ProgramData\Autodesk\Adlm

Mac:

/Library/Application Support/Autodesk/Adlm/.config

Linux:

/var/opt/Autodesk/Adlm/.config

 

Receive message opening Perspectives: This workbook has lost its vba project, active x control and any other programmability related features

Receive message opening Perspectives: This workbook has lost its vba project,  active x control and any other programmability related features

Problem(Abstract)

Message trying to start Perspectives using a new instance of Excel 2007:

This workbook has lost its vba project, active x control and any other

programmability related features.

Symptom

Message displayed:

This workbook has lost its vba project, active x control and any other
programmability related features.

Cause

New install of Excel 2007 does not install 'Visual Basic for Applications' by

default.

Resolving the problem

Steps to add 'Visual Basic for Applications';

1. Click on the "Start" button and choose "Control Panel".

2. Goto "Add or Remove Programs".

3. Select "Microsoft Office" from the list of programs and Click on "Change".

4. Select "Add or Remove Features" and then click on "Continue".

5. Expand "Office Shared Features".

6. Select "VBA for Application" and click Continue.

-
Now that VBA for Applications is installed, you will need to show the "Developer" item on your toolbar and

set macro security.

7. Click on the Office button.

8. Select "Excel Options" at the bottom of the window.

9. Select "Popular" and place a check mark for "Show Developer in the Ribbon".

10. You should now see a new item on the menu bar called "Developer".

11. To set the security level of Excel so that you can use macros, click on the "Developer" menu item and

click on the "Macro Security" button in the ribbon. Place a check mark for the second level "Disable all

Macros with Notification".

12. Click OK.

Then It should work

After Changing all the setting, you can open and test the excel sheet.

Most of this kind of error occurs when there is hyperlink is enabled in the Excel.

If you're able to open the Excel sheet and unable to run the hyper link you need to check Active X setting and select " prompt me before enabling all the controls with minimal restriction " 

Under Developer -- Macro Security --  Active X Settings

After all the settings the Excel should work ....

Issue

NTLDR is missing

Related errors

Below are the full error messages that may be seen when the computer is booting.

Boot: Couldn't find NTLDR
please insert another disk

NTLDR is missing 
Press Ctrl Alt Del to Restart

Causes

1. Computer is booting from a non-bootable source.
2. Computer hard disk drive is not properly setup in BIOS.
3. Corrupt NTLDR and NTDETECT.COM file.
4. Misconfiguration with the boot.ini file.
5. New hard disk drive being added.
6. Corrupt boot sector / master boot record.
7. Seriously corrupted version of Windows 2000 or Windows XP.

Solutions

Computer is booting from a non-bootable source

Many times this error is caused when the computer is attempting to boot from a non-bootable floppy disk or CD-ROM. First verify that no floppy diskette or CD is in the computer, unless you are attempting to boot from a diskette.

Important: When you see this message press any key such as the Enter key immediately, otherwise it will try booting from the hard drive and likely get the NTLDR error again.

Note: If you are not receiving the above message and your BIOS boot options are set properly it's also possible that your CD-ROM drive may not be booting from the CD-ROM properly. Verify the jumpers are set properly on the CD-ROM drive.

Computer hard disk drive is not properly setup in BIOS

Verify that your computer hard disk drive is properly setup in the CMOS setup. Improper settings can cause this error.

Corrupt NTLDR or NTDETECT.COM file

1. Insert the Windows XP bootable CD into the computer.
2. When prompted to press any key to boot from the CD, press any key.
3. Once in the Windows XP setup menu press the "R" key to repair Windows.
4. Log into your Windows installation by pressing the "1" key and pressing enter.
5. You will then be prompted for your administrator password, enter that password.
6. Copy the below two files to the root directory of the primary hard disk. In the below example we are copying these files from the CD-ROM drive letter, which in this case is "e." This letter may be different on your computer.
   copy e:\i386\ntldr c:\
   copy e:\i386\ntdetect.com c:\
7. Once both of these files have been successfully copied, remove the CD from the computer and reboot.Misconfiguration with the boot.ini file

Misconfiguration with the boot.ini file

          Edit the boot.ini on the root directory of the hard disk drive and verify that it is pointing to the            the correct location of your Windows operating system and that the partitions are properly defined.

New hard disk drive being added

If you are attempting to add a new hard disk drive to the computer make sure that drive is a blank drive. Adding a new hard disk drive to a computer that already has Windows installed on it may cause the NTLDR error to occur.

If you are unsure if the new drive is blank or not try booting from a bootable diskette and format the new hard disk drive.

Corrupt boot sector / master boot record

It's possible your computer's hard disk drive may have a corrupt boot sector or master boot record. These can be repaired through the Microsoft Windows Recovery console by running thefixboot and fixmbr commands.