 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
| HomeDiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWordDirectoryUser Groups Related Topics Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ... |
MS Office Forum / Outlook / Contacts / June 2007Permanent loop security warning importing Contacts from PST file
Hi, I wonder if someone could help me, I'm kind of at my wit's end with this. Apologies for post length, I figured more detail upfront is better. Here's the deal... I got a new 32-bit Vista laptop, copied all the Outlook data over and reinstalled Outlook (2002). I used Windows Update when prompted, which patched me up to SP3. I opened all my old PST files that I use to sort / store emails etc. So far so good. Then I tried to import my old primary mailbox into the new mailbox on the new install. It imported most of the old emails, sent items etc but then when it got to Contacts, I got the Outlook security warning message: "A program is trying to access email addresses... " and the options to allow access, Yes or No. I clicked Yes, and the message pops up again. I click yes again. Same thing. Short story, no matter what I do I can't clear this warning, it just keeps popping up. This includes terminating the application through Task manager, and rebooting. When I restart Outlook, it checks the PST files that were not closed properly, then carries on trying to import the contacts, and the warning pops up again. I'd be very grateful if someone can advise how to stop Outlook from looping like this, short of uninstalling and reinstalling and repatching (and I don't even know whether THAT would work!) Thanks for ploughing through to the end, and thanks in advance for your help! :) I don't understand why you would ever use import to transfer Outlook data when we have posted so clearly and so frequently that importing is never the correct way to transfer Outlook data. Did you think your results would be different? If so, why? How do you expect us to help you? Your post is far to deficient on the details we would need to do so. You mention PST files and mailboxes in the same sentence. They do not belong in the same sentence.  SignatureRuss Valentine [MVP-Outlook] > Hi, I wonder if someone could help me, I'm kind of at my wit's end with > this. [quoted text clipped - 31 lines] > end, > and thanks in advance for your help! :) I see my preemptive thanks were misdirected. Russ, my deepest, abject, humblest apologies. I confess - I didn't read every post in the discussion board about importing outlook data. I'm a reasonably competent user, but I'm no expert programmer, so I read the help file, searched the MS KB, and when I found no information there, I looked for "Help from the Experts" as MS put it. I searched the relevant group, but could find no reference to the problem I was experiencing. I didn't note any advice that said "don't import" along the way. So I posted my specific problem, hoping for a specific answer. Sorry it was so "lacking in detail" that I shouldn't have "expected you to help me". Your answer is extremely unhelpful, but it must have given you you a warm glow of superiority. I can't think of any other reason you would have made such a pointless post. Thanks for nothing, I'll sort it out myself without any "Help from the Experts"... AR > I don't understand why you would ever use import to transfer Outlook data > when we have posted so clearly and so frequently that importing is never the [quoted text clipped - 37 lines] > > end, > > and thanks in advance for your help! :) The other alternative of course would be to post accurate and relevant details that would allow someone to help from the distance of a newsgroup. Not sure why you were expecting help unless you were expecting us to be mind readers. Post your problem more clearly. Include accurate steps to repro the problem. Recognize that the Outlook version you are using is no longer supported and does not work reliably on Vista. No one here is a programmer. Nor would you have needed to read "every post" to discover that importing is never the correct way to transfer Outlook data. There are countless posts here that tell you how to migrate Outlook data correctly. You only needed to read one. SignatureRuss Valentine [MVP-Outlook] >I see my preemptive thanks were misdirected. > [quoted text clipped - 73 lines] >> > end, >> > and thanks in advance for your help! :) *sigh* > The other alternative of course would be to post accurate and relevant > details that would allow someone to help from the distance of a newsgroup. Details provided are accurate. To imply otherwise is to imlpy that I am lying. Are you implying that I am lying? Why would you make such an accusation against someone who is merely asking for assistance? Are you really THAT arrogant? In what way are the details I provided irrelevant? Maybe you, in your infinite clarity and wisdom, would like to advise what additional information you need to provide some advice. (then look up "Sarcasm" on dictionary.com) > Not sure why you were expecting help unless you were expecting us to be mind > readers. I wasn't expecting you to be mind readers. I wasn't expecting you to be completely obnoxious, arrogant tossers either, though, so I suppose anything's possible. > Post your problem more clearly. Include accurate steps to repro the problem. What don't you understand? Actually, don't answer that. > Recognize that the Outlook version you are using is no longer supported and does not work reliably on Vista. From what I can tell from the Microsoft site, Outlook is actually supported as far as "Security related issues". From my (customer's) perspective, that's exactly what this is - an issue created by a security patch, applied automatically by Microsoft. And sure, I could upgrade. Except I see no reason to from a functionality perspective, and am prevented from doing so cost-effectively by the fact that MSoft no longer offer an upgrade to Outlook only, just Office Standard (of which I use nothing except Outlook). And seeing as this problem does not appear to be related to the OS, why highlight the fact that MS is incapable of writing backward-compatible software? Or rather that their profit margins are based on a forced-upgrade policy, from the code up? > No one here is a programmer. Nor would you have needed to read "every post" > to discover that importing is never the correct way to transfer Outlook > data. There are countless posts here that tell you how to migrate Outlook > data correctly. You only needed to read one. Yes, but of course, as anyone with an ounce of sense would realise, I only started reading these posts AFTER THE PROBLEM HAD OCCURRED. Why would I come and start reading through discussion boards to look for issues that hadn't even occurred yet? Why would I know ahead of the fact that a built-in application function would cause the entire system to become unusable? (Except of course that I *should* have known better... after all, I've used MS apps before!) My programmer reference was because most of the posts/KBarticles etc I did read before posting my question related to the SP3 patch causing problems for people writing programatic interfaces to Outlook, and corresponding developer workarounds. Kindly don't reply to my question any more, Russ, you clearly have nothing constructive to say. AR > >I see my preemptive thanks were misdirected. > > [quoted text clipped - 30 lines] > >> and > >> mailboxes in the same sentence. They do not belong in the same sentence. The precise steps that trigger the security prompt were needed. Also, what you meant by "importing my old primary mailbox." "Mailbox" refers to Exchange and implies you are running against Exchange server. Are you? We have posted many reasons not to import Outlook data, but I've never seen it trigger the security prompt before so this may be a new problem caused by running an older version of Outlook on an OS on which it is not supported. Normally you just open a PST file. What happens if you create a new Outlook profile, repair this PST file, then open it in the new profile? SignatureRuss Valentine [MVP-Outlook] > *sigh* > [quoted text clipped - 116 lines] >> >> mailboxes in the same sentence. They do not belong in the same >> >> sentence. Good point. I would be curious to know the answers also. Nikki > The precise steps that trigger the security prompt were needed. Also, what > you meant by "importing my old primary mailbox." "Mailbox" refers to [quoted text clipped - 135 lines] >>> >> mailboxes in the same sentence. They do not belong in the same >>> >> sentence. Please take a look at the following link for a possible solution: http://www.slipstick.com/outlook/esecup.htm#autosec The "object model guard" feature of the patch imposes two extreme restrictions on automating Outlook from add-ins that use either the Outlook object model or Simple MAPI: a.. If an add-in tries to send an Outlook message, the user gets a notification pop-up and must explicitly authorize or deny each attempt to send. The user must wait 5 seconds before the Yes button becomes available to click. b.. If an add-in tries to access address information in an Outlook item or the address book or to save an Outlook item as a file, the user gets a notification pop-up and can deny access, authorize a one-time access or extend access for a period of several minutes. PDA sync utilities are an example of the kind of application that will be affected by this restriction. I used to suggest the "Express Click Yes" which can be found on the page that the link above takes you to. I am a little rusty on this issue but I believe the above link will offer you a solution. Nikki >I see my preemptive thanks were misdirected. > [quoted text clipped - 73 lines] >> > end, >> > and thanks in advance for your help! :) Thanks, Nikki, for your blessedly polite and helpful response. OK, I read through the slipstick article, and a bunch of the related ones. I tried the ClickYes app, which installed and ran fine, but Outlook now "Stops working" (in Vista terminology). I've given up trying to repair the original problem, and decided to start again with a clean install. However it is currently proving more difficult than I would have expected to uninstall and reinstall Outlook... It uninstalls fine, removes all the files, then reinstalls OK but it has clearly retained the settings from the previous installation (I can see emails in the inbox, and I'm prompted for account login info. Then the original Outlook security warning message appears again ("A program is trying to access email addresses... ") I'm currently searching for advice on completely removing outlook 2002, so I'll look in the KB and relevant forums. If you have any advice, I'd really appreciate it, but no urgency. Thanks again for your help. AR > Please take a look at the following link for a possible solution: > http://www.slipstick.com/outlook/esecup.htm#autosec [quoted text clipped - 18 lines] > > Nikki > OK, I read through the slipstick article, and a bunch of the related > ones. > I tried the ClickYes app, which installed and ran fine, but Outlook > now "Stops working" (in Vista terminology). Express ClickYes is a subversion of Outlook's object model guard and if your PC is ever compromised to that it becomes a mailbot, you'll never know it. You're better off trying this tool: http://www.mapilab.com/outlook/security/ > I've given up trying to repair the original problem, and decided to > start again with a clean install. However it is currently proving [quoted text clipped - 5 lines] > warning message appears again ("A program is trying to access email > addresses... ") Uninstalling and reinstalling Outlook does not affect the mail profile, which exists in the Windows Registry and not touched by the reinstallation. Try creating a new mail profile using the Mail applet in the Control Panel. You'll have to enable the 32 bit Control Panel option to see it, though. SignatureBrian Tillman A simple reinstall will not clean these files up. Close Outlook first, then: a.. Search your hard drive for *.ost and delete all found (Be sure to search in hidden files) b.. Search your hard drive for Outcmd.dat and delete it. (This file holds your customized toolbar settings) c.. Search your hard drive for Views.dat and delete it. (This file holds your customized system folder views settings) d.. Search your hard drive for extend.dat and delete it. (this file holds your Installed add-ins information) e.. 2003: Outlook.xml (This file includes Shortcuts, Calendar, and Contact links.) a.. The navigation pane settings are profile-specific and are stored in an .xml file with the profile name, in the Application Data\Outlook folder. To clear all navigation pane customizations, start Outlook once with the /resetnavpane switch. Try opening Outlook again using the switch : a.. /CleanViews Restores default views. All custom views you created are lost. b.. /ResetOutlookBar Rebuilds the Outlook Bar. Some of the folders might be hidden folders. To view them I do the following on my XP machine, I am not well versed on Vista. Windows XP 1.. Click Start, and then click My Computer. 2.. On the Tools menu, click Folder Options, click the View tab, and then click the Show hidden files and folder option. Nikki > Thanks, Nikki, for your blessedly polite and helpful response. > [quoted text clipped - 44 lines] >> >> Nikki Outlook version aside (Vista & O'2002 and whether or not there are any different operational issues), the security message you're getting generally has an option to "allow" for "x" number of minutes which would alleviate some if not all of the issue. That aside, if you're importing from your original PST file, skip the "import process" altogether and simply open the old PST file on Vista and make it your "default" mailbox. No need to do anything else. There are times when importing/exporting is the correct approach - this just isn't one of those times since it is totally unnecessary. Karl ___________________________________________________ Karl Timmermans - The Claxton Group ContactGenie - Importer 1.3 / DataPorter 2.0 / Exporter "Power contact importers/exporters for MS Outlook '2000/2007" http://www.contactgenie.com > Hi, I wonder if someone could help me, I'm kind of at my wit's end with > this. [quoted text clipped - 31 lines] > end, > and thanks in advance for your help! :) Hi Karl, thanks for your advice too. Couple of specific responses to your comments below... Cheers AR > Outlook version aside (Vista & O'2002 and whether or not there are any > different operational issues), the security message you're getting generally > has an option to "allow" for "x" number of minutes which would alleviate > some if not all of the issue. I have tried all of the options presented by the warning - Yes, No and Allow for 1-10 mins. Whenever I click any available option on the warning box, a new warning box appears instantly to replace it. I had thought maybe it was just giving me a warning for every contact in my address book, and therefore perhaps I just needed to permit for each contact (I don't have THAT many, maybe 100-150) but having tried clicking about 500 times I gave up and figured that wasn't the answer :) > That aside, if you're importing from your original PST file, skip the > "import process" altogether and simply open the old PST file on Vista and > make it your "default" mailbox. No need to do anything else. There are times > when importing/exporting is the correct approach - this just isn't one of > those times since it is totally unnecessary. Right, that's great to know, thanks for that. If I can get Outlook to work AT ALL in the future, I'll certainly do that. Wish I'd known before, but hey - hindsight is always 20-20... :) Thanks very much for helping... AR > Karl > [quoted text clipped - 3 lines] > "Power contact importers/exporters for MS Outlook '2000/2007" > http://www.contactgenie.com Not having all that much experience with importing PST files (and especially not under Vista/O'2002) - hard to guess what the problem is as to why the security wrapper is generating all those messages. The times we have imported PST's to simulate a customer issue (customer using a contact folder that was previously imported), generally ended up with nothing but aggravation. Am sure there is a time when importing from a PST is the "correct method of choice" - just haven't run across it yet (my guess is that it may have had some legitimate use when Outlook was originally released way back when but is now one of those "features" that has outlived it's usefullness). If this was one of our boxes and things weren't working correctly - would start fresh on your Vista box - a) uninstall Office, b) re-install, and c) copy your PST file over making it the new default mailbox - just to see if things improved rather then try and figure out why things are happening in the event that "compound" issues are at play. Also, you may also find this page of interest from Diane Poremsky's "Outlook Tips" website: http://www.outlook-tips.net/howto/vista.htm Karl ___________________________________________________ Karl Timmermans - The Claxton Group ContactGenie - Importer 1.3 / DataPorter 2.0 / Exporter "Power contact importers/exporters for MS Outlook '2000/2007" http://www.contactgenie.com > Hi Karl, thanks for your advice too. Couple of specific responses to your > comments below... [quoted text clipped - 41 lines] >> "Power contact importers/exporters for MS Outlook '2000/2007" >> http://www.contactgenie.com The problem is resolved; Many thanks to all for their suggestions and advice. For those that are interested, some further details on my steps to resolution are below. The key issue was that the warning message, having originally come up during the import of the contacts (from a PST file) was appearing again every time I opened Outlook. After some basic steps to counter the warning, I gave up and tried to uninstall and reinstall Outlook. This proved a lot harder than it looked; as Brian & Nikki pointed out, the Uninstall didn't remove the mail profile, so after every uninstall & reinstall, Outlook would restart with all the same settings and most importantly, with the perpetual warning message reoccurring. So even removing the application and starting again, didnt get round the problem! I tried the Express ClickYes app, and with it running starting outlook didn't cause the warning message to appear BUT Outlook did immediately crash. However, the detail provided under the Vista "Stopped Working" message did advise that the module involved was OutlookAddinSetup, which after some investigation turned out to be a Creative add-in installed as part of the original Dell OS image. I uninstalled the OutlookAddin from Control Panel, and Outlook started fine with ClickYes running. Since then, I've disabled and uninstalled ClickYes and Outlook still starts up fine. I think, as I always thought, that I just needed to get pst the warning for it to sort itself out. Russ, my reference to Mailbox was probably misterminology due to the label on the folder list, which by default is [Mailbox - username]. What I was originally trying to import was my old default outlook.pst file. Sorry if the inexpert terminology caused confusion. Nikki, thanks for your advice, it looks like I worked around it in the end without having to hunt down and delete all the files... And Karl, thanks for the link, useful information. Cheers all AR Thank you for sharing your experience with us. Do you happen to remember what was the name of the addin was? If not, no worries. Glad you are back to good working order. Nikki > The problem is resolved; Many thanks to all for their suggestions and > advice. [quoted text clipped - 41 lines] > Cheers all > AR > Thank you for sharing your experience with us. Do you happen to > remember what was the name of the addin was? If not, no worries. Glad > you are back to good working order. Nikki, here's what he said: >> However, the detail provided under the Vista "Stopped Working" >> message did advise that the module involved was OutlookAddinSetup, That is the name of the app. This particluar app is part of "Dell MediaDirect", I believe. SignatureBrian Tillman Duh! Thanks Brian. I've seen you mention this little addin on several occasions. I'll have to tuck this away in my list of Outlook irritants. Nikki >> Thank you for sharing your experience with us. Do you happen to >> remember what was the name of the addin was? If not, no worries. Glad [quoted text clipped - 7 lines] > That is the name of the app. This particluar app is part of "Dell > MediaDirect", I believe. Dear Adam I have finally managed to resolve the same excruciating problem - after syncing with my PDA, also using outlook 2002 with vista on a new laptop- thanks to you. I have been trolling through these threads for almost a week and I was getting desperate. I had managed to install and reinstall successfully, again to no avail. I haven't spent much time on these threads before and I am quite startled how unpleasant people can be, I'm not a complete novice and I just followed sequential instructions from microsoft and also failed to get the appropriate help in the all the guides etc when it went pear shaped- I also didn't see any warnings. Thank you so much for your post Sisterm > The problem is resolved; Many thanks to all for their suggestions and advice. > For those that are interested, some further details on my steps to [quoted text clipped - 32 lines] > Cheers all > AR Adam Radcliffe is a jerk...he should be reported for responding to inquiries.. I had the same trouble and spent 2 days trying to figure it out and was even on the phone with tech support and they could not figure it out...i deleted the "outlookaddins" and it worked...thanks Adam for your follow up...pure genious. Does anyone think there will be any reprecussions to this? I too am a novice and would never be able to write or think as an expert. > Dear Adam > [quoted text clipped - 52 lines] > > Cheers all > > AR I meant to say Russ Valentine was a jerk...I hate people like that. > Adam Radcliffe is a jerk...he should be reported for responding to inquiries.. > [quoted text clipped - 63 lines] > > > Cheers all > > > AR I don't know Russ but I believe that your comment about him is uncalled for. He was trying to help you and if his advise was not correct in this case, that is unfortunate. He and many other people spend a lot of time in these newsgroups trying to help people like you and me. I always want someone to try to help me. SignatureNeil >I meant to say Russ Valentine was a jerk...I hate people like that. > [quoted text clipped - 96 lines] >> > > Cheers all >> > > AR You posted in a thread that is long expired in most news readers. You failed to quote any portion of the post that would support your claim. You posted an insult but no constructive criticism. You misdirected that insult. You seem to be one clever fellow. SignatureRuss Valentine [MVP-Outlook] >I meant to say Russ Valentine was a jerk...I hate people like that. > [quoted text clipped - 96 lines] >> > > Cheers all >> > > AR |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.