Runtime Error '9' subscript out of range

Our company uses MSDE2000 for a Document Creation System. When a user
gets the [runtime error '9' subscript out of range]I have found no fix
without reinstalling the OS. I have not found the cause for the error.
Backups are unable to complete once this error occures. We have un
installed MSDE and reinstalled (also uninstall the software and
reinstalled it)
The five times I have seen this error everything work until the merge
proccess this along with unable to backup makes me think it is MSDE
related.
HELP
Joe Bullington
TechnologySupport
National Network Technology TEAM
One Valmont Plaza - Fourth Floor
Omaha, NE 68154
Toll Free: (888) 837-9709 ext. 3859
Local: (402) 964-3859
Email: joeb@.nnepa.com
General Support Email: support@.nnepa.comJoe NNEPA (joeb@.nnepa.com) writes:
> Our company uses MSDE2000 for a Document Creation System. When a user
> gets the [runtime error '9' subscript out of range]I have found no fix
> without reinstalling the OS. I have not found the cause for the error.
> Backups are unable to complete once this error occures. We have un
> installed MSDE and reinstalled (also uninstall the software and
> reinstalled it)
> The five times I have seen this error everything work until the merge
> proccess this along with unable to backup makes me think it is MSDE
> related.
This sounds like a Visual Basic error to me, so poking with MSDE
may not resolve the problem easily. You should probably debug
the document-creation system, or talk to the vendor if it is a
3rd party product.
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

Runtime Error

I got a game called Dungeon Runner from ncsoft, which I know to be a reputable company. It was a download a.ly game as it's free to download and play.

After installation I tried to play the game and received a Runtime Error. Here are the exact messages I got:

Runtime Error!

Program: C:...

This application has requested the Runtime to terminate in an unusual way.

Please contact the application's support team for more information.

Ok

If that wasn't bad enough, after I clicked ok, I got THIS message!

The exception unknown software exception (0x40000015) occurred in the application at location 0x7813461a.

Click on OK to terminate the program

Click on CANCEL to debug the program

