Search found 2 matches

I took your suggestion and tried removing the duplicate “All” entry, and even removed the entire line and am still not able to import this file. Proceeding with this thought process of a single entry causing this I attempted to isolate the offending line. I started by removing all but the top 10 lines, but this too failed. I then took the top 10 lines from the file and it again failed. The part of this that is most confusing is I’m exporting this recip.txt file from the same version of PageGate I’m trying to import to. I have reviewed the comma separated items and it all seems to be right on. I have even run a line by line (for the first ten lines) comparison of an export from the new server (upgrade of the NotePage database) and these exports, and it’s all consistent. I am really at a loss on why it won’t import.

I have been working with this for weeks and finally felt I had all the bugs worked out, but this came back. I am consolidating an old Notepager and not as old Pagegate server onto newer hardware. I have taken and copied the databases for each, and exported the databases for both as well to a location on the new server. I proceed to install Pagegate 4.0 on the new server, then on it’s first start, point to the old notepager DB, followed by the upgrade notification. I accept and it upgrades the database fine. Then I start to import the old pagegate items (carriers.txt, groupmem.txt etc.) And they all import perfectly, until I reach the recip.txt. At this point I would receive the message

In my testing I verified file permissions, and I’m the domain admin with full rights to this domain member server, but found that after reaching this point I was able to run the “Rebuild Database” tool, and then the import would work fine.

Now, I’m on the new server following all I had done before in test, and I receive this same error message. I have tired several times to rebuild the database, and still unable to import the 561 user (recip.txt) file. All the others (carrier, groupmem, connect and settings.txt) imported fine from the exact location. Having successfully done this in test using production data I even tried exporting the recip.txt data from it and still receive the same error. I’m stumped.

Thanks for your input.

Author	Message
Topic: Excessive file errors
supergeniusdan Replies: 4 Views: 12181	Forum: PageGate Support Posted: Mon Oct 02, 2006 11:31 am Subject: Excessive file errors
supergeniusdan Replies: 4 Views: 12181	I took your suggestion and tried removing the duplicate “All” entry, and even removed the entire line and am still not able to import this file. Proceeding with this thought process of a single entry causing this I attempted to isolate the offending line. I started by removing all but the top 10 lines, but this too failed. I then took the top 10 lines from the file and it again failed. The part of this that is most confusing is I’m exporting this recip.txt file from the same version of PageGate I’m trying to import to. I have reviewed the comma separated items and it all seems to be right on. I have even run a line by line (for the first ten lines) comparison of an export from the new server (upgrade of the NotePage database) and these exports, and it’s all consistent. I am really at a loss on why it won’t import.
Topic: Excessive file errors
supergeniusdan Replies: 4 Views: 12181	Forum: PageGate Support Posted: Fri Sep 29, 2006 3:07 pm Subject: Excessive file errors
supergeniusdan Replies: 4 Views: 12181	I have been working with this for weeks and finally felt I had all the bugs worked out, but this came back. I am consolidating an old Notepager and not as old Pagegate server onto newer hardware. I have taken and copied the databases for each, and exported the databases for both as well to a location on the new server. I proceed to install Pagegate 4.0 on the new server, then on it’s first start, point to the old notepager DB, followed by the upgrade notification. I accept and it upgrades the database fine. Then I start to import the old pagegate items (carriers.txt, groupmem.txt etc.) And they all import perfectly, until I reach the recip.txt. At this point I would receive the message In my testing I verified file permissions, and I’m the domain admin with full rights to this domain member server, but found that after reaching this point I was able to run the “Rebuild Database” tool, and then the import would work fine. Now, I’m on the new server following all I had done before in test, and I receive this same error message. I have tired several times to rebuild the database, and still unable to import the 561 user (recip.txt) file. All the others (carrier, groupmem, connect and settings.txt) imported fine from the exact location. Having successfully done this in test using production data I even tried exporting the recip.txt data from it and still receive the same error. I’m stumped. Thanks for your input.