SQL connection issues

Paintedeyes87

Junior Member
Jan 31, 2010
8
0
61
Hello

for the last month i've been battling issues with our sql server(2000). We had a power outage and I updated the windows server 2003 with a windows update. I've never had issues in doing so. This is a medical office and we all use an EMR called "Versaform" they all connect to the server to access the database. What is very odd is now each computer has to be administrator for the program to run properly. If i'm under a limited user I get this error, "Transaction Error Code: -1
Database Error Code: 10004".

I'm not very familiar with sql servers and such but a lot of people are unsure what the issue is. Even Versaform said it's on our end and not theirs. I've tried giving everyone full permissions on the program and everything. It's very annoying to me and I especially dont want staff to be logged under administrator because they can certainly ruin computers.
Thanks!
 

her209

No Lifer
Oct 11, 2000
56,336
11
0
Did the power cut out in the middle of Windows Server update? Also, it could be one of the updates that are affecting the SQL connections.
 

Paintedeyes87

Junior Member
Jan 31, 2010
8
0
61
no, we didn't lose power during the updates. I really do think it was one of those updates. we have a bunch of security updates for windos server 2003, security for IE 8, windows malicious software removal tool, update rollup for active x killbits, security update for .net framework 2.0 sp2 and 3.5 sp1. no idea if those mean anything haha.
 

seepy83

Platinum Member
Nov 12, 2003
2,132
3
71
Have you looked at the logs (SQL and System/Event Viewer) to see if there's anything to help narrow it down?
 

Paintedeyes87

Junior Member
Jan 31, 2010
8
0
61
i'm not entirely sure what to look for but i'll post what i think might be of use haha.

on the event view for windows server 2003 i see some warnings "supersocket info:(spnRegister): Error 1355" that comes up a couple of times today. and source of that is MSSQLSERVER.

under system in the event viwer i'm seeing a ton of errors and it has to be when i'm trying to run versaform. Event ID: 7000 and source is Service contorl manager.

when on the sql service enterprise manager looking at the sql server logs i'm not really seeing much i can take a screenshot if needed but i do see a common one which is error :50000, severity:1, state:1.

Obviously I do not have a degree in this nor did I set this whole system up but i'm the only one who is available for this.
 

Emulex

Diamond Member
Jan 28, 2001
9,759
1
71
what is the maintenance plan? you need to make sure it has one. it should do a integrity check, re-index, then backup. if the database is in simple mode (probably for your admin skills) you would then backup the database to a disk location - this would truncate the log files.

Sql server is easy :) google t-sql or sql server 2005 and your question.

if its running 2000 sql server - it is not vss aware and requires to be shutdown and restarted to hot-backup the machine (assuming you backup the machine).

1. check the maintenance plan to make sure maintenance is being done.
2. the log files and eventvwr will show the maintenance plan being done in applications.

google dude. There's some great private forums like sqlexchange.

sql server is like an o/s in itself - not hard to pick up - very powerful.
 

ScottMac

Moderator<br>Networking<br>Elite member
Mar 19, 2001
5,471
2
0
Sounds like a corrupted rights table.
If you don't know how to fix it, bring in a pro... there's a large chance of doing serious damage and losing it all.
 

Paintedeyes87

Junior Member
Jan 31, 2010
8
0
61
ya i agree probably need to get a real pro in here. I discovered that the client computers have to use the administrator login and all the same password. these are the same exactly login info used on the server. I did a test while on a client computer that once i changed the password to another, the program did not work but it worked as soon as i changed it back. very odd.
 

seepy83

Platinum Member
Nov 12, 2003
2,132
3
71
You said in the first post that Versaform told you it's a problem on your end. I would talk to them again and ask them how to set up rights/permissions so that each of the users can use their own (non-administrator) account. Someone familiar with MS SQL would probably be able to figure it out, but I would expect the Software Developer to help you through this without the need for you to bring in a third party.