Microsoft Excel cannot open or save any more documents because there is not enough available memory or disk space

Error while accessing Office Exel Files via IIS.

ERROR :

Microsoft Excel cannot open or save any more documents because there is not enough available memory or disk space.
• To make more memory available, close workbooks or programs you no longer need.
• To free disk space, delete files you no longer need from the disk you are saving to.

RESOLUTION :

 Go to run type dcomcnfg.msc
Click >Component services >Computes >My Computer>Dcom config> and select micro soft Excel Application>
 Right Click on Microsoft Excel Application>Properties>Give Asp.net Permissions
 Select Identity table >Select interactive user >select ok




That's IT.

Cheers!!!!!

free spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filterexchange spam filter exchange spam filter

Access is denied when using Configuration Manager Remote Control

The ConfigMgr Console Could not Connect to the ConfigMgr Site Database. Verigy that this computer has network connectivity to the SMS Provider computer and that your user account has Remote Activation permissions on both the ConfigMgr site server and SMS Provider computers. For More information see " How to Configure DCOM Permissions for Configuration Manager Console"

error while trying to access SCCM Server via remote Console.

Solution No 1:


The user account running the Configuration Manager console requires permissions to access the site database through the SMS Provider. Any administrators who will use a remote Configuration Manager console require Remote Activation DCOM permissions on both the site server computer and the SMS Provider computer.
The SMS Admins security group is used to grant access permissions to the SMS Provider. User accounts for administrators that will run the Configuration Manager console must be a member of the SMS Admins group and the following procedure must be performed to grant the necessary DCOM activation permissions to the SMS Admins group.

To grant Remote Activation permissions to the SMS Admins group

1. From the Start menu, click Run and type Dcomcnfg.exe.
2. In Component Services, click Console root, expand Component Services, expand Computers, and then click My Computer. On the Action menu, click Properties.
3. In the My Computer Properties dialog box, on the COM Security tab, in the Launch and Activation Permissions section, click Edit Limits.
4. In the Launch Permissions dialog box, click Add.
5. In the Select User, Computers, or Groups dialog box, in the Enter the object names to select (examples): box, type SMS Admins and click OK.
6. In the Permissions for SMS Admins section, select the check box to allow Remote Activation.
7. Click OK twice, and then close Computer Management.

For More Information see : http://technet.microsoft.com/en-us/library/bb633148.aspx

Solution No 2:

1)      Go to Start - > Run -> type “WMIMGMT.MSC”

2)      Right Click on “WMI Control ( Local )” and select Properties.

3)      Select Security Tab in WMI control properties Window.

4)      Find SMS Folder by expanding Root Folder.

5)      Select Site_<site Code> folder and Click on Security button.

6)      Add Local Group of SMS Admins and Give below Permission.

Execute Method

Provider Write

Enable Account

Remote Enable

===============================xxxxx=============================

Cheers!!!!!!!!

Gaurang Patel

free spam filter

0x80091007 OS Deployment Task Sequence Error in SCCM 2007

0x80091007 OS Deployment Task Sequence Error in SCCM 2007

yesterday i was landed up with above task sequence during OS deployment with SCCM 2007, Task Sequence was made by using MDT integration with SCCM 2007, After Facing this error i read the SMSTS.LOG file and Found The reason and able to solve the issue, hear is the CAUSE and Resolution of this error.

Cause :

Failed to run the action: Use Toolkit Package.
The hash value is not correct. (Error: 80091007; Source: Windows) TSManager 00/00/2012 3:51:24 PM 3112 (0x0C28)
because downloaded package hash value is different.

RESOLUTION :

1) Refresh effected Package on DP with New Source Version.
2) or Re-create Package and add on DP.


Cheers!!!!

Gaurang Patel

exchange spam filter exchange spam filter exchange spam filter exchange spam filterexchange spam filter exchange spam filter exchange spam filter

SCCM Capture Media not able to Capture Reffrence Computer image.

When trying to capture a new image of DELL Optiplex 790 windows 7 Proff SP1.  After I fill in the relevant information to save to a network share on a SCCM Server itself and then select finish, the windows disappears and does nothing.
i looked for Sysprep Folder in %System Drive %\windows32\Sysprep but it was present and able to run properly.
Checked Computer Network Access Account on SCCM Server and for Local Computer also then after
  i have looked at the logs and this is what it states:

