command line printing problems.

[Guest Curt]

win2k3 sbs. Printing worked fine until reboot yesterday.

On the server console:

When I print from application/test page, everything works fine.

When I try "dir > \\servername\printername" I get an error "The parameter is

incorrect."

I tried "print /d:\\servername\printername c:\testfile" and get "Unable to

initialize device \\servername\printername"

 

I try from a client PC, works fine. It's like the server isn't allowed to

print, but clients are.

 

How can I test/fix...what parameters could be incorrect?

[Guest Pegasus \(MVP\)]

Re: command line printing problems.

 

 

"Curt" <Curt@discussions.microsoft.com> wrote in message

news:ADBCE495-3550-4253-97FF-2432E0EB826E@microsoft.com...

> win2k3 sbs. Printing worked fine until reboot yesterday.

> On the server console:

> When I print from application/test page, everything works fine.

> When I try "dir > \\servername\printername" I get an error "The parameter

> is

> incorrect."

> I tried "print /d:\\servername\printername c:\testfile" and get "Unable to

> initialize device \\servername\printername"

>

> I try from a client PC, works fine. It's like the server isn't allowed to

> print, but clients are.

>

> How can I test/fix...what parameters could be incorrect?

>

 

Google is your friend. I typed this into a Google search box

printer "the parameter is incorrect"

and got around 18,000 hits. The one relating to the HP Photosmart printer

looks promising.

[Guest Curt]

SOLVED: Re: command line printing problems.

 

SOLVED: Re: command line printing problems.

 

I have been searching all day...litterally.

I found that a drwatson.log held the key.

Dell status monitor was causing the fault:

Long story short, I stopped the status monitor and printing works.

I uninstalled and it still works.

 

Here is the error from drwatson.log...in case it helps others.

 

*** WARNING: Unable to verify checksum for c:\program files\dell

printers\Additional Color Laser Software\Status Monitor\DLPSP.EXE

*** ERROR: Symbol file could not be found. Defaulted to export symbols for

c:\program files\dell printers\Additional Color Laser Software\Status

Monitor\DLPSP.EXE -

function: DLPSP

00402633 0000 add [eax],al

00402635 3beb cmp ebp,ebx

00402637 75d8 jnz DLPSP+0x2611 (00402611)

00402639 5f pop edi

0040263a 5e pop esi

0040263b 5d pop ebp

0040263c 33c0 xor eax,eax

0040263e 5b pop ebx

0040263f 81c428020000 add esp,0x228

00402645 c21000 ret 0x10

FAULT ->00402648 8bad28090000 mov ebp,[ebp+0x928]

ss:0023:00000928=????????

0040264e 3beb cmp ebp,ebx

00402650 0f84c8fbffff je DLPSP+0x221e (0040221e)

00402656 be01000000 mov esi,0x1

0040265b 8b453c mov eax,[ebp+0x3c]

0040265e 89742414 mov [esp+0x14],esi

00402662 3bc3 cmp eax,ebx

00402664 7413 jz DLPSP+0x2679 (00402679)

00402666 8d4c2414 lea ecx,[esp+0x14]

0040266a 6a04 push 0x4

0040266c 51 push ecx

 

 

Thanks for the reply!

"Pegasus (MVP)" wrote:

>

> "Curt" <Curt@discussions.microsoft.com> wrote in message

> news:ADBCE495-3550-4253-97FF-2432E0EB826E@microsoft.com...

> > win2k3 sbs. Printing worked fine until reboot yesterday.

> > On the server console:

> > When I print from application/test page, everything works fine.

> > When I try "dir > \\servername\printername" I get an error "The parameter

> > is

> > incorrect."

> > I tried "print /d:\\servername\printername c:\testfile" and get "Unable to

> > initialize device \\servername\printername"

> >

> > I try from a client PC, works fine. It's like the server isn't allowed to

> > print, but clients are.

> >

> > How can I test/fix...what parameters could be incorrect?

> >

>

> Google is your friend. I typed this into a Google search box

> printer "the parameter is incorrect"

> and got around 18,000 hits. The one relating to the HP Photosmart printer

> looks promising.

>

>

>

[Guest Pegasus \(MVP\)]

Re: SOLVED: Re: command line printing problems.

 

Re: SOLVED: Re: command line printing problems.

 

Strange . . . thanks for the feedback.

 

"Curt" <Curt@discussions.microsoft.com> wrote in message

news:8CCB2B29-A019-425F-95B8-5659A7482ED7@microsoft.com...

>I have been searching all day...litterally.

> I found that a drwatson.log held the key.

> Dell status monitor was causing the fault:

> Long story short, I stopped the status monitor and printing works.

> I uninstalled and it still works.

>

> Here is the error from drwatson.log...in case it helps others.

>

> *** WARNING: Unable to verify checksum for c:\program files\dell

> printers\Additional Color Laser Software\Status Monitor\DLPSP.EXE

> *** ERROR: Symbol file could not be found. Defaulted to export symbols

> for

> c:\program files\dell printers\Additional Color Laser Software\Status

> Monitor\DLPSP.EXE -

> function: DLPSP

> 00402633 0000 add [eax],al

> 00402635 3beb cmp ebp,ebx

> 00402637 75d8 jnz DLPSP+0x2611 (00402611)

> 00402639 5f pop edi

> 0040263a 5e pop esi

> 0040263b 5d pop ebp

> 0040263c 33c0 xor eax,eax

> 0040263e 5b pop ebx

> 0040263f 81c428020000 add esp,0x228

> 00402645 c21000 ret 0x10

> FAULT ->00402648 8bad28090000 mov ebp,[ebp+0x928]

> ss:0023:00000928=????????

> 0040264e 3beb cmp ebp,ebx

> 00402650 0f84c8fbffff je DLPSP+0x221e (0040221e)

> 00402656 be01000000 mov esi,0x1

> 0040265b 8b453c mov eax,[ebp+0x3c]

> 0040265e 89742414 mov [esp+0x14],esi

> 00402662 3bc3 cmp eax,ebx

> 00402664 7413 jz DLPSP+0x2679 (00402679)

> 00402666 8d4c2414 lea ecx,[esp+0x14]

> 0040266a 6a04 push 0x4

> 0040266c 51 push ecx

>

>

> Thanks for the reply!

> "Pegasus (MVP)" wrote:

>

>>

>> "Curt" <Curt@discussions.microsoft.com> wrote in message

>> news:ADBCE495-3550-4253-97FF-2432E0EB826E@microsoft.com...

>> > win2k3 sbs. Printing worked fine until reboot yesterday.

>> > On the server console:

>> > When I print from application/test page, everything works fine.

>> > When I try "dir > \\servername\printername" I get an error "The

>> > parameter

>> > is

>> > incorrect."

>> > I tried "print /d:\\servername\printername c:\testfile" and get "Unable

>> > to

>> > initialize device \\servername\printername"

>> >

>> > I try from a client PC, works fine. It's like the server isn't allowed

>> > to

>> > print, but clients are.

>> >

>> > How can I test/fix...what parameters could be incorrect?

>> >

>>

>> Google is your friend. I typed this into a Google search box

>> printer "the parameter is incorrect"

>> and got around 18,000 hits. The one relating to the HP Photosmart printer

>> looks promising.

>>

>>

>>