Home Forums Discussions Problems Miscellaneous Error

Anyone ever had a "micellaneous error" when trying to start AC from a remote computer. Error: invalid function call or something or other?

Were you able to open it eventually. It sounds like a rather generic error. If you Googled it, you would probably get hundreds of hits.

I have gotten this error many times in the last few weeks, since the most recent upgrade. I have to log out and reboot both the server and the client computers

I have been able to recover from this error by running Amazing Utilities on the "main computer" and running the "Repair Connections" option.

Thanks guys. When I rebooted my main pc it went away.

In my office with 10 computers running on windows XP peer to peer - I get this error multiple times a day on one machine or another when starting (or trying to start) AC v 5.0.24. It is a big error window generated by AC. Sometimes restarting the "non-main" computer that give the error helps. Other times you have to reset the path (although it appears nothing is wrong with the path). Sometimes the main computer has to run amazing utilities and push the repair connections. Today it was the "main" computer. [and how on earth does the "main" computer not find itself] And It worked after running amazing utilities "check amazing charts." Didn't have to optimize a thing - just check it. No firewall on "main" computer. and the error only seems to bother one computer or another - others work just fine when the error pops up. Not sure if it is related to max connections in XP of 10? But we had no such error before the upgrade.

Is the main computer XP Pro? How much memory do you have on it?

you know, it is a problem that only occured once I installed 5.024. It may go away once I download the newer one. I sure hope so.

Bert: XP Pro with 1 GB of RAM. I took an exam room off-line last night - put LogMeIn ignition on it so I could rapidly connect to my personal office computer so now we have less computers trying to simultaneously connect to "main." Depending on how well my experiment goes - I may do the same for more of the exam rooms so as to minimize simultaneous connections to "main."

First, you shouldn't have to remote in to your office computer so the error goes away. I mean it may work, but you shouldn't have to.

A few things. Just ideas, can't say they will work.

First, RAM is cheap. I would add at least one more. SQL loves to eat RAM. There is a way to limit how much it takes. When you get the error, check how much RAM SQL is taking using your task manager on the main computer. Certainly, a reboot would fix that, so it could be part of it. Rebooting the other computer shouldn't make a difference but a fresh connection may.

If you find out it's the RAM, I can remote in and possibly limit the amount of RAM Express is taking. I would have to research it. I can do it easily on 2008, but not sure how to on XP Pro. I am sure it is out there on the net somewhere. But, I would have to do it for you.

I WOULD TRY THIS JUST FOR FUN:

Have you tried mapping all the drives on each computer to the server so the connection is constant? Or whatever it does, lol.

Bert,

Could you clarify your suggestion? Do you mean mapping the AC folder on the main computer or server to a drive letter on each client computer? I'm intrigued, does this create a more stable network connection?

John,

Good question. Notice my "whatever it does" at the end of my post. And, yes, I meant what you stated.

I do know as I am sure you do that a mapped drive will appear and behave very much the same way as if the physical folder were actually in the local computer and assigned a drive letter. Normally, shortcuts to shares on a server or application connecting to a shared database accomplish the same thing, but it can be advantageous and sometimes necessary for a program to use a mapped drive. eMedware is one of those programs. You HAVE to map the entire folder for it to work properly.

Obviously, this is not true with AC, but given Alberto was stating he was having issues with paths, I thought this may give him a more stable path on each client. It was just a thought. Easy enough to do.

One other comment about one of Alberto's post. He asked, "How does the main computer not find itself?" A program has to find a database whether it is on the server or on a computer a hundred miles away.

I am going to try the mapping idea. I get some random disconnects from the database on our server, and I'll report back whether it helps.

LOL, my signature is working.

Well, I tried mapping the AC folder as a disk on my client computer. Sad to say, I still got disconnected and when I tried to reconnect, the "Miscellaneous Error: invalid procedure call or argument" appeared.

Sorry it didn't work. I was hoping.

I recently upgraded the server and encountered this issue. The problem is related to security settings in the SQL Server files. We don't know what caused the problem.

We resolved this issue by going to the program files folder of Amazing Charts. Find all the files that are of SQL Server type. You can sort by this type if it helps. We had 6 files: 3 files that were duplicates. I forgot the names of the files. Right click on each of the files and check the Security permissions. For a quick fix, you can set each file to Everyone. For better security, set the security permissions to each individual user or group accessing the files.

As for the random disconnects with mapped drives, we had this problem too. Some of my map drives were randomly disconnecting and it was causing problems with Amazing Charts. According to Microsoft, this is designed by default to conserve server resources.

Use the net config server command to adjust settings and check your idle session time. You can disable this feature by typing the following in a command prompt (with admin rights):

net config server /autodisconnect:-1

Do this on all your computers. We have a small network so we don't care about conserving resources and connections but if you have a larger network, you will need a network administrator to monitor this stuff regularly and adjust resources.

References:

http://support.microsoft.com/kb/297684