AllocateCDRoms is set; will not start TSManager

This seems to halt the capture process and nothing else happens.
i have also plugged in an external drive to capture the image to this, and the same error comes up.

Cause :

AllocateCD Rome is Restricted by Group Policy when it was in Domain or by default set by some OEM vendors.

SCCM Capture media uses SYSTEM and Domain Account for Capturing the Windows Image but GPO is only allow CD ROM access to Logged on Users in result Capture wizard Finished without any capture process.

Resolution :

"allocatecdroms" is the REG Key value which is responsible for the CD ROM access.

By default the Value is "0" if this value is "1" that means CD ROM access has been restricted for Local logged on users only.

To resolve this issue set REG Key value to Default "0" and save it.

close Regedit and Restart Computer.

Start Capture wizard again and check...

For More information Please browse Microsoft Technet Article for the same...

http://technet.microsoft.com/en-us/library/cc957388.aspx

Cheers!!!!!

exchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter

Windows Deployment Service Fail to start in 2003 and 2008 with SCCM

Windows Deployment Service Fail to start in 2003 and 2008 with SCCM.

I have a Windows 2008 Server that has WDS + SCCM 2007 R3 installed.  The Windows
Deployment Services Server Service isn't started and when I try to
Start  it I got a message that says:

Windows could not Start the Widows Deployment Services Server on Local
Computer.  For more information, review the System Event Log.  If this
is a non-Microsoft service, contact the service vendor, and refer to

server-specific error code 2310.
Event viewer lists Event ID 257 and this:
An error occurred while trying to Start the Windows Deployment Services
server.
 Error Information: 0x906
  
Hear is the Problem Analysis and Resolution of below errors.

CAUSE :

This problem occurs because the location of the computer object that is running WDS has changed in the Active Directory directory service.

A Windows Deployment Services (WDS) server is running Microsoft Windows Server 2003 with Service Pack 1 (SP1) or Microsoft Windows Server 2003 with Service Pack 2 (SP2). If you move the WDS server to a different organizational unit, the WDS server may not start. Additionally, one of the following error messages may be logged in the System log on the WDS server:

Error Messages :

Error message 1

Type: Error
Event ID: 7024 Source: Service Control Manager
Description: The Windows Deployment Services Server service terminated with service-specific error 9 (0x 3).

exchange spam filter exchange spam filter exchange spam filter exchange spam filter exchange spam filter Error message 2

Type: Error
Event ID: 7024 Source: Service Control Manager
Description: The Windows Deployment Services Server service terminated with service-specific error 19 (0x13)

One of the following groups of error messages may also be logged in the Application log:

Error message group 1

Type: Error
Event ID: 261
Source: WDSPXE
Description: An error occurred while trying to initialize provider BINLSVC loaded from C:\WINDOWS\system32\binlsvc.dll. If the provider is marked as critical the Windows Deployment Services server will be shutdown. Error Information: 0x 3

Type: Error
Event ID: 1800 Source: BINLSVC
Description: An error occurred while creating the Service Control Point object for this Windows Deployment Services server in Active Directory Domain Services. Error Information: 0x 3

Type: Error
Event ID: 1803
Source: BINLSVC
Description: An error occurred while attempting to locate the Service Control Point object for this Windows Deployment Services server in Active Directory Domain Services. There was an error reading the 'netbootSCPBL' attribute from the Computer object. Error Information: 0x2

Error message group 2

Event Type: Error
Event Source: BINLSVC
Event ID: 1803 Description: An error occurred while attempting to locate the Service Control Point object for this Windows Deployment Services server in Active Directory Domain Services. There was an error reading the 'netbootSCPBL' attribute from the Computer object. Error Information: 0x2

Event Type: Error
Event Source: BINLSVC
Event ID: 1800 Description: An error occurred while creating the Service Control Point object for this Windows Deployment Services server in Active Directory Domain Services. Error Information: 0x13

