Typing in net use in dos the following error occurs error 1734 - array bounds invalid

Typing in net use in dos the following error occurs error 1734 - array bounds invalid
LVL 2
knightfrankAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

sjklein42Commented:
I wonder if you have a batch file or an executable called "net" that is interfering with the built-in NET command in DOS.

Try directly running the net command using the full path and see if the error goes away:

C:\WINDOWS\system32\net.exe
0
knightfrankAuthor Commented:
No this did not work see below :


C:\>c:\windows\system32\net.exe
The syntax of this command is:


NET [ ACCOUNTS | COMPUTER | CONFIG | CONTINUE | FILE | GROUP | HELP |
      HELPMSG | LOCALGROUP | NAME | PAUSE | PRINT | SEND | SESSION |
      SHARE | START | STATISTICS | STOP | TIME | USE | USER | VIEW ]


C:\>c:\windows\system32\net.exe net use
The syntax of this command is:


NET USE
[devicename | *] [\\computername\sharename[\volume] [password | *]]
        [/USER:[domainname\]username]
        [/USER:[dotted domain name\]username]
        [/USER:[username@dotted domain name]
        [/SMARTCARD]
        [/SAVECRED]
        [[/DELETE] | [/PERSISTENT:{YES | NO}]]

NET USE {devicename | *} [password | *] /HOME

NET USE [/PERSISTENT:{YES | NO}]



C:\>net use
System error 1734 has occurred.

The array bounds are invalid.
0
knightfrankAuthor Commented:


C:\>c:\windows\system32\net.exe use
System error 1734 has occurred.

The array bounds are invalid.

0
Webinar: Miercom Evaluates Wi-Fi Security

It's not just about Wi-Fi connectivity anymore. A wireless security breach can cost your business large amounts of time, trouble, and expense. Plus, hear first-hand from Miercom how WatchGuard's Wi-Fi security stacks up against the competition in our upcoming webinar!

sjklein42Commented:
There is a Microsoft Hotfix for this:

http://support.microsoft.com/?id=2454533

The problem was apparently caused by this update:

KB980802

Uninstalling KB980802 fixed the problem for some people but the Hotfix covers it.

See this discussion:

http://social.answers.microsoft.com/Forums/en-US/vistawu/thread/28bc2814-319e-446d-97b4-fd164c4e4d9a
0
knightfrankAuthor Commented:
I could not find the hotfix on http://support.microsoft.com/?id=2454533
 and i went through my updates and could not find KB980802 in my updates
0
sjklein42Commented:
Hello again.  I guess "no news is good news" doesn't apply here.  Sorry to hear it.

I have not found any other suggestions regarding this error.  The message often seems connected to Microsoft's Visual Studio.  Do you have Visual Studio on that PC, even if it is not running?

Maybe you should make a "Request for Attention" to see if anyone else has an idea.
0
knightfrankAuthor Commented:
im using winxp
0
sjklein42Commented:
Like I said, I don't have the answer, but my thoughts are this:

One of the entries that NET USE is trying to display must be upsetting it.  NET USE shows the list of mapped network drives.  Do you have any mapped network drives?

Open Windows Explorer, and go to Tools/Disconnect Network Drive.  See anything unusual?  If you feel like it, you could disconnect any drives you see there and then test if the NET USE command works when there are no mapped drives.  Of course, after this test, you'll have to set up your mapped drives again, so it might be a pain to try out.  But it may work.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
knightfrankAuthor Commented:
awesome you were right. Went through 1 by 1 and a mapped drive was causing the error. Thanks
0
sjklein42Commented:
That's great.  Thanks.
0
knightfrankAuthor Commented:
happened to be a sharepoint drive also, the only sharepoint drive i had mapped
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
IT Administration

From novice to tech pro — start learning today.