Multiple connections to a server or shared resource by the same user…

Error Message:  “\\x.x.x.x is not accessible.  You might not have permission to use this network resource.  Contact the administrator of this server to find out if you have access permissions.

Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed.  Disconnect all previous connections to the server or shared resource and try again.”

I get this once in a while when working on files remotely.  To make it go away, do the following:

1. Go to Start->Run, type in cmd and hit Enter.
2. Type net use to view all mapped network shares.
3. Type net use \\network_share /del to disconnect that specific network share or  type net use * /del to disconnect all network shares.

VMware ESXi: Setup did not find any hard disk drives installed in your computer (Windows XP)

If you get this error when installing Windows XP in VMware ESXi, simply do the following:

1. Download this floppy image which contains the VMware SCSI drivers: vmscsi-1.2.0.4.flp.
2. Upload the floppy image to the datastore using the VI Client.
3. Edit the virtual machine settings and select Floppy Drive 1, then choose the option on the right to “Use existing floppy image in datastore:” and select the floppy image.
4. Power on the virtual machine.
5. Press F6 when you see the message “Press F6 if you need to install a third party SCSI or RAID driver…” at the bottom of the screen.
6. Connect Floppy Drive 1.
7. Press S, then press Enter to select the VMware SCSI Controller driver, then press Enter again to continue with the setup.

That’s it! The Windows XP setup should now be able to detect the hard drives :).

Source: VMware Knowledgebase Document

Windows cannot access the specified device, path, or file

Error Message: “Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.”

If you get this error when you tried to run an executable file, simply do the following:

1. Right-click on the file and choose Properties.
2. In the General tab, click the Unblock button at the bottom and hit OK.

Try running the executable file again and it should now work.

Exchange 2007 SP1: Message rejected as spam by Content Filtering

Error Message: “550 5.7.1 Message rejected as spam by Content Filtering.”

One of our users reported that after we applied Service Pack 1 and Update Rollup 1 to Exchange Server 2007, some of the emails that he has scheduled to send daily were getting rejected with the message above.

I guess the integrated anti-spam in Exchange got updated as well.

You can configure Content Filtering in Exchange to bypass specific users or domains.

Open the Exchange Management Shell:

# To check the Content Filter configuration, type in:

Get-ContentFilterConfig

# To set the Bypassed Senders (example):

Set-ContentFilterConfig -BypassedSenders donotspamme@calazan.com, jdoe@abc.com

# To set the Bypassed Sender Domains (example):

Set-ContentFilterConfig -BypassedSenderDomains calazan.com, *.xyz.com

Important Note: BypassedSenders and BypassedSenderDomains are multivalued properties. When you use the Set-ContentFilterConfig cmdlet, it will overwrite the values of those properties. If you just need to add more senders or domains, please follow the example below.

# To add Bypassed Senders:

$x = Get-ContentFilterConfig

$x.BypassedSenders += “jsmith@google.com”, “bhope@yahoo.com”

# To remove Bypassed Senders (can only be done one at a time):

$x = Get-ContentFilterConfig

$x.BypassedSenders -= “jsmith@google.com”

# To empty the list:

Set-ContentFilterConfig -BypassedSenders $null

Exchange Management Tools SP1: Service Remote Registry failed to reach status “Stopped”

I got this error while upgrading the Exchange Management Tools on my Windows XP computer at work to Service Pack 1. I checked the services and the Remote Registry service is stuck at “Stopping” status.

To fix this, simply set the Remote Registry service’s startup type to Manual, reboot your computer, try installing Exchange Server 2007 SP1 Management Tools again and it should now install successfully. The Remote Registry service will automatically start and the startup type will go back to Automatic after the installation.

Excel 2007: When trying to open Office Excel (.xls) file, worksheet does not open until you click the minimize or maximize button

Update: Two more users reported the same problem and it looks like it’s actually the Adobe PDF add-in causing the problem! I noticed that all 3 users have this add-in. I didn’t uninstall it because they’re using it, but what I did to fix this problem was I installed and enabled one of the add-ins that is part of Office 2007 and all their Excel files started loading fast again :).

Original Post:

You may also see the error message below:

Cannot find the file ‘PathToFile‘ (or one of its components). Make sure the path and filename are correct and that all required libraries are available.

One of our users who we just upgraded to Microsoft Office 2007 had this problem this morning. When she double-clicks on an Excel file, the Excel program opens but the file itself doesn’t open until she clicks the minimize or maximize buttons.

The problem seems to have something to do with DDE.

To fix this problem, do the following:

1. Open Windows Explorer.
2. Go to Tools -> Folder Options -> File Types tab. Select XLS then click the Advanced button.
3. Select Open, then click the Edit button.
4. Under Application used to perform function: make sure there’s a quotation mark before and after %1 just like the picture below:
   



5. Uncheck Use DDE.

Credit goes to the posts from this site.

WMI: Access is denied. (Exception from HRESULT: 0×80070005)

We have one computer at work that I couldn’t send a Remote Assistance request to and whenever I try to query it using WMI and PowerShell I get the following error message:

Get-WmiObject : Access is denied. (Exception from HRESULT: 0×80070005 (E_ACCESSDENIED))

The problem turned out to be DCOM. For some reason it got disabled.

To change its settings, do the following:

1. Go to Start -> Run, type in dcomcnfg.
2. Go to Component Services -> Computers.
3. Right-click on My Computer and select Properties.
4. Go to the Default Properties tab.
5. Make sure that Enable Distributed COM on this computer is checked.
6. Compare the settings to a computer that is working properly and make the necessary changes. Compare the settings for the COM Security tab as well.
7. Reboot the computer and try it again.

Credit goes to this website where I found this solution.

Exchange 2007: Mapi session exceeded the maximum of 32 objects of type “session”

Error Message: “Mapi session “/o=Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=JohnSmith” exceeded the maximum of 32 objects of type “session”".
Source: MSExchangeIS
Event ID: 9646

On the client side, the user is unable to connect to Microsoft Exchange or getting this error:

Unable to open your default e-mail folders. The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server is down for maintenance.

This usually happens when the user loses network connectivity while Outlook is still open. The Exchange server wasn’t able to close the sessions properly so they just stayed there even when they are not in use.

By default, Exchange only allows up to 32 MAPI (Outlook) sessions per user. To fix this problem, you must close some of the sessions.

What to do:

1. Download and extract Sysinternals’ TCPView (free) on the Exchange server
2. Open the Exchange Management Shell and type in the following command to get a list of all the opened sessions. Make a note of the IP Addresses:
   Get-LogonStatistics jsmith | Sort-Object clientipaddress | Format-Table username,clientipaddress,logontime
3. Open Tcpview.exe on the server. Sort it by Remote Address, then sort it by Process.
4. Look for the IP Addresses from Step 2 in the Remote Address column (if you only see hostnames, go to Options -> uncheck Resolve Addresses) and close their connections for the store.exe process (right-click and choose Close Connection, you can select multiple connections by holding the Shift or Ctrl key)
5. Run the command from Step 2 again and you will see that the sessions disappeared. The user should now be able to connect to the Exchange server again.