- Is the Excel file local to your computer (on your workstation harddrive)?
- Is this a shared database?
- If it is a shared database, have you tried moving the Excel file to the server and testing the import?
- To determine if it is a problem with the Excel file itself, manually create an Excel file and put in 2 records (along with a header row) and test importing that file.
- To determine if it is a problem with the database, open the ACT! demo database and attempt to import your original file and then the test file (if original fails).
- If you are using either a Vista or Windows 7 operating system, try running ACT! 'as admin'. To do this: close ACT! > right click on the ACT! icon > select 'Run As Administrator > test import.
Greg, thanks for your help. I work with Joel, and consulted our system administrator on this issue.
When you are attempting the import:
- Is the Excel file local to your computer (on your workstation harddrive)? no, it is on a network drive.
- Is this a shared database? -- yes
- If it is a shared database, have you tried moving the Excel file to the server and testing the import?
ACT! is accessed only via Citrix XenApp. Once logged in to Citrix, the user logs in to ACT! and attempts to import excel file from there. We had our data specialist log directly into the server itself and still encountered this issue.
- To determine if it is a problem with the Excel file itself, manually create an Excel file and put in 2 records (along with a header row) and test importing that file. We have attempted this with multiple excel files, both .xls and .xlsx file types; we also attempted the import from different file locations, including putting a copy directly on the server. We receive the same exact error message regardless of the file location, file name or version of excel the file is saved onto. This appears to be a system-generated file. Assuming ACT! was accessing the file for some other purpose, we kicked all users from the server, rebooted and logged just the data specialist in, directly to the server, but the issue persisted.
- To determine if it is a problem with the database, open the ACT! demo database and attempt to import your original file and then the test file (if original fails). we did not try this. See below for how we got around the issue (but it still is not solved).
- If you are using either a Vista or Windows 7 operating system, try running ACT! 'as admin'. To do this: close ACT! > right click on the ACT! icon > select 'Run As Administrator > test import. The user we are having import files is already logged in as an admin.
We were originally running ACT! from a Citrix XenApp environment, duplicated across 8 servers. Individual profile settings were regularly lost using this configuration, so we forced ACT! onto a single server (call it Server #1). I believe this is where the issue began. We ran all of our scenarios off of this one server, and the issue persisted, so instead our system administrator forced all users to access ACT on a different server (Server #2), and the error did not recur again.
Currently all users accessing ACT via Citrix are funneled through "Server #2", but we are concerned it will show up again. Do you have suggestions regarding what may have happened and how we can avoid this issue in the future? Was this just a corrupted install of ACT! ? Is it due to having multiple users logged on simultaneously? We currently have 25 licenses, with a max of perhaps 15 users logged in at any one time.
Unfortunately I'm not able to answer exactly what caused the problem, but my first thought is that there was a bad install on the first server. If the first server is still available, you can test this by reinstalling ACT! on it and testing. Having multiple users signed on shouldn't cause a problem (unless they are all signed on with the exact same ACT! username, but you've got 25 licenses).
Note: If these are Windows 7 or Vista systems, 'Run As Administrator' is different than having a Windows user defined as 'Administrator'. The 'Run As Administrator' option provides additional authority to the program, even for a Windows Admin username.
I know that this thread is long dead but I leave this here for the record if anyone else has a similar problem esp. in Windows 7
My exact error message was
act! error message 13.0.401.0ImportCSV.txt is denied
but I found this thread searching act! error message ImportCSV.txt is denied
Having had the import working fine it stopped after Act! has stopped respoding and I had forced the application to quit via the Task Manager.
Following some suggestions above I moved the .xls file around, re-named it etc.
However, what sorted the problem for me was launching Excel as adminstrator
As Greg notes
If these are Windows 7 or Vista systems, 'Run As Administrator' is different than having a Windows user defined as 'Administrator'. The 'Run As Administrator' option provides additional authority to the program, even for a Windows Admin username.
Hope, like Arnie Saknussen bones, this might help others!
