Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
7.6.200.5 Invoicing
- Thread starter NeWTRoG
- Start date
MacolaHelp
Instructor
More details: OS of WS & server, what does "throw them out" mean (error messages, close the program, happens when printing), etc. I've never heard of this or experienced it at any of my sites. How long has this been going on? Is this a terminal session or citrix, or 2 completely separate companies on 2 separate servers?
- Thread starter
- #3
Thanks for your response - much appreciated.
It is happening at two sites one of which has Windows 2003 Server OS, MS SQL 2000 SP3, with an XP client accessing Macola via Citrix Metaframe Presentation Server (MPS3) and Citrix Program Neighbourhood client Version 8. The second site has Windows 2000 Server OS, MS SQL 2000 SP3, with a W2000 Professional WS running Macola across the LAN (i.e. Macola Client Installled on the WS). Neither site is in the USA if that makes any difference. The description was a users description and was not very accurate as it turns out - apologies. Apparently the Macola session freezes and has to be terminated and restarted. I don't use Macola myself but am responsible for network asdmin. so I am somewhat removed from the first line of support process but would like to know whether or not MUST use PWE (currently not a published application at the Citrix users site) or whether there something else we should be checking first. In other words I'd rather solve the problem than work around it. Thanks again.
It is happening at two sites one of which has Windows 2003 Server OS, MS SQL 2000 SP3, with an XP client accessing Macola via Citrix Metaframe Presentation Server (MPS3) and Citrix Program Neighbourhood client Version 8. The second site has Windows 2000 Server OS, MS SQL 2000 SP3, with a W2000 Professional WS running Macola across the LAN (i.e. Macola Client Installled on the WS). Neither site is in the USA if that makes any difference. The description was a users description and was not very accurate as it turns out - apologies. Apparently the Macola session freezes and has to be terminated and restarted. I don't use Macola myself but am responsible for network asdmin. so I am somewhat removed from the first line of support process but would like to know whether or not MUST use PWE (currently not a published application at the Citrix users site) or whether there something else we should be checking first. In other words I'd rather solve the problem than work around it. Thanks again.
- Thread starter
- #4
MacolaHelp
Instructor
Have you edited the registry to allow all macola users full permissions to the hkey\local\software macola, odbc, etc folders? And, did you use add programs (I'm sure you did) to install the macola, mssql clients, etc? If you are concerned about access to enterprise manager & such, you can still install the full client & then delete the shortcuts in the group so the users don't know they exist. I've seen some odd things happen if the full mssql client isn't installed.
- Thread starter
- #6
No I haven't edited the registry to allow macola users full permissions etc. - Wasn't aware of that one. Should i do this on the Citrix box? i.e. where the application is published for the Citrix user.
Yes I did use add programs to do all installs on the Citrix box (i.e. changed the user mode to install mode) and the installs are full client installs (shortcuts are deleted for the users groups).
A colleague has recently suggested a problem with EDI may have some part in this problem once i chase him down and get a full explanation I will re-post to see if it rings any bells.
Thanks again.
Yes I did use add programs to do all installs on the Citrix box (i.e. changed the user mode to install mode) and the installs are full client installs (shortcuts are deleted for the users groups).
A colleague has recently suggested a problem with EDI may have some part in this problem once i chase him down and get a full explanation I will re-post to see if it rings any bells.
Thanks again.
MacolaHelp
Instructor
Yes, do this on the citrix server & any LAN client with win2k or xp. Just one of those wierd macola/microsoft things.
- Thread starter
- #8
Ok, will check that one out, thanks a lot.
Just found out from our Business Systems department that there is apparently an ERS program that generates orders into Macola from an EDI flat file. What I guess we need to do now is determine whether or not Macola is freezing only when these orders are being invoiced or whether it is a global invoicing problem.
Just found out from our Business Systems department that there is apparently an ERS program that generates orders into Macola from an EDI flat file. What I guess we need to do now is determine whether or not Macola is freezing only when these orders are being invoiced or whether it is a global invoicing problem.
ERS? Why? Its already suspect, IMHO.
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
- Thread starter
- #10
Let us know if manually entered orders are having the same problems.
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports
- Thread starter
- #12
Thanks - I have shot an email off to the European site and anm awaiting a response. The user doing invoicing at my site (Aust) has given up using Prog. SQL explorer because of this problem and is using PWE.
All of our development for the past 5 years has been done in ERS - not just reports but complete manufacturing applications. There is quite a bit of investment in the whole system. However we are investigating moving away from ERS (a slow and frustrating process) and Business Systems people always tend to blame any problems on the physical system.
All of our development for the past 5 years has been done in ERS - not just reports but complete manufacturing applications. There is quite a bit of investment in the whole system. However we are investigating moving away from ERS (a slow and frustrating process) and Business Systems people always tend to blame any problems on the physical system.
MacolaHelp
Instructor
I don't think a data problem created by an external upload should cause this standard/PWE user interface symptom. But after you post the outcome of manual vs imported maybe we'll know better.
When I have seen standard/pwe differences in the past, it has been on xp & 98 LAN clients & has always related to the other programs installed on the workstation exhibiting the behavior. There's nothing wrong to switching to PWE. Most of my clients have converted over now.
Since PWE loads odbc connections & you are heavily invested in ERS/VBA, you may have a hodgepodge of VB dlls that PWE calls by default, but standard explorer doesn't when the program opens.
When I have seen standard/pwe differences in the past, it has been on xp & 98 LAN clients & has always related to the other programs installed on the workstation exhibiting the behavior. There's nothing wrong to switching to PWE. Most of my clients have converted over now.
Since PWE loads odbc connections & you are heavily invested in ERS/VBA, you may have a hodgepodge of VB dlls that PWE calls by default, but standard explorer doesn't when the program opens.
- Status
Similar threads