Event Type: Error
Event Source: WDSPXE
Event ID: 261 Description: An error occurred while trying to initialize provider BINLSVC loaded from C:\WINDOWS\system32\binlsvc.dll. If the provider is marked as critical the Windows Deployment Services server will be shutdown. Error Information: 0x13

Event Type: Error
Event Source: WDSPXE
Event ID: 265 Description: An error occurred while trying to initialize provider BINLSVC. Since the provider is marked as critical, the Windows Deployment Services server will be shutdown. Error Information: 0x13

Event Type: Error
Event Source: WDSServer
Event ID: 513 Description: An error occurred while trying to initialize provider WDSPXE from C:\WINDOWS\system32\wdspxe.dll. Windows Deployment Services server will be shutdown. Error Information: 0x13

Event Type: Error
Event Source: WDSServer
Event ID: 522

Description: An error occurred while trying to shutdown provider WDSPXE. Error Information: 0x6

RESOLUTION :

To resolve this problem, reinitialize the WDS server after you move the WDS server to a different organizational unit. To do this, follow these steps:

1. Click Start, click Run, type cmd, and then click OK.
2. At the command prompt, type wdsutil /uninitialize-server, and then press ENTER.
3. Move the WDS account to Active Directory in the new organizational unit.
4. To reinitialize the WDS service, type wdsutil /initialize-server /reminst:{RemoteInstallFolder} at a command prompt, and then press ENTER.

Enjoy!!!!

Enabling workgroup clients to locate SMS and ConfigMgr site systems using LMHOSTS files

System Center Configuration Manager can Manage Workgroup Computer clients but Workgroup computers must be able to locate a server locator point for site assignment and their default management point in order to be managed. Because workgroup clients cannot query Active Directory Domain Services to find these site systems, in this situation, you have three options:

1. The server locator point can be specified in the CCMSetup.exe installation command-line parameters. For more information about doing this see About Configuration Manager Client Installation Properties at: http://technet.microsoft.com/en-us/library/bb680980.aspx.
2. You can manually publish the server locator point and management point in WINS. For more information about doing this see, How to Manually Add Configuration Manager Site Information to WINS at: http://technet.microsoft.com/en-us/library/bb632567.aspx.
3. The server locator point can be specified in the LMHOSTS file on workgroup computers when a WINS server is not available

For Workgroup clients to locate these site systems, you need to enable some sort of NetBIOS name resolution. If you do not have a WINS server in place to support these clients, you can use an LMHOSTS file to enable site system name resolution for Workgroup clients.
To use the LMHOSTS file for site system name resolution, just add the following information (where <site code> is the site code for the primary site the client should be assigned to) to the LMHOSTS file. The LMHOSTS file is generally located in the client's %WINDIR%\system32\drivers\etc directory:
<IP address of MP> "MP_<site code> \0x1A" #PRE
<IP address of SLP> "SMS_SLP \0x1a" #PRE

NOTE: For the lmhosts file to work, it should not have a file extension. If you only find the lmhosts.sam (sample file) in that location just modify the file for your purposes and save it without the .sam file extension.

Because these names contain special characters, they must be enclosed in quotation marks. There must be a total of 20 characters within the quotation marks. There must be a total of 20 characters within the quotation marks. Yes, I wrote that twice on purpose for emphasis! If there aren't 20 characters in the name then using the LMHOSTS file for this will not work. Make sure that the backslashes are at the 16th character the end quotes should be after the 20th character.
Here's a handy trick for doing this that I picked up from How to write an Lmhosts file for domain validation and other name resolution issues (http://support.microsoft.com/kb/180094):
There must be a total of 20 characters within the quotations (the domain name plus the appropriate number of spaces to pad up to 15 characters, plus the backslash, plus the NetBIOS hex representation of the service type).

To help determine where the sixteenth character is, copy the following line to your Lmhosts file:# IP Address "123456789012345*7890" Line up the double quotation marks (") by adding or removing spaces from the comment line, and put the \ on the sixteenth column (the column marked with the asterisk). You must use spaces after the name and before the \, not a tab.
After that has been done, to verify it worked just open up a command prompt and enter the following command to refresh the name cache:
nbtstat -R