Sage 100

MAS 200 4.30.0.21 on Windows 7 64 Bit workstation. I have installed the WKSupdate right clicked and Run as Admin. It's the only Win 7 workstation onsite. When we print the Daily Sales Reports from this workstation the Daily Sales Recaps aren't printing. It looks like the correct cdintf300.dll is in the Windows\SysWow64 folder. I don't see one in the Common Components folder. A bit stumped.

No other cdintfxxx files exist?

Is this the role maintenance issue? Didn't someone have something similar 2-3 months ago?

No other cdintf*.dll files.

I'm going to double check.

Grrrr.... I hate when I miss stuff like that. There was one. Got rid of it. No change.

what size is the cdintf file? It should be 3,744 KB on a 64-bit workstation, not 3,436 KB

Reregister the existing one? I have been wrestling with same issue for past week client is on 4.3.23....

Are they printing to printers or paperless? We have had a similar issue in PO Receipt of Invoice where MAS was combining multiple Journals/Registers into a single PDF for paperless and not all of them made it to the PDF. If printed directly to a printer, it worked fine. The issue only affected two Win 7 workstations.

It's paperless. That's what is happening here. The xp machines work fine.

On the Win 7 machine - do any other paperless documents print ok? Temporarily assign full rights to the user and test again.

The issue is the registers, as far as I know, are the only place where it's combining separate reports into one PDF. I'll check her local user rights in a few minutes. Or are you talking about MAS rights?

Possibly worth trying 1. The mas shortcut itself in Properties / shortcut tab choose Run as Administrator 2. In Sage PDF Converter properties :: - instead of Sage port create a directory path of C:\Users\username - on security tab increase permissions to max The thinking here is you may have Acrobat Reader X installed.

By username above I meant actual windows user login

I'll try that. I did make the change to the rights on the PDF Converter, but will try the rest. Doh! Yes. I think Acrobat Reader X is in stalled.

Or installed.

Weirdness. It's actually adding them to the PDF but when the PDF opens on the screen it's not on there.

@ThereseLogeais it's 3744 kb.

Local user is an administrator level account. Sometimes it's adding them to the PDF in Source Journal Viewer and sometimes it's not.

Once I made the changes @AlnoorCassim it's started adding them to the PDF that is getting saved but it's not always popping up with them. WTF? If I close the file and pull it up from the recent files in Acrobat Reader, it's the whole file. I also uninstalled Acrobat Reader 10 and rolled back the the one on the 4.30 installer. 8 I think.

Feeling like this?

That is a lovely stump.

And that is exactly how I feel. If it were consistent, I'd feel better.

I loaded Foxit Reader thinking that might make a difference. It didn't.

Here is the easiest way for me to fix paperless office on 4.3 on a Win 7 machine. Copy your WKSETUP from your 4.5 install. You will need to rename the old Wksetup to WKSetup430. Then in the 45 wksetup folder run the WksUpdate 90.exe only - it will install the sage pdf printer. Rename the wksetup folder to wksetup 450 and rename the wksetup430 back to WKSetup - Works like a champ!

Seems to work consistently in MAS 90 mode.

Hmmmm... That may be worth a shot @JohnnyPabian.

Double Hmmmmm....... Could this be the Hummmmmm Dinger????? RW, keep us posted on this solution!!!! @JohnnyPabian Do you ever get the ""incorrect version of Crystal"" message when you do this? I wonder what the effect is if you don't have least v4.3.18 installed? I have a client that is stuck at v4.3.11 that we are hoping to soon upgrade to v4.5 so we don't want to jump through the 4.3 upgrade hoops (SWK enhancements to deal with) and they want to add a WIN 7 64 OS to their network for the new CEO. Of course, I told them I could not support this configuration presently and urged them to sign off on the upgrade.

@JeffSchwenk the trick with Johnny's suggestion is to run just the update not the wksetup. It didn't work. It is consistently working in MAS 90 mode.