When I click Ok nothing happens, and when I click Cancel nothing happens either (it doesn't debug the program.)

What am I supposed to do now? I've already tried uninstalling the program, and reinstalling it, and on the advice of the manufacturers I've updated my video card (though that didn't make any sence to me as to why I even got a runtime error.) I've been at this for 12 hours, and I'm getting very frustrated. Please help me if you can.

If it can be solved with DMO or SMO we would be glad to help you with that :-)

WesleyB

Visit my SQL Server weblog @. http://dis4ea.blogspot.com

|||

Well im having similar problems but the error was a bit different and i tried to get a version off my friend whitch had all the updates and now it is comming up with a new error and i cant fix it!!!!! i am sooooo anoyed !

any one got any suggestions add my msn and talk lol

well yer i need help my computer is so gay i always have problems with new software or games or anything realy !

thnx

Running SQL Server on a Desktop Machine

Hi,

The company I work at was going to install SQL Server 2005 on a server running Windows Server 2000. However this server is no longer available, and due to cost restraints we are unable to purchase another server.

I still wish to get SQL Server 2005 running, and have a spare desktop computer avaible. This computer is a P4 3.2GHz with 1GB of RAM and 40GB hard disk.
I was thinking of adding RAM and a larger hard disk, and installing Windows Server 2003 on it.

Is it advisable to run SQL Server 2005 (and Server 2003) on a desktop computer? Any comments or experiences of similar situations would be appreciated.

Thanks,
MattThere's lots of issues here;
1 What's it for?
2 Version
You have not mentioned which version of SQL Server 2005
3 Capacity
Your hardware spec. meets the minimum requirements, you can install SQL 2005, but what you will actually be doing with it will determine the hardware.
4 Availability
Again, what do you need to do on this server; server hardware is built to serve mission critical applications, the numbers might not look as good but you generally get a system that allows for RAID, hot swapping HDDs and memory, etc.
5 Maintenance & Support
E.g. If a HDD fails, will your hardware guys fix it, or will they say - what's this mickey-mouse setup?

And so on...|||Thanks for the reply, sorry I should have been more specific.

The version used would be the Standard Edition.

I am responsible for the reporting of our organisation. Currently data is taken from the enterprise system and reported on using Microsoft Access and Excel. So if I upgraded to SQL Server then it would be used to implement a data warehousing solution. Table updates would run in the morning, along with the emailing/printing of several reports. After that most usage would be via Excel queries. There would be around 20-30 users doing this, with no more than 10 accessing the SQL Server concurrently.

Eventually the SQL Server system would be moved to a server, but this cannot happen until 8 months or so. I am ready to start going live with a SQL Server solution, and want to use to desktop machine as a temporary solution. I want to know whether using this desktop will provide a workable solution. I know it is far from perfect, but considering we are currently running Access as a reporting database server, will the solution work temporarily?

Regarding maintennance and support, seeing it is not a mission critical solution, I had planned to backup the data files and any code created in BIDS on a seperate server. In the event of a disaster this would allow me to recreate the data warehouse on another hard drive. Again, it is an imperfect solution but I am hoping it would do the job until a server machine becomes available.

Purchasing a server is not really an option due to the price. The cost of SQL Server has already been approved, and if I go with this desktop machine only another $1200 or so will be needed for Server 2003 and hardware upgrades.

Any help or opinions with this would be great.|||You haven't said anything that makes me think it won't be able to handle the capacity, but I still would worry about a live service on a server-under-the-desk scenario.
Apart from the issues I've alreay mentioned, make sure you aren't breaking any corporate standards, laws or regulatory requirements for the data you are handling.

Running SQL Server 2000 with Win2003 Server

I'm not sure if i'm asking in the right place but I've to start some where.
Recently our company got our hands on the Windows 2003 Server Standard Editi
on and also SQL Server 2000 Standard Edition. We've tried to install both of
these onto a development s
erver and the autorun on the SQL Server 2000 CD prompts that it will not run
with any service pack below service pack 2. So we installed the database se
rver along with service packs 1, 2 and 3 into the server. Running the databa
se server on the local mach
ine proves that nothing is wrong where everything can run on the enterprise
manager and query analyzer. But when we turn to the client machines and trie
d to register the SQL Server instance with enterprise manager on the client
machines, it just returns "
Server non-existing or access denied" error, even when the password and user
name is correct (user logins set at the development server). Did we miss any
thing that we need to set or have we done the whole thing wrong? Can anybody
help?Are the clients able to access the server in other ways such as ping or smb?
If not, it might be the built-in firewall in 2003. You can find it by going
into the properties of the network connection.
"Chris" <honchein.choi@.newera.edu.my> wrote in message
news:514C4401-60B6-4D19-9605-34E2A5D01BB9@.microsoft.com...
> I'm not sure if i'm asking in the right place but I've to start some
where. Recently our company got our hands on the Windows 2003 Server
Standard Edition and also SQL Server 2000 Standard Edition. We've tried to
install both of these onto a development server and the autorun on the SQL
Server 2000 CD prompts that it will not run with any service pack below
service pack 2. So we installed the database server along with service packs
1, 2 and 3 into the server. Running the database server on the local machine
proves that nothing is wrong where everything can run on the enterprise
manager and query analyzer. But when we turn to the client machines and
tried to register the SQL Server instance with enterprise manager on the
client machines, it just returns "Server non-existing or access denied"
error, even when the password and username is correct (user logins set at
the development server). Did we miss anything that we need to set or have we
done the whole thing wrong? Can anybody help?|||I'm sure that all clients can't access to the database server, enterprise ma
nager, query analyzer, odbc connections, etc. i've checked the properties of
the network connection and the firewall wasn't activated automatically and
i can ping the server throu
gh tcp/ip protocol. that's y i dunno wut's wrong here. any ideas?
-- Johan wrote: --
Are the clients able to access the server in other ways such as ping or smb?
If not, it might be the built-in firewall in 2003. You can find it by going
into the properties of the network connection.
"Chris" <honchein.choi@.newera.edu.my> wrote in message
news:514C4401-60B6-4D19-9605-34E2A5D01BB9@.microsoft.com...
> I'm not sure if i'm asking in the right place but I've to start some
where. Recently our company got our hands on the Windows 2003 Server
Standard Edition and also SQL Server 2000 Standard Edition. We've tried to
install both of these onto a development server and the autorun on the SQL
Server 2000 CD prompts that it will not run with any service pack below
service pack 2. So we installed the database server along with service packs
1, 2 and 3 into the server. Running the database server on the local machine
proves that nothing is wrong where everything can run on the enterprise
manager and query analyzer. But when we turn to the client machines and
tried to register the SQL Server instance with enterprise manager on the
client machines, it just returns "Server non-existing or access denied"
error, even when the password and username is correct (user logins set at
the development server). Did we miss anything that we need to set or have we
done the whole thing wrong? Can anybody help?

Running SQL Server 2000 with Win2003 Server

I'm not sure if i'm asking in the right place but I've to start some where. Recently our company got our hands on the Windows 2003 Server Standard Edition and also SQL Server 2000 Standard Edition. We've tried to install both of these onto a development s
erver and the autorun on the SQL Server 2000 CD prompts that it will not run with any service pack below service pack 2. So we installed the database server along with service packs 1, 2 and 3 into the server. Running the database server on the local mach
ine proves that nothing is wrong where everything can run on the enterprise manager and query analyzer. But when we turn to the client machines and tried to register the SQL Server instance with enterprise manager on the client machines, it just returns "
Server non-existing or access denied" error, even when the password and username is correct (user logins set at the development server). Did we miss anything that we need to set or have we done the whole thing wrong? Can anybody help?
Are the clients able to access the server in other ways such as ping or smb?
If not, it might be the built-in firewall in 2003. You can find it by going
into the properties of the network connection.
"Chris" <honchein.choi@.newera.edu.my> wrote in message
news:514C4401-60B6-4D19-9605-34E2A5D01BB9@.microsoft.com...
> I'm not sure if i'm asking in the right place but I've to start some
where. Recently our company got our hands on the Windows 2003 Server
Standard Edition and also SQL Server 2000 Standard Edition. We've tried to
install both of these onto a development server and the autorun on the SQL
Server 2000 CD prompts that it will not run with any service pack below
service pack 2. So we installed the database server along with service packs
1, 2 and 3 into the server. Running the database server on the local machine
proves that nothing is wrong where everything can run on the enterprise
manager and query analyzer. But when we turn to the client machines and
tried to register the SQL Server instance with enterprise manager on the
client machines, it just returns "Server non-existing or access denied"
error, even when the password and username is correct (user logins set at
the development server). Did we miss anything that we need to set or have we
done the whole thing wrong? Can anybody help?
|||I'm sure that all clients can't access to the database server, enterprise manager, query analyzer, odbc connections, etc. i've checked the properties of the network connection and the firewall wasn't activated automatically and i can ping the server throu
gh tcp/ip protocol. that's y i dunno wut's wrong here. any ideas?
-- Johan wrote: --
Are the clients able to access the server in other ways such as ping or smb?
If not, it might be the built-in firewall in 2003. You can find it by going
into the properties of the network connection.
"Chris" <honchein.choi@.newera.edu.my> wrote in message
news:514C4401-60B6-4D19-9605-34E2A5D01BB9@.microsoft.com...
> I'm not sure if i'm asking in the right place but I've to start some
where. Recently our company got our hands on the Windows 2003 Server
Standard Edition and also SQL Server 2000 Standard Edition. We've tried to
install both of these onto a development server and the autorun on the SQL
Server 2000 CD prompts that it will not run with any service pack below
service pack 2. So we installed the database server along with service packs
1, 2 and 3 into the server. Running the database server on the local machine
proves that nothing is wrong where everything can run on the enterprise
manager and query analyzer. But when we turn to the client machines and
tried to register the SQL Server instance with enterprise manager on the
client machines, it just returns "Server non-existing or access denied"
error, even when the password and username is correct (user logins set at
the development server). Did we miss anything that we need to set or have we
done the whole thing wrong? Can anybody help?

Running SQL Server 2000 with Win2003 Server

I'm not sure if i'm asking in the right place but I've to start some where. Recently our company got our hands on the Windows 2003 Server Standard Edition and also SQL Server 2000 Standard Edition. We've tried to install both of these onto a development server and the autorun on the SQL Server 2000 CD prompts that it will not run with any service pack below service pack 2. So we installed the database server along with service packs 1, 2 and 3 into the server. Running the database server on the local machine proves that nothing is wrong where everything can run on the enterprise manager and query analyzer. But when we turn to the client machines and tried to register the SQL Server instance with enterprise manager on the client machines, it just returns "Server non-existing or access denied" error, even when the password and username is correct (user logins set at the development server). Did we miss anything that we need to set or have we done the whole thing wrong? Can anybody help?Are the clients able to access the server in other ways such as ping or smb?
If not, it might be the built-in firewall in 2003. You can find it by going
into the properties of the network connection.
"Chris" <honchein.choi@.newera.edu.my> wrote in message
news:514C4401-60B6-4D19-9605-34E2A5D01BB9@.microsoft.com...
> I'm not sure if i'm asking in the right place but I've to start some
where. Recently our company got our hands on the Windows 2003 Server
Standard Edition and also SQL Server 2000 Standard Edition. We've tried to
install both of these onto a development server and the autorun on the SQL
Server 2000 CD prompts that it will not run with any service pack below
service pack 2. So we installed the database server along with service packs
1, 2 and 3 into the server. Running the database server on the local machine
proves that nothing is wrong where everything can run on the enterprise
manager and query analyzer. But when we turn to the client machines and
tried to register the SQL Server instance with enterprise manager on the
client machines, it just returns "Server non-existing or access denied"
error, even when the password and username is correct (user logins set at
the development server). Did we miss anything that we need to set or have we
done the whole thing wrong? Can anybody help?|||I'm sure that all clients can't access to the database server, enterprise manager, query analyzer, odbc connections, etc. i've checked the properties of the network connection and the firewall wasn't activated automatically and i can ping the server through tcp/ip protocol. that's y i dunno wut's wrong here. any ideas
-- Johan wrote: --
Are the clients able to access the server in other ways such as ping or smb
If not, it might be the built-in firewall in 2003. You can find it by goin
into the properties of the network connection
"Chris" <honchein.choi@.newera.edu.my> wrote in messag
news:514C4401-60B6-4D19-9605-34E2A5D01BB9@.microsoft.com..
> I'm not sure if i'm asking in the right place but I've to start som
where. Recently our company got our hands on the Windows 2003 Serve
Standard Edition and also SQL Server 2000 Standard Edition. We've tried t
install both of these onto a development server and the autorun on the SQ
Server 2000 CD prompts that it will not run with any service pack belo
service pack 2. So we installed the database server along with service pack
1, 2 and 3 into the server. Running the database server on the local machin
proves that nothing is wrong where everything can run on the enterpris
manager and query analyzer. But when we turn to the client machines an
tried to register the SQL Server instance with enterprise manager on th
client machines, it just returns "Server non-existing or access denied
error, even when the password and username is correct (user logins set a
the development server). Did we miss anything that we need to set or have w
done the whole thing wrong? Can anybody help?