Author Archive

Setting up a new installation of Office 2010 Standard on a computer , and thanks to the standard unistall procedure of Norton Internet Security, the computer restarted half way through the installation. Re installation produced the following error message at the end of set-up HRSERULT:OX80070BC9 To fix this error , download and run the Office 2010 un-installer from here After this has completed , give the computer a reboot and try again , and it will complete this time!
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
After trying to connect to connect to a computer in the Remote Web Workplace the following message comes up VBScript: Remote Desktop Disconnected An internal error has occured The computer had to be added manually to the domain instead of using the remote web workplace wizard. This means the default Windows 7 options for Remote Desktop is set to “Don’t allow connections to this computer” Setting the “Allow connections only from computers running Remote Desktop with Network Level Authentication” will produce this error The option needs to be on for “Allow connnection from computer running any version of Remote Desktop” for connection to work Then choose the Select Users button and add the user who needs access remotely or set to Domain Users for everyone on the domain. Also make sure the RDP port 3389 is enabled on the local firewall of the PC
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
If  you are using a Remote Desktop Connection on a MAC , and you want to minimise the session , so you can switch between your mac desktop and the RDP session the following commands will do this Command key icon (Command key) and H = Hide/Minimise the Session Command key icon (Command key) and Q = Quits the Session
VN:F [1.9.22_1171]
Rating: 7.5/10 (4 votes cast)
VN:F [1.9.22_1171]
Rating: +1 (from 3 votes)
After the moving of 5 computers to a new office, windows shares and transfers where causing issues. Upon opening up any of the programs in the Microsoft Office Suite and saving the document back to the file server, the program would crash and bring up : Windows delayed write failed and Path is too Deep The file path was the root of the drive and the file name was small so there wasn’t a problem with the Path Size in the users computer After manually saving the document to the local desktop and then copying it back to the same server, it worked! Further testing proved that copying a large sized file around 30mb would provide a new error message just after starting the transfer and creating the file  network path is no longer available The network was fine with pings , no drop outs and copying down from the server was fine. The problem pointed to the MTU size or transfer speed not being agreed by the switch or the computer. The problem in the end turned out to be a fault Media Converter ( Fibre to Ethernet ). So if you get the error message I would double check cables , switches and routers in between the two devices!
http://gallery.techarena.in/data/519/delayed-write-failed-error-thumb.jpg
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
I recently had an issue , where a single user in an exchange server email enviroment, was sending a single email ( one item appearing in Sent Items) , however two where being receipted by the users. Even sending an email to himself or CC’ing himself in, duplicated the message. The messages had different message ID’s. The error seemed to be in the .SRS file of the outlook profile. This is used to store all the ?Microsoft Outlook Send/Receive Settings. You can delete this file by 1) Closing Outlook ( Check the Process Outlook.exe is also closed in Task Manager using Ctrl , Alt and Delete ) 2) Go to the users Outlook Profile Location usually %USERPROFILE%\Application Data\Microsoft\Outlook for Windows XP or %appdata%\microsoft\outlook for Windows 7 3) Locate the SRS file for the current outlook profile being used and delete 4) Open up outlook again , which will recreate a new SRS file and should fix the error
VN:F [1.9.22_1171]
Rating: 7.0/10 (1 vote cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
I recently activated a blackberry to a Blackberry Enterpise Server , however on sending emails , a red cross was displayed with the following error message “Desktop email program unable to submit message” Upon research the problems for this error message are displayed in the KB04422 and further issues showed it was a Send As Error . After checking the user account , BesAdmin did not have Send As Permission. I added the permission let it replicate and restart the blackberry routing service which fixed the issue. An hour last the user came back with the same problem and upon checking the permissions had been reset. Microsoft has provided the following list. If an object (user, machine, or other group) is a member of any of these groups, it will be considered a protected object and will hourly have its ACL reset ( is considered protected and will have its ACL reset hourly )
  • Administrators
  • Account Operators
  • Server Operators
  • Print Operators
  • Backup Operators
  • Domain Admins
  • Schema Admins
  • Enterprise Admins
  • Cert Publishers
1) Remove the problem account from these groups 2)Using the dsacls utility (available in the Resource Kit for your version of Windows Server), you can change the AdminSDHolder object. By using this utility you can allow your Blackberry service account to be added to the AdminSDHolder object. This will allow the ability to add the Blackberry service account to users in protected groups and not have it overwritten. To do this, you will need to install the dsacls utility on a server, create a batch file containing the commands below, and run the batch file on the server with the utility installed: dsacls “cn=adminsdholder,cn=system,dc=mydomain,dc=com” /G “\SELF:CA;Send As” dsacls “cn=adminsdholder,cn=system,dc=<mydomain>,dc=com” /G “\SELF:CA;Receive As” dsacls “cn=adminsdholder,cn=system,dc=<mydomain>,dc=com” /G “\SELF:CA;Change Password” dsacls “cn=adminsdholder,cn=system,dc=<mydomain>,dc=com” /G “\SELF:RPWP;Personal Information” dsacls “cn=adminsdholder,cn=system,dc=<mydomain>,dc=com” /G “\SELF:RPWP;Phone and Mail Options” dsacls “cn=adminsdholder,cn=system,dc=<mydomain>,dc=com” /G “\SELF:RPWP;Web Information” dsacls “cn=adminsdholder,cn=system,dc=mydomain,dc=com” /G “\%BLACKBERRYSERVICEACCOUNT%:CA;Send As” You will need to add the Blackberry service account ( Bes Admin )  with Send As permissions again after this and it won’t get removed with the ACL Update
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
A user typing in Word and Outlook ( Using word as the email editior) had intermitent issues with her spell check not automatically detecting spelling mistakes as she wrote. Microsoft Office calls this “Check Spelling as your Type” Upon going to Tools , Options , Spelling & Grammer tab and pressing OK this starts the spelling as you type working , until you open up a new document and have to repear the process again. After trying all the obious things Check Spelling as you Type is Ticked Check Grammer as you Type is Ticked Check Grammer with Spelling is Ticked Checking “Do not checking spelling or Grammer” is unticked ( In Tools Language ) The problem turned out to be the problem with the detection of language automatically using the “Detect Language Automatically” tick box After unticking this and Selling the dictionary to English (U.K.) this solved the issue
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
If you have a Blackberry User you wish to move to another Blackberry Enterprise Server on a seperate blackberry domain ( which means they utlize different blackberry user databases) you will need to go through the following tasks : 1) Backup the Blackberry Device via Blackberry Desktop Manager 2) Delete the User from the Old Blackberry Enterprise Server , and make sure you choose : “Yes – Delete the user and remove the BlackBerry information from the user’s mail system” , this removes all the Blackberry information in Exchange for the User ( Hence the backup ) 3) Wipe the device ( Go to Options, Select Security Options, Select General Settings then Click the Menu key, Select Wipe Handheld, Click Continue, Type “blackberry”) 4) Perform a restore on the device with the blackberry backup you took 5) Setup the new user on the new server with an activation password 6) Perform a reactivation with the new enterprise server ( Option , Advanced Options , Enterpise Activation )
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
Recently someone had sent an JPG Image over , however on opening the image from Outlook with Windows 7’s  Photo Viewer it was showing the image as a slide show of five seperate images.Initially confused ( as a TIF is the only mulipage image format ), I thought the slideshow program was being clever and scanning through my Temp Folder and displaying all the photos in that folder, however upon reopening the image from a new location this was not the case. I opened the image up with tools such as Microsoft Office Picture Manager and Paint , and only the first page showed. Upon dragging the image into Infran Viewer, it straight away told me the image was infact a TIF image and would I like to change the file extension! I was amazed Windows opened these fine without trying to decode these as jpg instead of TIFS. So you can fool windows into thinking there are multipage jpgs, could be useful for accountants scanner in and archiving documents!
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
I was recently trying to setup a users home Windows Vista machine up for Terminal Services Web Access through the Active-X Control. Upon installing the Active X control I was given an error about the version for RDP. To find out the version of Remote Desktop Connection on your computer , open the Remote Desktop Client by clicking on Start , then in the Run or Search field then type mstsc and enter Now in the top left of the Remote Desktop Connection box , press the computer icon once , then click about. This machine only had Version 6.0.6000 which is the version Windows Vista comes with. Vista Service Pack 1 updates this to Version 6.0.6001 , which supports RDP 6.1 and the Terminal Services Web Access.
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)