Unfortunately MAS 90 mode isn't a permanent solution.

@RobertWood - what isn't working? What do you mean mas90 mode? I thought the issue is the Sage PDF driver not installing on Win 7. The driver does not care if it is MAS90 or 200.

I agree @JohnnyPabian but if I log onto MAS 200 it still doesn't work. I get the Sales Journal but no Recap Report. If I copy a MAS 90 icon over to this system and point it at the MAS90 folder on the server and login it works. I get the Sales journal and the Recap Report. Which still means it is something to do with the files on the workstation install.

@RobertWood - With our client, the XP machines and other Win 7 machines work just fine. We have not been able to see any significant differences in the setups on these Win 7machines. I saw in a later post that you found the missing report is actually in the PDF but does not show up in paperless. With our client, the report is definitely missing from the PDF. Do I understand correctly, that reports were also missing from your PDFs prior to making the changes Alnoor suggested? In our case the issue was missing the variance register when updating PO Receipt of Invoice. There are potentially 4 journal/registers that can print with the variance register being #3. We found a workaround when the client informed us AP Tax tracking was on but they didn't use it. We cleared that and turned it off so the Tax summary didn't print any longer and now the variance shows up except on rare occasions. Now the issue is hard to duplicate. Specifically which journals are you having issues with? I would like to do some more testing and try Alnoor's suggestions. I spent a lot of time with Chris Powers on this and we kind of gave up when the workaround produced significant improvement. Also never tried the MAS90 mode.

hmm ok - I have seen a similar issue with the gross profit not printing in 4.2 - check the cdintf250.dll file on the server and compare to workstation.

I guess it is the cdintf250.dll for 4.2 and cdintf300 for 4.30.

In 4.30 it's cdintf300.dll and they're the same.

It's weird. It works when I run from an icon setup to run in MAS90 mode. It doesn't work (consistently) when running from a MAS 200 icon.

It's not related to paperless being on another sever and running MAS200 as a service with a login that does not allow for access to the other server via unc? I doubt it and it may have been covered but ran into this on one MAS 200 upgrade some time ago.

Everything is stored on the same server.

And it all works fine from XP machines.

Last week I spent way too much time getting the PDF converter to install on Win 7 64 bit on 4.3.0.21, and finally got Sage involved. I used all the Sage KB articles and 90Minds posts I could lay my hands on, to no avail. I worked with Cullen at Sage. The first thing that pissed me off was that he says something to the effect of ""When I get this kind of call, I pull out my handy dandy cheat sheet with my top 3 things to check"". <Rant on> Why the **** does he need a cheat sheet!? After all this time, why isn't this issue either resolved in one way or another or at least well documented in, oh say, the installation guide or a current KB article? <Rant off> So, in case this helps anyone, these are the steps that ulimately worked. I've attached Cullen's cheat sheet, and my marked up copy of reside 506665.

@BarbaraGoldstein - do you know what ultimately worked because most of those tips are similar to what floats around here. I'm curious if something outside of that worked or was it some type of anti-virus / rights / malware type issue?

What I did differently with Sage that ultimately succeeded were registering the CDINTF300.DLL in SysWow64 and registering it with the REGSVR32.EXE in SysWow64.

Thanks

One of those DUH moments, this is what finally worked on the NEW WIN 7 64 OS workstation running v4.3.21. I reran the 4.30PDFDriverUpdate.exe at the server, then uninstalled the client, rebooted, then ran the wksetup again. Client installed a couple WIN 7 32 OS several months back (running FRx). Client picked up several WIN 7 64 OS workstations (not running FRx on these machines). Since I saw the patch on the server, I ASSUMED that it had been installed. Thus I was beating my head for several days. After installing the patch, all is well in MAS land...............

Doh! I will have to pursue that.

Actually, I think you situation is different. PDF works in most instances.

It shouldn't hurt to try it anyway.