Error 1905 Trying to map printer

[Alovantous]

I have 17 machines in a pool that should be automaticlly mapping printers however I keep getting the following error randomly. (It works for a week then gives this error)

2017-06-27 07:51:15.393 [DEBUG] Broadcasting UEM shortcut changes

2017-06-27 07:51:16.691 [ERROR] Error 1905 trying to map printer '\\zenbarrieserv\Reception Keytag Printer' ('Reception Keytag Printer.xml')

2017-06-27 07:51:20.610 [INFO ] Successfully mapped printer '\\zenbarrieserv\Shop Management Office' ('Shop Management Office (Default).xml')

2017-06-27 07:51:20.610 [INFO ] Set printer as default

What would be causing this? I do not use App volumes nor do I use thin print.

[theaaronstrong]

Are there new print drivers?

[ijdemes]

"Error 1905 trying to map printer" has been reported in a thread last year. Maybe this gives you an indication.

Default printer mapping? and search for "error 1905".

[Sravan_k]

did you got fix for this problem?

[Pim_van_de_Vis]

The biggest problem here is that you use spaces in your shared printer names. This is known to cause issues as described my Microsoft here:

https://support.microsoft.com/en-us/help/2444599/a-printer-share-name-that-contains-spaces-or-that-i...

[VMvvol]

Hi Experts,

I was seeing same error message from UEM async log's.

I see two error codes, error 1905 and 21, but if I try to re-produce it with other user I am not seeing any issues, need some help here.

Thank you,

Volga.

[Sravan_k]

Hi Volga,

It was interesting, you are seeing error 1905 & 21 with one particular user?

error 1905: is due to naming or deleted printer related, as of I know

error 21: this was new for me, some one can comment on it

check the below things:

if you are delivering this printer using AD group? please make sure user is in and

check either it is blocking from local spooler to printer

also check this thread it may help you "Default printer mapping? "

Please let us know your feedback here

Regards,

Vkmr. 

[VMvvol]

Sorry for delay reply, I was little busy with my trainings

It was interesting, you are seeing error 1905 & 21 with one particular user?

Yes, it was happening with only one user.

error 1905: is due to naming or deleted printer related, as of I know

error 21: this was new for me, some one can comment on it

Yes, I saw one time this error 21, I am not aware of it too

check the below things:

if you are delivering this printer using AD group? please make sure user is in and

Yes I did, user is part of respected AD group

check either it is blocking from local spooler to printer

Yes, this printer is set to "everyone can print" under local print queue.

Any input is much appreciated ...

Thank you,

Volga.

[Sravan_k]

That's fine, currently I am running out of my questions since you replied to my questions as "Yes"

are you using appstacks?

alright,

Just give a try but I am not saying it is the solution, it may work.

Ask user to log-off

goto user profile and rename the "only" log files [for example logs and log-async files]

Ask user to log-in

and see if it works

In this process we are just cleaning the log files, please provide me your valuable feedback on it.

Regards,

Vkmr. 

[VMvvol]

Not worked

[HiggsBoson1]

Youre printer name is to long.

According to Microsoft, a shared printer name should not be longer than 31 characters...

https://support.microsoft.com/en-us/topic/a-printer-share-name-that-contains-spaces-or-that-is-longe...